cx-infra
Query Coralogix infrastructure resources with the cx infra CLI: resource types, filterable attributes, resource lists, health, raw data and configuration changes. Use when the user asks to "show resource types", "list infrastructure resources", "what resources of this kind are monitored", "is this resource healthy", "why is this resource critical", "which health policy is failing", "when did this resource go critical", "get raw resource data", "find resources by name", "filter resources by service or environment", "critical hosts in a region", "what can I filter resources by", "resources in this cluster or namespace", "which resources changed recently", "what changed in this resource", "configuration drift", "did anything change before the incident", "what was this config last week", or wants to explore infrastructure resources.
- Installs
- 2.6K
- Last 24h
- +85
- Trending rank
- #2211
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/coralogix/cx-cli --skill cx-infra- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads cx-infra automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Infrastructure Resources
All commands live under cx infra resources and are read-only. Run
cx infra resources <command> --help for flags.
"Infrastructure monitoring is not enabled for this team" means the team has no infrastructure data. Stop and say so. Do not retry or change filters.
A stderr line starting warning: ... could not verify that infrastructure monitoring is enabled is informational: the enablement check itself failed and
the command still ran.
| Command | Answers |
|---|---|
types | which (category, type) pairs exist |
filters | which attributes can be filtered on, and their accepted values |
list | which resources match, with their health policies |
health-history | daily health per resource, oldest first |
raw-data | the raw resource document, now or at a past time |
config-changes | which resources changed configuration in a window |
config-diff | what changed, field by field |
Resource ids
- Take them from
list(resource_id) and pass them as-is, quoted. health-history,config-changesandconfig-difftake up to 100 ids per call. Pass them all in one call, not one call each. Over 100, the CLI refuses. Split into batches.- An id belongs to one team, so the id commands refuse more than one
-p. Onlytypes,filtersandlistfan out across profiles. From a multi-profilelist, use the row'sprofileto pick the one to query. - Ids mean nothing outside this skill. To reach other skills, use the resource
nameor itsServicevalue.
Finding resources
filtersfirst. Attribute names and values differ per type, so never guess. Per attribute:kind(stringis free text,statusa fixed set),values(the accepted set) andwildcard(whether*works).listwith the filters:- Every
--match-allmust match, at least one--match-anymust match, and the two groups are ANDed.--match-all OS=linux --match-any Health=Critical --match-any Region=eu-west-1meansOS=linux AND (Health=Critical OR Region=eu-west-1). - Commas give one attribute several values. In
--match-anyany one matches. In--match-allall must, which only makes sense for wildcards:--match-all 'Name=*alert*,*processing*'. - Name an attribute once, in one flag. A repeat is refused.
--categoryand--typeare plain filters, not requirements, and are not attributes (no--match-all Category=...). At least one filter or scope flag is required.- Exact values are case-sensitive (
OS=linux, notOS=Linux). Wildcards are not. Quote wildcards so the shell leaves*alone. --name-filterand--scope(service,environment,team) are legacy flags. They need both--categoryand--type, and cannot mix with--match-*.--match-all 'Name=*web*'does what--name-filter webdoes.
- Every
- Zero rows is an answer. Don't retry. A wrong attribute or value is refused with the accepted ones listed.
list -o json is an envelope: {total_count, returned_count, resources}.
The other commands return plain arrays or objects.
- It returns one window, rows 0 to 100 by default (
--start-row, and--end-rowwhich is exclusive). Keep paging whilestart_row + returned_count < total_count. - A window cannot pass row 10,000. For bigger results, narrow the query.
- With several profiles, each one pages against its own
total_count(seecounts_by_profile).
Health
listrows carryhealth_policies: [{id, name, status}]withstatusone ofhealthy,criticalorpending(not evaluated yet). A critical policy says why a resource is critical. No extra call needed.health-historyreturns[{resource_id, health_history: [{timestamp, status}]}]withstatusone ofHealthy,CriticalorUnmonitored. The two sets of statuses have different casing.- Ids that don't parse, and repeats, are dropped. A shorter answer is normal and stderr gives the count. Returned ids are normalized, so they may not string-match the ones sent.
- Infra health is not Service Catalog health. Correlate it with telemetry rather than treating the two as the same.
cx infra resources list --match-all Health=Critical -o json \
| jq '.resources[] | {name, failing: [.health_policies[] | select(.status == "critical") | .name]}'
cx infra resources health-history "1001234:host_id=i-abc" "1001234:host_id=i-def" -o json \
| jq '.[] | {resource_id, critical: [.health_history[] | select(.status == "Critical") | .timestamp]}'
Raw data
raw-data -o json returns {version_timestamp, raw_data}.
--timestamp(now-7dor ISO-8601) gets the newest version at or before that time.version_timestampsays which version came back, and can be passed back as--timestampto get it again.raw_data: nullmeans no document. That is not an error.version_timestamp: nullwith a document means the document has no version.
Configuration changes
Two steps: find out which resources changed, then see what changed.
cx infra resources config-changes --resource-id "1001234:host_id=i-abc" \
--resource-id "1001234:host_id=i-def" --from now-24h -o json
cx infra resources config-diff --resource-id "1001234:host_id=i-abc" --from now-24h -o json \
| jq '.[] | select(.outcome == "changed") | .changes[] | {field, before, after}'
config-changeslists only resources that changed. Empty means nothing changed. Don't retry with a wider window.- Rows are per resource and source. A resource with two collectors can give two rows.
- Some cloud and agent types report an update every collection cycle, so
config-changescan flag them when nothing changed. Check withconfig-diffbefore telling the user something changed. config-diffhas no row for a resource with no history in the 14 days before--fromor inside the window. Readoutcomebeforechanges:
outcome | meaning |
|---|---|
changed | the versions before and inside the window differ |
unchanged | they don't differ, or nothing happened inside the window |
created | the resource first appeared inside the window |
priorStateUnavailable | it changed, but no version exists in the 14 days before --from. Not a failure. Move --from earlier to reach an older version |
comparisonUnavailable | both versions exist, but one could not be read |
beforeandafterare raw JSON.nullmeans the field was added or removed. A new or removed subtree is one entry.- To look at a single change, narrow
--fromand--toaround it.
Related Skills
Bridge with the resource name or its Service value:
cx-telemetry-querying:cx search-fields "<name>" -s valuefinds the log and span fields holding the name.cx logs "filter $l.subsystemname == '<service>'"gets its telemetry.cx-alerts:cx alerts list --name "<name-or-service>".cx-dashboards:cx dashboards search "<name-or-service> ...". Aftersearch-fields -s value,cx dashboards query-search --field <field>finds queries on that field.
FAQ
What does the cx-infra skill do?
Query Coralogix infrastructure resources with the cx infra CLI: resource types, filterable attributes, resource lists, health, raw data and configuration changes. Use when the user asks to "show resource types", "list infrastructure resources", "what resources of this kind are monitored", "is this resource healthy", "why is this resource critical", "which health policy is failing", "when did this resource go critical", "get raw resource data", "find resources by name", "filter resources by service or environment", "critical hosts in a region", "what can I filter resources by", "resources in this cluster or namespace", "which resources changed recently", "what changed in this resource", "configuration drift", "did anything change before the incident", "what was this config last week", or wants to explore infrastructure resources.
How do I install cx-infra?
Run npx skills add https://github.com/coralogix/cx-cli --skill cx-infra in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/cx-infra/ (personal) or .claude/skills/cx-infra/ (project).
Which AI agents can use cx-infra?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is cx-infra safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains cx-infra?
It is published by coralogix in coralogix/cx-cli. It has 2,639 recorded installs.
More from coralogix/cx-cli
cx-telemetry-querying
coralogix/cx-cli
Use this skill for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior", "understand a production incident", "query telemetry data", "look at logs", "search logs", "find errors", "find stack traces", "filter by severity", "check traces", "examine spans", "investigate request latency", "debug service-to-service calls", "look up a trace ID", "analyze RUM data", "query rum.events", "check frontend performance", "frontend errors", "Core Web Vitals", "JavaScript exceptions", "query metrics", "check CPU usage", "run a PromQL query", "check error rate", "look up a metric", "check memory usage", "how do I write a DataPrime query", "DataPrime syntax", or wants to answer questions using observability data from logs, metrics, traces, RUM, or APM.
cx-search-dashboard
coralogix/cx-cli
This skill should be used when the user asks to "find a dashboard", "search dashboards", "does a dashboard exist for X", "find widgets that query Y", "which dashboards use this field", "find a dashboard about errors", "look up dashboards by description", "search for existing monitoring dashboards", "find widgets that reference a field", or wants to discover existing Coralogix dashboards or widgets using natural-language or field-based search.
coralogix-docs
coralogix/cx-cli
Search and read official Coralogix platform documentation using cx docs search and cx docs fetch. Use when the user asks how Coralogix features work, how to configure or use the UI, set up integrations (OpenTelemetry, agents, collectors, webhooks), manage API keys, explore spans/traces/logs in the product, configure alerts/SLOs/dashboards, or needs authoritative product docs — not live tenant telemetry.
cx-alerts
coralogix/cx-cli
This skill should be used when the user asks to "manage alerts", "create alert", "list alerts", "delete alert", "check alert status", "enable alert", "disable alert", "investigate firing alerts", "check which alerts are active", "find alerting rules", "set up an alert", "configure alerting", "mute an alert", "silence an alert", "see alert definitions", "check alert priority", or wants to manage Coralogix alert definitions using the cx CLI.
cx-cli
coralogix/cx-cli
This skill should be used whenever the user runs any cx command, uses the cx CLI, Coralogix CLI, or mentions cx in the context of Coralogix observability. This skill provides cross-cutting concerns like update notifications that apply to all cx commands.
cx-observability-setup
coralogix/cx-cli
Use this skill when the user asks to "set up monitoring", "configure observability", "onboard new service", "create saved view", "set up notifications", "configure webhook", "set up Slack integration", "outgoing webhook", "automation action", "webhook for alerts", "create view", "saved view", "view folder", "organize dashboards", "install integration", "configure extension", "contextual data", "connect external service", "create notification connector", "set up email alerts", "configure PagerDuty", "notification routing", "deploy extension", "test webhook", "notification preset", "test notification", "webhook actions", or wants to set up, configure, or manage the observability stack for a service or team.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.