
Cx Search Dashboard
- 1.3k installs
- 113 repo stars
- Updated August 4, 2026
- coralogix/cx-cli
cx-search-dashboard is a Coralogix CLI skill that discovers existing monitoring dashboards and widgets through semantic or field-based search for developers who need to find observability views before building duplicates
About
cx-search-dashboard is a Coralogix cx-cli agent skill (version 0.1.0) for discovering existing Coralogix dashboards and widgets before creating new monitoring views. It uses natural-language or field-based search via cx dashboards CLI commands to answer questions like whether a dashboard exists for errors, which widgets query a specific field, or which dashboards reference a given metric. Developers reach for cx-search-dashboard when operating Coralogix-backed systems and needing to locate prebuilt observability assets instead of rebuilding dashboards from scratch during incident response or platform audits.
- Semantic search across dashboards using natural language descriptions
- Field-based widget discovery to find every dashboard referencing a specific log field
- 5 specialized cx dashboards CLI commands for search, catalog, and retrieval
- Always-search-first rule to prevent dashboard duplication
- JSON and agent-optimized output formats for downstream automation
Cx Search Dashboard by the numbers
- 1,313 all-time installs (skills.sh)
- +112 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #299 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/coralogix/cx-cli --skill cx-search-dashboardAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.3k |
|---|---|
| repo stars | ★ 113 |
| Last updated | August 4, 2026 |
| Repository | coralogix/cx-cli ↗ |
How do you find existing Coralogix dashboards by field or topic?
Quickly discover existing Coralogix monitoring dashboards and widgets before building new ones.
Who is it for?
Platform and SRE developers operating Coralogix who need to discover existing dashboards and widgets by natural language or log field before building new ones.
Skip if: Developers without Coralogix access or those building brand-new observability stacks unrelated to existing cx dashboards inventory.
When should I use this skill?
The user asks to find a Coralogix dashboard, search dashboards by description, or locate widgets querying a specific field.
What you get
Matching Coralogix dashboard listings, widget references, and field-usage reports from cx dashboards CLI search.
- dashboard search results
- widget field references
- existing observability inventory
By the numbers
- cx-search-dashboard skill version 0.1.0
Files
Dashboard Search Skill
Use this skill to discover existing Coralogix dashboards and widgets using semantic or field-based search via the cx dashboards CLI commands. Before creating a new dashboard, always search first to avoid duplication.
CLI Commands
| Command | Purpose | Key flags |
|---|---|---|
cx dashboards search "<description>" | Find dashboards by natural-language description | --limit |
cx dashboards query-search --description "<text>" | Find widgets whose queries match a description | --limit |
cx dashboards query-search --field "<field-path>" | Find all widgets that reference a specific field | --limit |
cx dashboards catalog -o json | List all dashboards | - |
cx dashboards get <id> -o json | Get full dashboard definition | - |
Output format: append -o json or -o agents for machine-readable output.
When to Use Each Command
| Goal | Command |
|---|---|
| Check if a dashboard for a service or topic already exists | cx dashboards search |
| Find widgets whose queries cover a topic you care about | cx dashboards query-search --description |
| Find widgets whose queries reference a specific field path | cx dashboards query-search --field |
| Browse all dashboards | cx dashboards catalog |
Examples
Find a dashboard for a service
cx dashboards search "payment service error rate"
cx dashboards search "kubernetes node cpu"Find widgets whose queries cover a topic
cx dashboards query-search --description "http 5xx error rate"
cx dashboards query-search --description "p99 latency over time"Find all widgets that reference a field
cx dashboards query-search --field '$d.http.status_code'
cx dashboards query-search --field '$d.kubernetes.pod.name'This reveals query patterns already in use — useful for reusing existing approaches when adding new widgets.
Inspect and clone a found dashboard
# Get full JSON of a dashboard you found
cx dashboards get <dashboard-id> -o json > dashboard.json
# Modify it, then create a copy
cx dashboards create --from-file dashboard.jsonKey Principles
- Search before creating — always run
cx dashboards searchbefore building a new dashboard to avoid duplicates - Use field search for discovery —
cx dashboards query-search --fieldshows how a field is already being queried, which is the fastest way to find reusable PromQL or DataPrime patterns - Description search is fuzzy — the results are ranked by similarity, not exact match; try several phrasings if the first search returns nothing useful
- Use `cx dashboards get` to inspect — once you find a relevant dashboard or widget, pull its full JSON to study the query structure
Related Skills
- `cx-dashboards` — build and deploy a new Coralogix dashboard from scratch
- `cx-telemetry-querying` — discover what telemetry fields and metrics exist before searching dashboards
Related skills
How it compares
Pick cx-search-dashboard over manual Coralogix UI browsing when agents must programmatically inventory dashboards and field-referencing widgets via CLI.
FAQ
How does cx-search-dashboard find Coralogix dashboards?
cx-search-dashboard uses Coralogix cx dashboards CLI commands with semantic or field-based search to locate existing dashboards and widgets by description, topic, or specific log and metric field references.
When should developers use cx-search-dashboard?
cx-search-dashboard fits Coralogix operators who need to confirm whether a dashboard already exists for errors or a field, discover widgets querying a metric, or avoid duplicating monitoring views during incidents.