-
SuggestedSuggested
- How It Works Streama© is the foundation of Coralogix's stateful streaming data platform, based on our 3 “S” architecture – source, stream, and sink.
- How Monday.com Improved Monitoring to Spend Less Time Searching for Issues Monday.com uses Coralogix to centralize and standardize their logs so they can easily search their logs across the entire stack.
- Creating a Free Data Lake with Coralogix Like many cool tools out there, this project started from a request made by a customer of ours. Having recently migrated to our service, this customer...
Oh no!
Oh no!We didn’t find anything for “”,
please try a different search
Breaking News from AWS re:Invent
Coralogix receives AWS Rising Star award!
Data Usage Metrics
Enable Data Usage Metrics for an added layer of granularity in your data usage overview. Use this feature to create custom dashboards, insights, alerts, and useful summaries of your data.
Overview
The Data Usage Metrics feature creates three new metrics: GB Sent, Counted Units, and Daily Quota. These metrics are counted towards your team’s daily metrics quota. With these new metrics, you will be able to create custom dashboards, insights, alerts, and an overview of your data.
Enabling Data Usage Metrics
Enable the data usage metrics feature after having configured your s3 metrics bucket.
Once enabled, Coralogix begins an auto-populate process to provide data for the past 24 hours. This process may take up to two hours.
STEP 1. In the navigation bar, click Settings > Data Usage.
STEP 2. On the Data Usage page, toggle Enable data usage metrics.
- If you do not have a required S3 metrics bucket configured, the toggle will be disabled.
STEP 3. View your new data usage metrics using our custom dashboards. Metric names will appear as:
cx_data_usage_unitscx_data_usage_bytes_totalcx_data_plan_units_per_day
Step 4. Use the data usage metrics to define useful alerts to monitor your data consumption and quota.
Labels
The information gathered on the new metrics includes the following labels:
| Label | Description |
pillar | Type of traffic (logs, spans, metrics) in each data point |
subsystem_name | Subsystem that generated the traffic (used by the logs and spans pillars) |
application_name | Application that generated the traffic (used by the logs and spans pillars) |
priority | TCO priority (high, medium, low, blocked) |
severity | Log severity (critical, error, warn, info, debug, trace) used by the logs pillar |
blocking_reason_type | The reason why traffic was blocked. The value can be either tco_policy or parsing_rule. |
blocking_reason_name | The name of the TCO policy or parsing rule which is blocking traffic. |
Additional Resources
Support
Need help?
Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.
Feel free to reach out to us via our in-app chat or by sending us an email at [email protected].