Skip to content

Commit

Permalink
Fix link formatting
Browse files Browse the repository at this point in the history
  • Loading branch information
trangl-splunk committed Aug 22, 2023
1 parent 69c119c commit 4bb258c
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions signalfx-org-metrics/metrics.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -700,7 +700,7 @@ sf.org.num.awsServiceAuthErrorCount:
description: |
Total number authentication errors thrown by AWS services.
* Dimension(s): `integrationId`,`orgId`,`namespace` (AWS Cloudwatch namespace),`clientInterface` (AWS SDK Interface),`method` (AWS SDK method)
* Dimension(s): `integrationId`, `orgId`, `namespace` (AWS Cloudwatch namespace),`clientInterface` (AWS SDK Interface), `method` (AWS SDK method)
* Data resolution: 1 second
metric_type: gauge
title: sf.org.num.awsServiceAuthErrorCount
Expand Down Expand Up @@ -1323,17 +1323,16 @@ sf.org.numComputationsStartedByToken:
sf.org.numComputationsThrottled:
brief: Rate at which SignalFlow jobs are being throttled
description: |
The number of SignalFlow computations, which mostly consist of chart views and detectors, throttled because you reach the maximum number of SignalFlow jobs you can run for your organization. To learn more about this limit, see (Maximum number of SignalFlow jobs per organization)[https://docs.splunk.com/observability/admin/references/system-limits/sys-limits-infra.html#maximum-number-of-signalflow-jobs-per-organization].
The number of SignalFlow computations, which mostly consist of chart views and detectors, throttled because you reach the maximum number of SignalFlow jobs you can run for your organization. To learn more about this limit, see [Maximum number of SignalFlow jobs per organization](https://docs.splunk.com/observability/admin/references/system-limits/sys-limits-infra.html#maximum-number-of-signalflow-jobs-per-organization).
* Dimension(s): `orgId`
* Data resolution: 10 seconds
metric_type: counter
title: sf.org.numComputationsThrottled

sf.org.numComputationsThrottledByToken:
brief: Rate at which SignalFlow jobs are being throttled
description: |
One value per token. The number of computations, which mostly consist of chart views and detectors, throttled because you reach the maximum number of SignalFlow jobs you can run for your organization. To learn more about this limit, see (Maximum number of SignalFlow jobs per organization)[https://docs.splunk.com/observability/admin/references/system-limits/sys-limits-infra.html#maximum-number-of-signalflow-jobs-per-organization].
One value per token. The number of computations, which mostly consist of chart views and detectors, throttled because you reach the maximum number of SignalFlow jobs you can run for your organization. To learn more about this limit, see [Maximum number of SignalFlow jobs per organization](https://docs.splunk.com/observability/admin/references/system-limits/sys-limits-infra.html#maximum-number-of-signalflow-jobs-per-organization).
* Dimension(s): `orgId`, `tokenId`
* Data resolution: 10 seconds
Expand Down

0 comments on commit 4bb258c

Please sign in to comment.