Skip to content

Commit

Permalink
Merge pull request #1631 from splunk/dg24078-remove-old-email
Browse files Browse the repository at this point in the history
[24078] Remove support email from related metrics table
  • Loading branch information
mbechtold-splunk authored Jan 2, 2024
2 parents 7f094a9 + 12214fb commit 0f0cb44
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions infrastructure/metrics-pipeline/related-metrics.rst
Original file line number Diff line number Diff line change
Expand Up @@ -83,10 +83,10 @@ Data point dropping metrics
- 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 :ref:`dpm-usage`. The sum of all the values might be less than the value of ``sf.org.numDatapointsDroppedExceededQuota``. For more information, see :new-page-ref:`metrics-by-token`.

* - ``sf.org.numDatapointsDroppedThrottle``
- Number of data points you sent to Infrastructure Monitoring that Infrastructure Monitoring didn't accept because your organization significantly exceeded its DPM limit. For help with this issue, reach out to support at observability-support@splunk.com. Unlike ``sf.org.numDatapointsDroppedExceededQuota``, this metric represents data points for both existing and new MTS. If Infrastructure Monitoring is throttling your organization, it isn't keeping any of your data.
- Number of data points you sent to Infrastructure Monitoring that Infrastructure Monitoring didn't accept because your organization significantly exceeded its DPM limit. Unlike ``sf.org.numDatapointsDroppedExceededQuota``, this metric represents data points for both existing and new MTS. If Infrastructure Monitoring is throttling your organization, it isn't keeping any of your data.

* - ``sf.org.numDatapointsDroppedThrottleByToken``
- 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. For help with this issue, reach out to support at observability-support@splunk.com. Unlike ``sf.org.numDatapointsDroppedExceededQuota``, this metric represents data points for both existing and new MTS. If Infrastructure Monitoring is throttling your organization, it isn't keeping any of your data. The sum of all the values might be less than the value of ``sf.org.numDatapointsDroppedThrottle``. For more information, see :new-page-ref:`metrics-by-token`.
- 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 ``sf.org.numDatapointsDroppedExceededQuota``, this metric represents data points for both existing and new MTS. If Infrastructure Monitoring is throttling your organization, it isn't keeping any of your data. The sum of all the values might be less than the value of ``sf.org.numDatapointsDroppedThrottle``. For more information, see :new-page-ref:`metrics-by-token`.

* - ``sf.org.numDatapointsDroppedInvalid``
- 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.
Expand Down

0 comments on commit 0f0cb44

Please sign in to comment.