
cx-observability-setup
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.
- Installs
- 3.5K
- Last 24h
- +75
- Trending rank
- #2428
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/coralogix/cx-cli --skill cx-observability-setup- 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-observability-setup 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.
Observability Setup Skill
Use this skill when setting up or configuring the observability stack - saved views, webhook integrations, notification channels, and external integrations. This is the "day 1 setup" skill for onboarding a new service or reconfiguring notification pipelines.
CLI Commands
Views
| Command | Purpose |
|---|---|
cx views list | List all saved views |
cx views get <id> | Get a view definition |
cx views create --from-file | Create a saved view |
cx views update <id> --from-file | Update a saved view |
cx views delete <id> | Delete a saved view |
cx views folders list | List view folders |
cx views folders get <id> | Get a folder |
cx views folders create --from-file | Create a folder |
cx views folders update <id> --from-file | Update a folder |
cx views folders delete <id> | Delete a folder |
Webhooks
| Command | Purpose |
|---|---|
cx webhooks list | List all outgoing webhooks |
cx webhooks get <id> | Get webhook details |
cx webhooks create --from-file | Create a webhook |
cx webhooks update <id> --from-file | Update a webhook |
cx webhooks delete <id> | Delete a webhook |
cx webhooks test <id> | Test a webhook |
cx webhooks types | List available webhook types |
cx webhooks actions list | List automation actions |
cx webhooks actions get <id> | Get action details |
cx webhooks actions create --from-file | Create an action |
cx webhooks actions update --from-file | Update an action |
cx webhooks actions delete <id> | Delete an action |
cx webhooks actions batch --from-file | Batch execute actions |
cx webhooks actions reorder --from-file | Reorder actions |
Notifications
| Command | Purpose |
|---|---|
cx notifications connectors list | List notification connectors |
cx notifications connectors get <id> | Get connector details |
cx notifications connectors create --from-file | Create a connector |
cx notifications connectors update --from-file | Update a connector |
cx notifications connectors delete <id> | Delete a connector |
cx notifications connectors types | List connector types |
cx notifications connectors entity-types | List entity types |
cx notifications connectors entity-subtypes --type <type> | List entity subtypes |
cx notifications routers list | List notification routers |
cx notifications routers get <id> | Get router details |
cx notifications routers create --from-file | Create a router |
cx notifications routers update --from-file | Update a router |
cx notifications routers delete <id> | Delete a router |
cx notifications routers validate-matcher --from-file | Test entity label matcher |
cx notifications presets list | List notification presets |
cx notifications presets get <id> | Get preset details |
cx notifications presets create --from-file | Create a custom preset |
cx notifications presets update --from-file | Update a custom preset |
cx notifications presets delete <id> | Delete a custom preset |
cx notifications presets set-default <id> | Set default preset |
cx notifications test connector --from-file | Test connector config |
cx notifications test destination --from-file | Test destination |
cx notifications test preset --from-file | Test preset config |
cx notifications test routing-condition --from-file | Test routing condition |
cx notifications test template-render --from-file | Test template rendering |
Integrations
| Command | Purpose |
|---|---|
cx integrations list | List all integrations |
cx integrations get <id> | Get integration details |
cx integrations create --from-file | Create an integration |
cx integrations update <id> --from-file | Update an integration |
cx integrations delete <id> | Delete an integration |
cx integrations test --from-file | Test integration config |
cx integrations template | Get integration template |
cx integrations definition <id> | Get integration definition |
cx integrations deployed <id> | Get deployed integration |
cx integrations extensions list | List available extensions |
cx integrations extensions get <id> | Get extension details |
cx integrations extensions deployed | List deployed extensions |
cx integrations extensions deploy --from-file | Deploy an extension |
cx integrations extensions update --from-file | Update deployed extension |
cx integrations extensions undeploy --from-file | Undeploy an extension |
cx integrations contextual-data list | List contextual data integrations |
cx integrations contextual-data get <id> | Get contextual data details |
cx integrations contextual-data create --from-file | Create contextual data integration |
cx integrations contextual-data update <id> --from-file | Update contextual data integration |
cx integrations contextual-data delete <id> | Delete contextual data integration |
cx integrations contextual-data definition <id> | Get contextual data definition |
cx integrations contextual-data test <id> | Test contextual data integration |
All commands support -o json for structured output and -p <profile> for profile selection.
New Service Setup Workflow
When onboarding a new service, follow this checklist:
1. Create Saved Views
Set up views for the service's key log queries:
cx views folders create --from-file folder.json
cx views create --from-file view.json
2. Set Up Notification Connectors
Configure channels (Slack, PagerDuty, email):
cx notifications connectors types -o json
cx notifications connectors create --from-file slack-connector.json
3. Configure Notification Routing
Route alerts to the right channels:
cx notifications routers create --from-file router.json
4. Set Up Webhooks
Configure outgoing webhooks for external integrations:
cx webhooks types -o json
cx webhooks create --from-file webhook.json
cx webhooks test <webhook-id>
5. Install Integrations
Deploy relevant integrations and extensions:
cx integrations list -o json
cx integrations create --from-file integration.json
cx integrations extensions deploy --from-file extension.json
6. Create Dashboard
Use the cx-dashboards skill for the full dashboard creation workflow.
7. Create SLOs
Use the cx-slos skill for SLO creation and monitoring.
Notification Setup Workflow
Detailed notification channel configuration:
1. List Available Connector Types
cx notifications connectors types -o json
2. Create a Connector
cx notifications connectors create --from-file connector.json
3. Create a Router
cx notifications routers create --from-file router.json
4. Assign or Create a Preset
cx notifications presets list -o json
cx notifications presets create --from-file preset.json
cx notifications presets set-default <preset-id>
5. Test End-to-End
cx notifications test connector --from-file test-connector.json
cx notifications test destination --from-file test-destination.json
cx notifications test routing-condition --from-file test-condition.json
Webhook Setup
1. List Webhook Types
cx webhooks types -o json
2. Create Webhook
Template from an existing webhook if possible:
cx webhooks get <existing-id> -o json > webhook-template.json
cx webhooks create --from-file webhook.json
3. Test Webhook
cx webhooks test <webhook-id>
4. Create Automation Actions (Optional)
cx webhooks actions create --from-file action.json
cx webhooks actions reorder --from-file order.json
Key Principles
- Always test after setup - use
cx notifications test,cx webhooks test,cx integrations test - Use
--from-filefor complex JSON payloads - pipe from stdin or use a file - Template from existing -
cx <command> get <id> -o json > template.jsonbefore creating - Check connector types first -
cx notifications connectors typesandcx webhooks typesbefore creating
Related Skills
cx-dashboards- dashboard creation and replace workflowcx-slos- SLO creation and error-budget monitoringcx-cases- triage the cases raised when alerts firecx-alerts- alert definitions that trigger notificationscx-telemetry-querying- verify data flows after setup
FAQ
What does the cx-observability-setup skill do?
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.
How do I install cx-observability-setup?
Run npx skills add https://github.com/coralogix/cx-cli --skill cx-observability-setup 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-observability-setup/ (personal) or .claude/skills/cx-observability-setup/ (project).
Which AI agents can use cx-observability-setup?
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-observability-setup 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-observability-setup?
It is published by coralogix in coralogix/cx-cli. It has 3,453 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-data-pipeline
coralogix/cx-cli
Use this skill when the user asks to "set up parsing", "create parsing rule", "extract fields from logs", "regex extraction", "log parsing", "enrich logs", "add context to logs", "custom enrichment table", "lookup table", "geo enrichment", "create metric from logs", "events to metrics", "convert logs to metrics", "generate metrics from events", "recording rule", "precomputed metrics", "PromQL recording", "configure data pipeline", "transform log data", "data processing rules", "rule group", "enrichment settings", "E2M definition", "labels cardinality", "bulk delete rules", "enrichment limits", "search enrichment table", "what should I convert to metrics", "E2M not producing metrics", "E2M no series", "reduce log cost with E2M", "logs to metrics aggregation", "spans to metrics", or wants to configure how Coralogix processes, enriches, or transforms ingested data.
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.