cx-data-pipeline
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", "enr
Security Assessment
About cx-data-pipeline
cx-data-pipeline is a guidance skill for configuring how Coralogix processes, enriches, and transforms ingested observability data through the official cx command-line tool. It addresses the friction of hand-authoring the complex JSON payloads these operations require by teaching a template-from-existing-resource workflow: get an existing resource as JSON, modify it, then create or update. The skill spans four capability areas exposed by the CLI, and includes a reference file documenting the Events2Metrics JSON wire format, enums, and cardinality rules.
It covers parsing rules (extracting structured fields from raw logs via regex), enrichments (adding context from lookup tables including geo-IP, AWS, suspicious-IP, and custom tables), Events2Metrics (deriving Prometheus metrics from log and span events), and Prometheus recording rules (precomputing PromQL expressions). Each command supports list, get, create, update, and delete subcommands, plus JSON output and profile selection. The skill explains operational nuances such as E2M being forward-only with no backfill, TCO tier behavior, and verifying results by querying hot storage rather than archive.
The intended users are Coralogix platform engineers, SREs, and observability practitioners who manage data pipelines from the terminal. Typical use cases include setting up log parsing for a new service, adding geo enrichment, reducing log cost by converting high-volume events to metrics, and troubleshooting an E2M that produces no series.
FAQ
What can this skill configure?
Parsing rules, enrichment rules and custom lookup tables, Events2Metrics definitions, and Prometheus recording rule groups, all via the cx CLI.
How do I avoid JSON payload errors?
Always template from an existing resource: get it as JSON, modify the fields, remove the ID for create operations, then create or update via --from-file. The skill notes payload format errors are the number-one cause of failed attempts.
Does E2M backfill historical data?
No. Events2Metrics is forward-only; metrics start from the moment the E2M is created. It aggregates events as they stream through the real-time ingestion pipeline at roughly one-minute resolution.
What are the prerequisites?
The cx CLI installed and configured with a profile. Some features, such as scoping an E2M to a dataset via dataSource, require an account feature flag to be enabled or the API rejects the request.
How do I verify enrichment worked?
Query logs on the hot storage (FrequentSearch) tier to confirm enriched fields appear; avoid querying archive for verification because ingestion delays can cause false negatives.
Install cx-data-pipeline
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
coralogix/cx-cli