Common questions
The questions new users ask most, grouped by what you are trying to do. If your question is about something not working, see Troubleshooting instead.
Sending data
What is the fastest way to send my first data?
Use an integration package: a guided flow that sets the API key, endpoint, and application and subsystem for you. If you already run the OpenTelemetry Collector, point its exporter at your Coralogix endpoint instead. For a one-off test, post directly to the logs API.
What data sources does Coralogix support?
Logs, metrics, and traces from any source. Use OpenTelemetry for vendor-neutral collection, integration packages for one-step setup, shippers such as Fluent Bit and Prometheus, or browse the full integrations catalog for cloud providers and custom sources.
How long does it take for data to appear?
Usually a few minutes after setup. Livetail is the quickest way to confirm data is arriving. Note that events carry a timestamp: data timestamped more than 24 hours in the past or future is rejected, so check your shipper's clock and timezone if nothing shows.
Which API key do I need?
Use a Send-Your-Data API key for ingestion. It is different from Query, Team, and Personal keys, which are for API operations, sending data with the wrong key type fails authentication.
Which region and endpoint am I on?
Your region is set by the URL you sign in with. Match your team hostname to a row in the Quick reference, or use the domain selector on the endpoints reference to get the exact ingress and management endpoints for your domain.
Organizing and access
What are application and subsystem names for?
They are the two labels that organize everything you send. Use the application name for an environment or Kubernetes namespace (for example production), and the subsystem name for the service that emits the data (for example checkout). They drive filtering across the platform and can gate permissions, so pick a convention early.
How do I control who can see which data?
Separate data with application and subsystem names, then use teams and data scopes to control access and visibility per user. Note that Send-Your-Data and Team keys are not user-aware: they act with the permissions attached to the key, not a user's scope.
Cost, limits, and sensitive data
How does Coralogix keep observability costs down?
Coralogix processes data in-stream with Streama, so alerting, parsing, and metrics happen before storage, without indexing everything first. You then route each data flow to a TCO tier by how you use it: Frequent Search for interactive queries, Monitoring for dashboards and alerts, and Compliance for long-term archive. Lower tiers cost less per GB, so you match spend to value.
Are there limits I should know about?
A few per-team defaults matter early on: 35 parsing rules, 500 alerts, 10 anomaly-detection alerts, and 8 enrichments. Extension packages draw from these same limits. Contact Support through the in-app chat to raise them. See the Quick reference for the full list.
How do I keep sensitive data out of Coralogix?
Redact it at the source, before it leaves your environment. The OpenTelemetry Collector offers attributes, redaction, transform, and filter processors to block, mask, or drop fields; parsing rules can do the same on ingest. See Handling PII and sensitive data.
Tools and workflows
What is the difference between Explore, Livetail, and dashboards?
Explore is for searching and investigating historical logs and spans. Livetail streams logs in real time as they arrive. Custom dashboards give persistent visualizations of logs, metrics, and traces for ongoing monitoring. Use Explore to investigate, Livetail to verify, and dashboards to monitor.
Can I use Coralogix with my existing Grafana dashboards?
Yes. Coralogix provides a hosted Grafana instance and a Grafana plugin that query your Coralogix data. Import existing dashboards or build new ones on your Coralogix metrics.
Can I manage Coralogix as code?
Yes. Use the Terraform provider or the Coralogix Operator to define alerts, dashboards, and rules declaratively, the REST APIs for programmatic control, and the MCP server to drive Coralogix from AI tools.
Related resources
Next steps
Running into a setup problem? See Troubleshooting.