Switch descriptions for metrics
* Switch descriptions for metrics
Doc feedback given in this JIRA ticket:
* Added period
* updated data resolution fields for swapped metrics
@@ -1120,28 +1120,28 @@ sf.org.numLimitedEventTimeSeriesCreateCallsByToken:
title: sf.org.numLimitedEventTimeSeriesCreateCallsByToken
sf.org.numLimitedMetricTimeSeriesCreateCalls:
- brief: Number of MTS not sent; over maximum allowed
+ brief: Number of MTS not created because your account reached a category limit (or subscription limit).
description: |
- One value per metric type, each representing the number of metric
- time series (MTS) not sent to Infrastructure Monitoring because you've reached your maximum limit for active
- MTS, hosts, containers, custom metrics, bundled metrics, functions, high-resolution metrics,
- Application Performance Monitoring (APM) metrics, or APM bundled metrics.
- You can have up to three MTS for this metric; each MTS is sent with a dimension
- named `category` with a value of "counter", "cumulative_counter", or "gauge". To
- learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type).
+ Number of metric time series (MTS) not created because your account reached a category limit (or subscription limit).
* Dimension(s): `category`, `orgId`
- * Data resolution: 1 second
+ * Data resolution: 10 seconds
metric_type: counter
title: sf.org.numLimitedMetricTimeSeriesCreateCalls
sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryType:
- brief: Number of MTS not created because your account reached a category limit (or subscription limit).
+ brief: Number of MTS not sent; over maximum allowed.
description: |
- Number of metric time series (MTS) not created because your account reached a category limit (or subscription limit).
+ One value per metric type, each representing the number of metric
+ time series (MTS) not sent to Infrastructure Monitoring because you've reached your maximum limit for active
+ MTS, hosts, containers, custom metrics, bundled metrics, functions, high-resolution metrics,
+ Application Performance Monitoring (APM) metrics, or APM bundled metrics.
+ You can have up to three MTS for this metric; each MTS is sent with a dimension
+ named `category` with a value of "counter", "cumulative_counter", or "gauge". To
+ learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type).
* Dimension(s): `categoryType`, `orgId`
- * Data resolution: 35 seconds
+ * Data resolution: 10 seconds
metric_type: counter
title: sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryType
