copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2024-06-13 |
cloud-logs |
{{site.data.keyword.attribute-definition-list}}
{: #data-usage-metrics}
In {{site.data.keyword.logs_full_notm}}, you can enable data usage metrics to collect predefined metrics that you can use to monitor your data usage. Then, you can use these metrics in custom dashboards, insights, and alerts {: shortdesc}
{: #data-usage-metrics-prereqs}
To be able to enable data usage metrics, you must configure a metrics bucket.. {: note}
{: #data-usage-metrics-1}
Complete the following steps:
After you enable data usage metrics, it can take up to two hours to see metrics. {: note}
{: #data-usage-metrics-2}
The following pre-defined metric is available when you enable data usage metrics:
cx_data_usage_bytes_total
: Reports GB Sent.
In the Data Usage page in the UI, you can see the following information per day for the range of time that you select:
- Maximum bytes sent per day
- Total number of bytes sent
You can select data for the current month, the past 30 days, or the past 90 days.
{: #data-usage-metrics-3}
The information collected on these metrics includes the following labels:
tier
: Storage for logs. Valid values are:high
, andlow
.pillar
: Type of traffic. Valid values are:logs
, andmetrics
.severity
: Log severity. Valid values are:critical
,error
,warn
,info
,debug
, andtrace
.priority
: TCO priority. Valid values are:high
,medium
,low
, andblocked
.subsystem_name
: Host from where logs are generated.application_name
: Application that generates logs.blocking_reason_type
: The reason why traffic is blocked. Valid values are:tco_policy
orparsing_rule
.blocking_reason_name
: The name of the TCO policy or parsing rule which is blocking traffic.
{: #data-usage-metrics-next}
Check how you can generate data usage reports. For more information, see: