Related org metrics for metrics pipeline management
Splunk Infrastructure Monitoring provides some metrics to help you measure your usage of metrics pipeline management and how it affects your subscription. For more information on how to view these metrics, see Access organization metrics.
Data point ingestion metrics
|
Metric name |
Description |
|---|---|
|
|
Total number of data points Infrastructure Monitoring ingested in your organization, including data points that were later dropped or aggregated by metrics pipeline management. |
|
|
Total number of data points Infrastructure Monitoring ingested for each token, including data points that were later dropped or aggregated by metrics pipeline management. |
|
|
Total number of data points that arrived at Infrastructure Monitoring for your organization, before metrics pipeline management processing, aggregation, or drops were applied. |
|
|
Total number of data points that arrived at Infrastructure Monitoring for each token, before metrics pipeline management processing, aggregation, or drops were applied. |
sf.org.numArchivedDatapointsReceived |
Number of data points that metrics pipeline management routed to archived metrics in your organization. |
sf.org.numSendToRTMFailure |
Number of data points that metrics pipeline management dropped due to an internal error while sending them to the real-time metrics system in your organization. |
Data point aggregation metrics
|
Metric name |
Description |
|---|---|
|
|
Number of data points metrics pipeline management aggregated based on configured rules in your organization |
|
|
One value per token, number of data points metrics pipeline management aggregated based on configured rules |
Data point dropping metrics
|
Metric name |
Description |
|---|---|
|
|
Number of data points metrics pipeline management dropped based on configured rules in your organization |
|
|
One value per token, number of data points metrics pipeline management dropped based on configured rules |
|
|
Number of data points metrics pipeline management dropped when the aggregation metrics are more than the limit configured for your organization |
|
|
One value per token, number of data points metrics pipeline management dropped when the aggregation metrics are more than the limit configured for your organization |
|
|
Number of data points Splunk Observability Cloud didn’t attempt to create because Splunk Observability Cloud throttled or limited your account in the previous few seconds, and creation was unlikely to succeed. |
|
|
Reserved for Infrastructure Monitoring internal use only. |
|
|
Number of new data points you sent to Infrastructure Monitoring but Infrastructure Monitoring didn’t accept because your organization exceeded its subscription limit. To learn more about the process Infrastructure Monitoring uses for incoming data when you exceed subscription limits, see Infrastructure Monitoring subscription usage (DPM plans). |
|
|
One value per token, number of new data points you sent to Infrastructure Monitoring but Infrastructure Monitoring didn’t accept because your organization exceeded its subscription limit. To learn more about the process Infrastructure Monitoring uses for incoming data when you exceed subscription limits, see Infrastructure Monitoring subscription usage (DPM plans). The sum of all the values might be less than the value of |
|
|
Number of data points you sent to Infrastructure Monitoring that Infrastructure Monitoring didn’t accept because your organization significantly exceeded its DPM limit. Unlike |
|
|
One value per token, number of data points you sent to Infrastructure Monitoring that Infrastructure Monitoring didn’t accept because your organization significantly exceeded its DPM limit. Unlike |
|
|
Number of data points dropped because they didn’t follow documented guidelines for data points. For example, the metric name was too long, the metric name included unsupported characters, or the data point contained no values. |
|
|
Number of data points dropped for a specific access token because they didn’t follow documented guidelines for data points. For example, the metric name was too long, the metric name included unsupported characters, or the data point contained no values. |
|
|
Number of data points dropped because a single request contained more than 100,000 data points. In this scenario, Splunk Observability Cloud drops data points because it perceives sending more than 100,000 data points in a single request as excessive. |
|
|
One value per token, number of data points dropped because a single request contained more than 100,000 data points. In this scenario, Splunk Observability Cloud drops data points because it perceives sending more than 100,000 data points in a single request as excessive. |
Data point retention metrics
|
Metric name |
Description |
|---|---|
|
|
One value per metric type, each representing the number of data points that Infrastructure Monitoring received and processed. The sum of the values represents the total number of data points you sent to Infrastructure Monitoring, minus any data points that weren’t accepted because you exceeded a limit. You can have up to three metric time series (MTS) for this metric. |
|
|
One value per metric type per token, each representing the number of data points Infrastructure Monitoring received and processed. The sum of values for a token is the total number of data points you sent to Infrastructure Monitoring, minus the number of data points that Infrastructure Monitoring didn’t accept because you exceeded a limit. You can have up to three MTS for this metric. |
Metric rulesets org metrics
|
Metric name |
Description |
|---|---|
|
|
Number of metric rulesets created in your organization |
|
|
Number of aggregations in your organization |
|
|
Number of metric rulesets with data dropping enabled in your organization |