cx-dashboards
Build and deploy a Coralogix dashboard for a given service from its logs, spans, metrics, and service specs. Discovers telemetry via cx CLI commands, emits importable Coralogix JSON, verifies every PromQL and DataPrime query live through the `cx` CLI, and creates or updates dashboards via `cx dashboards create` and `cx dashboards replace`. Use whenever the user asks to create, build, generate, deploy, update, replace, or modify a Coralogix dashboard, monitoring dashboard, or observability dashbo
Security Assessment
About cx-dashboards
cx-dashboards builds and deploys a Coralogix observability dashboard for a target service, driven by the service's own telemetry — logs, spans, metrics, and service specs. It solves the tedious and error-prone work of authoring correct Coralogix dashboard JSON: it discovers the service's real metric names, log fields, and span attributes (only using ones it can cite from code, README, config, or a live query result rather than inventing them), emits importable Coralogix JSON, and verifies every PromQL and DataPrime query live through the cx CLI before deploying.
The workflow is a strict multi-phase checklist: discover telemetry and business meaning, gather dashboard specifications from the user, draft an internal plan of sections and widgets, generate the JSON, live-verify every query, self-verify structure, run a server-side validation via `cx dashboards check`, deploy with `cx dashboards create`, and finally share a clickable dashboard link. It ships reference material on DataPrime and PromQL syntax, log and span field discovery, dashboard query gotchas, and widget JSON templates. Supporting cx commands let it list the dashboard catalog, fetch an existing dashboard as a template, manage folders, and replace or duplicate dashboards.
It targets observability engineers, SREs, and developers using Coralogix who want a repeatable, verified path from a service to a working monitoring dashboard. The cx CLI operations involved are read-only telemetry queries plus dashboard create/replace calls against the user's own Coralogix account; there is no destructive or offensive behavior, and the emphasis on live-verifying queries and never fabricating field names makes it a careful, benign authoring tool.
FAQ
What does this skill produce?
An importable Coralogix dashboard JSON for a target service, deployed via the cx CLI, with every PromQL and DataPrime query verified live before deployment and a shareable dashboard link at the end.
How does it avoid inventing metrics or fields?
It only uses metric names, log fields, and span attributes it can cite from the service's code, README, configuration, or a live query that actually returned a result, and it live-verifies each query through the cx CLI.
What is the workflow?
A nine-phase checklist: discover telemetry and business meaning, gather specs from the user, draft a plan, generate JSON, live-verify queries, self-verify structure, run server-side validation with `cx dashboards check`, deploy with `cx dashboards create`, and share the link. Phases must proceed in order.
Can it update or duplicate existing dashboards?
Yes. It can fetch a dashboard as JSON with `cx dashboards get`, edit it, and apply with `cx dashboards replace`, or remove the id field and create a new copy. It can also list the catalog and manage dashboard folders.
What query languages does it support?
PromQL for metrics and DataPrime for logs and spans, with reference guides for syntax, counters versus gauges, histograms, and dashboard-specific gotchas such as time-range variables and PromQL query types.
All Files
9 filesInstall cx-dashboards
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
coralogix/cx-cli