Infrastructure Data Usage
Coralogix provides a transparent view into your infrastructure telemetry usage to help teams stay within fair usage limits and maintain system health.
The Infrastructure Data tab in the Data Usage section offers a clear breakdown of ingested infrastructure events and any that were blocked due to filters or limits.
- Infrastructure events are telemetry signals collected from your cloud and Kubernetes environments, such as node statuses, pod lifecycle events, and configuration metadata. These are used to populate Infrastructure Explorer.
- Blocked infrastructure events are those dropped before ingestion, usually due to namespace filters (e.g., excluding
kube-system) or fair usage constraints.
This information is essential for platform and DevOps teams to ensure the accuracy of Infrastructure Explorer, avoid unnecessary data loss, and fine-tune collection practices for maximum observability and cost-efficiency.
To monitor infrastructure ingestion trends and ensure you're operating within fair usage limits, navigate to Settings > Data Usage, then select the Infrastructure data tab at the top of the screen. This view provides a breakdown of all infrastructure events sent to Coralogix, along with how many were accepted or blocked.
At the top of the screen, you’ll see two high-level metrics:
- Total: Cumulative number of infrastructure events received during the selected date range.
- Daily max: Highest number of events sent in a single day.
Just below, a bar chart visualizes daily infrastructure ingestion. Each bar is split into two segments:
- The lighter orange section represents infrastructure events that were successfully processed and ingested.
- The darker orange section represents blocked events, which exceeded Coralogix’s fair usage limits and were dropped.
Blocked events do not appear in Infrastructure Explorer and are not included in the processed inventory. These limits are designed to ensure stability and performance for all users. By default, Coralogix allows up to 1 million infrastructure events per hour; beyond this threshold, additional events are discarded to avoid overload.
Avoiding event loss
To reduce unnecessary ingestion:
- Use Coralogix’s Helm chart to filter out system namespaces (e.g.,
kube-system) - Drop low-value event types such as
kind: Event
Scrolling further down, you'll find a detailed breakdown table showing the daily count of both accepted and blocked infrastructure events.
Note: Infrastructure events currently consume 0 units. However, this view helps you understand data patterns, identify spikes, and address ingestion inefficiencies proactively.
This data directly powers Infrastructure Explorer, which builds a live inventory of:
- Nodes
- Pods
- Containers
- Volumes
- Other infrastructure resources
By monitoring this usage screen, platform and DevOps teams can ensure Infrastructure Explorer remains accurate, responsive, and focused on the entities that matter most.
In summary, this view helps you:
- Understand how your infrastructure telemetry flows into Coralogix
- Track when and why data might be dropped
- Take corrective actions to improve observability and performance
If you consistently see high blocked event volumes, revisit your filters or refine what’s being collected.