From 778d1dfd3087f11abffc7ceaea7e6d58a90821f2 Mon Sep 17 00:00:00 2001 From: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Date: Mon, 25 Jul 2022 17:33:43 -0500 Subject: [PATCH 01/48] DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics --- signalfx-org-metrics/metrics.yaml | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 2c000c8b..133ec9b0 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -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 From 318655af199fdf7c9e6f13651aa4ea2ae816c77e Mon Sep 17 00:00:00 2001 From: bhillmer <86490494+bhillmer@users.noreply.github.com> Date: Thu, 4 Aug 2022 10:27:10 -0600 Subject: [PATCH 02/48] Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax --- signalfx-org-metrics/metrics.yaml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 133ec9b0..173c2882 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1145,6 +1145,22 @@ sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryType: metric_type: counter title: sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryType +sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken: + brief: Number of MTS not sent per token; over maximum allowed. + description: | + One value per metric type per token, 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 for values by token](#metrics-for-values-by-token). + + * Dimension(s): `categoryType`, `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken + sf.org.numLimitedMetricTimeSeriesCreateCallsByToken: brief: Per token of MTS not sent; over maximum allowed description: | From bee12adf906483f35795288da69ccd09c483425b Mon Sep 17 00:00:00 2001 From: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Date: Fri, 12 Aug 2022 10:12:28 -0500 Subject: [PATCH 03/48] DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml --- signalfx-org-metrics/metrics.yaml | 37 +++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 173c2882..719fead3 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1662,3 +1662,40 @@ sf.org.log.numContentBytesReceivedByToken: * Data resolution: 10 second metric_type: counter title: sf.org.log.numContentBytesReceivedByToken + +sf.org.subscription.hosts: + brief: Number of hosts. + description: | + Number of hosts. + + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.subscription.hosts + +sf.org.subscription.containers: + brief: Number of containers. + description: | + Number of containers. + + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.subscription.containers + + sf.org.subscription.customMetrics: + brief: Number of custom metric time series. + description: | + Number of custom metric time series. + + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.subscription.customMetrics + + sf.org.subscription.highResolutionMetrics: + brief: Number of high resolution metric time series. + description: | + Number of high resolution metric time series. + + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.subscription.highResolutionMetrics + From 6e1dce1d7947f80cfc79100d6bbc73033fde551f Mon Sep 17 00:00:00 2001 From: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> Date: Fri, 12 Aug 2022 11:50:52 -0400 Subject: [PATCH 04/48] Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. --- signalfx-org-metrics/metrics.yaml | 37 ------------------------------- 1 file changed, 37 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 719fead3..173c2882 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1662,40 +1662,3 @@ sf.org.log.numContentBytesReceivedByToken: * Data resolution: 10 second metric_type: counter title: sf.org.log.numContentBytesReceivedByToken - -sf.org.subscription.hosts: - brief: Number of hosts. - description: | - Number of hosts. - - * Data resolution: 10 seconds - metric_type: gauge - title: sf.org.subscription.hosts - -sf.org.subscription.containers: - brief: Number of containers. - description: | - Number of containers. - - * Data resolution: 10 seconds - metric_type: gauge - title: sf.org.subscription.containers - - sf.org.subscription.customMetrics: - brief: Number of custom metric time series. - description: | - Number of custom metric time series. - - * Data resolution: 10 seconds - metric_type: gauge - title: sf.org.subscription.customMetrics - - sf.org.subscription.highResolutionMetrics: - brief: Number of high resolution metric time series. - description: | - Number of high resolution metric time series. - - * Data resolution: 10 seconds - metric_type: gauge - title: sf.org.subscription.highResolutionMetrics - From 564d0a17d239f7410ba4d99ed151bfc48b0cf9bc Mon Sep 17 00:00:00 2001 From: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Date: Fri, 12 Aug 2022 11:17:53 -0500 Subject: [PATCH 05/48] Update metrics.yaml (#970) --- signalfx-org-metrics/metrics.yaml | 36 +++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 173c2882..b92ca988 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1662,3 +1662,39 @@ sf.org.log.numContentBytesReceivedByToken: * Data resolution: 10 second metric_type: counter title: sf.org.log.numContentBytesReceivedByToken + +sf.org.subscription.containers: + brief: Number of containers. + description: | + Number of containers. + + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.subscription.containers + +sf.org.subscription.customMetrics: + brief: Number of custom metric time series. + description: | + Number of custom metric time series. + + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.subscription.customMetrics + +sf.org.subscription.highResolutionMetrics: + brief: Number of high resolution metric time series. + description: | + Number of high resolution metric time series. + + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.subscription.highResolutionMetrics + +sf.org.subscription.hosts: + brief: Number of hosts. + description: | + Number of hosts. + + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.subscription.hosts From 1cc65a7451f31fd712b97db04e178e0167d6d441 Mon Sep 17 00:00:00 2001 From: Joe Malin Date: Mon, 15 Aug 2022 14:55:21 -0700 Subject: [PATCH 06/48] Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup --- signalfx-org-metrics/README.md.jinja | 2 ++ signalfx-org-metrics/metrics.yaml | 38 +++++++++++++++++++--------- 2 files changed, 28 insertions(+), 12 deletions(-) diff --git a/signalfx-org-metrics/README.md.jinja b/signalfx-org-metrics/README.md.jinja index 61be408e..e10c68ee 100644 --- a/signalfx-org-metrics/README.md.jinja +++ b/signalfx-org-metrics/README.md.jinja @@ -88,6 +88,8 @@ These metrics track limits that Infrastructure Monitoring enforces for your orga new MTS, but continues to accept data points for existing MTS. To monitor your usage against the limit, use the `metric sf.org.numActiveTimeSeries`. + The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. + * `sf.org.limit.metricTimeSeriesCreatedPerMinute` (gauge): Maximum rate at which you can create new MTS in your organization, measured in MTS per minute. If you exceed this rate, Infrastructure Monitoring stops accepting data points for new MTS, but continues to accept data points for existing MTS. diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index b92ca988..c47bc4d5 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -706,10 +706,13 @@ sf.org.numActiveTimeSeries: brief: Number of currently active MTS description: | Total number of metric time series (MTS) currently active in the organization. + + The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. + (Use `sf.org.numInactiveTimeSeries` to see how many MTS are not active.) - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: gauge title: sf.org.numActiveTimeSeries @@ -1087,10 +1090,14 @@ sf.org.numInactiveTimeSeries: brief: Number of inactive MTS description: | Total number of previously active metric time series (MTS) that are - no longer active. Use `sf.org.numActiveTimeSeries` to see how many MTS are active. + no longer active. The total number of inactive MTS is the total number of metric time series (MTS) that haven't received + any data points in the last 25 hours. You can still find these MTS in Observability Cloud until they expire. + The standard retention period is 13 months. + + Use `sf.org.numActiveTimeSeries` to see how many MTS are active. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: gauge title: sf.org.numInactiveTimeSeries @@ -1168,14 +1175,17 @@ sf.org.numLimitedMetricTimeSeriesCreateCallsByToken: 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. + + The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. + 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). The sum of all the values might be less than the value of `sf.org.numLimitedMetricTimeSeriesCreateCalls`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - - * Dimension(s): `category, orgId, tokenId` - * Data resolution: 1 second + + * Dimension(s): `category, orgId, tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numLimitedMetricTimeSeriesCreateCallsByToken @@ -1209,11 +1219,11 @@ sf.org.numMetadataWritesThrottled: metric_type: null title: sf.org.numMetadataWritesThrottled -sf.org.numMetadataWrttesThrottledByToken: +sf.org.numMetadataWritesThrottledByToken: brief: Infrastructure Monitoring internal metric description: Reserved for Infrastructure Monitoring internal use only. metric_type: null - title: sf.org.numMetadataWrttesThrottledByToken + title: sf.org.numMetadataWritesThrottledByToken sf.org.numMetricTimeSeriesCreated: brief: Number of MTS created @@ -1417,8 +1427,10 @@ sf.org.subscription.activeTimeSeries: brief: Maximum number of active MTS description: | Maximum number of active metric time series (MTS). + + The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. - * Data resolution: 15 minutes + * Data resolution: 15 minutes metric_type: gauge title: sf.org.subscription.activeTimeSeries @@ -1430,7 +1442,7 @@ sf.org.subscription.datapointsPerMinute: * Data resolution: 15 minutes metric_type: gauge - title: sf.org.suscription.datapointsPerMinute + title: sf.org.subscription.datapointsPerMinute sf.org.ui.num.pagevisits: brief: Infrastructure Monitoring internal metric @@ -1445,6 +1457,8 @@ sf.org.limit.activeTimeSeries: that your organization can have. If you exceed this limit, Infrastructure Monitoring stops accepting data points for new MTS, but continues to accept data points for existing MTS. To monitor your usage against the limit, use the `metric sf.org.numActiveTimeSeries`. + + The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. metric_type: gauge title: sf.org.limit.activeTimeSeries From 51f61dcb4004476cdf207b8767af193e774fb1b8 Mon Sep 17 00:00:00 2001 From: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Date: Mon, 22 Aug 2022 11:41:20 -0500 Subject: [PATCH 07/48] DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml --- signalfx-org-metrics/metrics.yaml | 35 +++++++++++++++++++++++++------ 1 file changed, 29 insertions(+), 6 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index c47bc4d5..004bc8e1 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1300,6 +1300,19 @@ sf.org.numPropertyLimitedMetricTimeSeriesCreateCallsByToken: metric_type: counter title: sf.org.numPropertyLimitedMetricTimeSeriesCreateCallsByToken +sf.org.numResourceMetrics: + brief: Number of resource metric time series (MTS) monitored. + description: | + Number of resource metric time series (MTS) received from host and container + categories. + + The `resourceType` dimension indicates whether the value represents hosts or containers. + + * Dimension(s): `orgId`, `resourceType` + * Data resolution: 10 minutes + metric_type: gauge + title: sf.org.numResourceMetrics + sf.org.numResourcesMonitored: brief: Number of host-based resources monitored description: | @@ -1680,25 +1693,25 @@ sf.org.log.numContentBytesReceivedByToken: sf.org.subscription.containers: brief: Number of containers. description: | - Number of containers. + Number of containers included in the subscription. * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.containers sf.org.subscription.customMetrics: - brief: Number of custom metric time series. + brief: Number of custom metric time series (MTS). description: | - Number of custom metric time series. + Number of custom metric time series (MTS) included in the subscription. * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.customMetrics sf.org.subscription.highResolutionMetrics: - brief: Number of high resolution metric time series. + brief: Number of high resolution metric time series (MTS). description: | - Number of high resolution metric time series. + Number of high resolution metric time series (MTS) included in the subscription. * Data resolution: 10 seconds metric_type: gauge @@ -1707,8 +1720,18 @@ sf.org.subscription.highResolutionMetrics: sf.org.subscription.hosts: brief: Number of hosts. description: | - Number of hosts. + Number of hosts included in the subscription. * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.hosts + +sf.org.subscription.function: + brief: Number of functions. + description: | + Number of serverless functions included in the subscription. + + * Data resolution: 2 minutes + metric_type: gauge + title: sf.org.subscription.function + From fac22ca9664ed6851925667e9395f1df176ba4ba Mon Sep 17 00:00:00 2001 From: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Date: Wed, 7 Sep 2022 12:55:12 -0700 Subject: [PATCH 08/48] Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. --- signalfx-agent/agent_docs/monitors/vsphere.md | 3 +++ vsphere/dimensions.yaml | 4 ++++ vsphere/smart_agent_config.yaml | 17 +++++++++++++++++ 3 files changed, 24 insertions(+) diff --git a/signalfx-agent/agent_docs/monitors/vsphere.md b/signalfx-agent/agent_docs/monitors/vsphere.md index b424b7e3..8df451c9 100644 --- a/signalfx-agent/agent_docs/monitors/vsphere.md +++ b/signalfx-agent/agent_docs/monitors/vsphere.md @@ -68,9 +68,11 @@ Configuration](../monitor-config.html#common-configuration).** | `inventoryRefreshInterval` | no | `int64` | How often to reload the inventory and inventory metrics (**default:** `60s`) | | `perfBatchSize` | no | `integer` | Maximum number of inventory objects to be queried for performance data per request. Set this value to zero (0) to request performance data for all inventory objects at a time. (**default:** `10`) | | `filter` | no | `string` | An 'expr' expression to limit the inventory traversed by the monitor. Leave blank or omit to traverse and get metrics for the entire vSphere inventory. Otherwise, this expression is evaluated per cluster. If the expression evaluates to true, metrics are collected for the objects in the cluster, otherwise it is skipped. Made available to the expr expression environment are the variables: `Datacenter` and `Cluster`. For example: filter: "Datacenter == 'MyDatacenter' && Cluster == 'MyCluster'" The above expr value will cause metrics collection for only the given datacenter + cluster. See https://github.com/antonmedv/expr for more advanced syntax. | +| `vmHostDimension` | no | `string` | The host dimension value set for monitored VMs. The options are: `ip`, `hostname` and `disable`. Default is `ip`. `ip` : the VM IP if available `hostname` : the VM Hostname if available `disable` : the vsphere monitor does not set the host dimension on the VM metrics (**default:** `ip`) | | `tlsCACertPath` | no | `string` | Path to the ca file | | `tlsClientCertificatePath` | no | `string` | Configure client certs. Both tlsClientKeyPath and tlsClientCertificatePath must be present. The files must contain PEM encoded data. Path to the client certificate | | `tlsClientKeyPath` | no | `string` | Path to the keyfile | +| `soapClientDebug` | no | `bool` | When set to true, all the SOAP requests and responses will be logged. This generates lots of data, only use it for debugging. For this setting to take effect, make sure to restart the agent (**default:** `false`) | ## Metrics @@ -362,6 +364,7 @@ dimensions may be specific to certain metrics. | `guest_family` | For virtual machine metrics, the guest operating system family for the virtual machine to which this metric pertains. For example 'linuxGuest'. | | `guest_fullname` | For virtual machine metrics, the full name of the guest operating system for the virtual machine to which the metric pertains. For example 'Windows 2000 Professional'. | | `guest_id` | For virtual machine metrics, the guest identifier of the virtual machine to which the metric pertains. | +| `host` | For virtual machine metrics, the host dimension will be set to the VM IP instead of the running agent hostname. This behavior is configurable; check the `vmHostDimension` option for details. | | `object` | For some metrics, the source of the metric. For example, the identifier of a NIC for a network metric, or the processor number for a CPU metric. | | `object_type` | The type of the resource to which the metric pertains. Values can be 'VirtualMachine' for a VM, or 'HostSystem' for an ESX host. | | `ref_id` | The unique vCenter identifier for the resource to which the metric pertains. | diff --git a/vsphere/dimensions.yaml b/vsphere/dimensions.yaml index 127cb6d6..0ecdee6f 100644 --- a/vsphere/dimensions.yaml +++ b/vsphere/dimensions.yaml @@ -17,6 +17,10 @@ guest_fullname: For virtual machine metrics, the full name of the guest operatin guest_id: For virtual machine metrics, the guest identifier of the virtual machine to which the metric pertains. +host: For virtual machine metrics, the host dimension will be set to the VM IP instead + of the running agent hostname. This behavior is configurable; check the `vmHostDimension` + option for details. + object: For some metrics, the source of the metric. For example, the identifier of a NIC for a network metric, or the processor number for a CPU metric. diff --git a/vsphere/smart_agent_config.yaml b/vsphere/smart_agent_config.yaml index a37b4c23..ba563023 100644 --- a/vsphere/smart_agent_config.yaml +++ b/vsphere/smart_agent_config.yaml @@ -59,6 +59,15 @@ vsphere: required: false type: string yamlName: filter + - default: ip + doc: 'The host dimension value set for monitored VMs. The options are: `ip`, `hostname` + and `disable`. Default is `ip`. `ip` : the VM IP if available `hostname` + : the VM Hostname if available `disable` : the vsphere monitor does not set + the host dimension on the VM metrics' + elementKind: '' + required: false + type: string + yamlName: vmHostDimension - default: '' doc: Path to the ca file elementKind: '' @@ -79,3 +88,11 @@ vsphere: required: false type: string yamlName: tlsClientKeyPath + - default: 'false' + doc: When set to true, all the SOAP requests and responses will be logged. This + generates lots of data, only use it for debugging. For this setting to take + effect, make sure to restart the agent + elementKind: '' + required: false + type: bool + yamlName: soapClientDebug From 306e5d78300bf68894a0a9f309851e90d8e3d5a9 Mon Sep 17 00:00:00 2001 From: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Date: Fri, 9 Sep 2022 13:12:29 -0400 Subject: [PATCH 09/48] Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) --- signalfx-org-metrics/metrics.yaml | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 004bc8e1..5c6bc05e 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -370,6 +370,16 @@ sf.org.num.alertmuting: metric_type: gauge title: sf.org.num.alertmuting +sf.org.num.awsServiceAuthErrorCount + brief: Authentication errors thrown by AWS services + 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) + * Data resolution: 1 second + metric_type: gauge + title: sf.org.num.awsServiceAuthErrorCount + sf.org.num.awsServiceCallCount: brief: Number of calls made to the Amazon API description: | @@ -382,7 +392,7 @@ sf.org.num.awsServiceCallCount: title: sf.org.num.awsServiceCallCount sf.org.num.awsServiceCallCountExceptions: - brief: Number of Amazon API calls that threw exceptions + brief: Number of Amazon API calls that threw exceptions description: | Number of calls made to the Amazon API that threw exceptions. From f1fd8b7b4d01ce992f4501231bf5b4294acea262 Mon Sep 17 00:00:00 2001 From: Joe Malin Date: Fri, 9 Sep 2022 21:21:20 -0700 Subject: [PATCH 10/48] DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml --- signalfx-org-metrics/metrics.yaml | 145 +++++++++++++++--------------- 1 file changed, 72 insertions(+), 73 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 5c6bc05e..5a88d356 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -370,13 +370,13 @@ sf.org.num.alertmuting: metric_type: gauge title: sf.org.num.alertmuting -sf.org.num.awsServiceAuthErrorCount +sf.org.num.awsServiceAuthErrorCount: brief: Authentication errors thrown by AWS services 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) - * Data resolution: 1 second + + * 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 @@ -1187,7 +1187,7 @@ sf.org.numLimitedMetricTimeSeriesCreateCallsByToken: Application Performance Monitoring (APM) metrics, or APM bundled metrics. The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. - + 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). @@ -1543,160 +1543,160 @@ sf.org.limit.metricTimeSeriesCreatedPerMinute: sf.org.log.numMessagesReceived: brief: The total number of log messages Splunk Log Observer accepts after filtering and throttling. description: | - The total number of log messages Splunk Log Observer accepts after filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The total number of log messages Splunk Log Observer accepts after filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesReceived sf.org.log.numContentBytesReceived: brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. description: | - The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numContentBytesReceived sf.org.log.grossMessagesReceived: brief: The total number of log messages Splunk Log Observer receives before filtering and throttling. description: | - The total number of log messages Splunk Log Observer receives before filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The total number of log messages Splunk Log Observer receives before filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossMessagesReceived sf.org.log.numMessageBytesReceived: brief: The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. description: | - The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessageBytesReceived sf.org.log.grossContentBytesReceived: brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. description: | - The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossContentBytesReceived sf.org.log.numMessagesReceivedByToken: brief: The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. description: | - The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesReceivedByToken sf.org.log.numMessagesDroppedOversize: brief: The number of log messages Splunk Log Observer receives that are too large to process. description: | - The number of log messages Splunk Log Observer receives that are too large to process. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The number of log messages Splunk Log Observer receives that are too large to process. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesDroppedOversize sf.org.log.numMessagesDroppedThrottle: brief: The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. description: | - The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesDroppedThrottle sf.org.log.grossMessageBytesReceived: brief: The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. description: | - The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossMessageBytesReceived sf.org.log.numMessagesDroppedOversizeByToken: brief: The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. description: | - The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesDroppedOversizeByToken sf.org.log.grossContentBytesReceivedByToken: brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. description: | - The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossContentBytesReceivedByToken sf.org.log.numMessagesDroppedThrottleByToken: brief: The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. description: | - The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesDroppedThrottleByToken sf.org.log.grossMessageBytesReceivedByToken: brief: The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression but before filtering and throttling are complete. description: | - The number of bytes received by Splunk Log Observer for a specific access token from ingested logs after decompression but before filtering and throttling are complete. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The number of bytes received by Splunk Log Observer for a specific access token from ingested logs after decompression but before filtering and throttling are complete. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossMessageBytesReceivedByToken sf.org.log.numMessageBytesReceivedByToken: brief: The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. description: | - The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessageBytesReceivedByToken sf.org.log.grossMessagesReceivedByToken: brief: The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. description: | - The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossMessagesReceivedByToken sf.org.log.numContentBytesReceivedByToken: brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. description: | - The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. - - * Dimension(s): `orgId` - * Data resolution: 10 second + The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. + + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numContentBytesReceivedByToken @@ -1722,11 +1722,11 @@ sf.org.subscription.highResolutionMetrics: brief: Number of high resolution metric time series (MTS). description: | Number of high resolution metric time series (MTS) included in the subscription. - + * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.highResolutionMetrics - + sf.org.subscription.hosts: brief: Number of hosts. description: | @@ -1735,7 +1735,7 @@ sf.org.subscription.hosts: * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.hosts - + sf.org.subscription.function: brief: Number of functions. description: | @@ -1744,4 +1744,3 @@ sf.org.subscription.function: * Data resolution: 2 minutes metric_type: gauge title: sf.org.subscription.function - From f015aa6e4ac1866a4e9d09b2e3f7fc65463d6945 Mon Sep 17 00:00:00 2001 From: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Date: Mon, 17 Oct 2022 12:34:46 -0400 Subject: [PATCH 11/48] Update metrics.yaml (#980) --- postgresql/metrics.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/postgresql/metrics.yaml b/postgresql/metrics.yaml index 8e284bad..8f37ceaa 100644 --- a/postgresql/metrics.yaml +++ b/postgresql/metrics.yaml @@ -108,7 +108,7 @@ postgres_query_time: brief: Total time taken to execute queries on the `database`, broken down by `user` custom: false description: Total time taken to execute queries on the `database`, broken down - by `user`. + by `user`. Measured in ms unless otherwise indicated. metric_type: cumulative monitor: postgresql title: postgres_query_time From 6644b7ca1fd22e704fa19e3cd342b2cfb9951c26 Mon Sep 17 00:00:00 2001 From: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Date: Tue, 18 Oct 2022 11:33:33 -0400 Subject: [PATCH 12/48] fixed typos (#982) --- signalfx-agent/agent_docs/monitors/collectd-genericjmx.md | 2 +- signalfx-metadata/README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/signalfx-agent/agent_docs/monitors/collectd-genericjmx.md b/signalfx-agent/agent_docs/monitors/collectd-genericjmx.md index 8ad98a2d..d40688c5 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-genericjmx.md +++ b/signalfx-agent/agent_docs/monitors/collectd-genericjmx.md @@ -108,7 +108,7 @@ The easiest thing to do here is to make sure the `com.sun.management.jmxremote.rmi.port` property in your Java app is set to the same port as the JMX connect port. There may be other variations of this that say `Connection reset` or `Connection refused` but they all -generaly indicate a similar cause. +generally indicate a similar cause. ## Configuration diff --git a/signalfx-metadata/README.md b/signalfx-metadata/README.md index 36ec4dba..23270e48 100644 --- a/signalfx-metadata/README.md +++ b/signalfx-metadata/README.md @@ -66,8 +66,8 @@ For more information on authentication, see the API's [Authentication documentat | configuration option | definition | default value | | ---------------------|------------|---------------| | ModulePath | Path on disk where collectd can find this module. | "/opt/signalfx-collectd-plugin" | -| URL | URL for where metrics are sent from collectd. If you are looking to limit the number of connections from your infrastructure to the SignalFx service you can optioally configure the use of the SignalFx metricproxy | "https://ingest.us0.signalfx.com/v1/collectd" | -| Token | Your SignalFx Organization Acess Token | none | +| URL | URL for where metrics are sent from collectd. If you are looking to limit the number of connections from your infrastructure to the SignalFx service you can optionally configure the use of the SignalFx metricproxy | "https://ingest.us0.signalfx.com/v1/collectd" | +| Token | Your SignalFx Organization Access Token | none | | LogTraces | Enable log traces | true | | Notifications | Enable notification on this plugin | true | | NotifyLevel | Set the notification level | "OKAY" | From 8698726458c3a1546bfc11b40dc8c276e37be8bb Mon Sep 17 00:00:00 2001 From: bhillmer <86490494+bhillmer@users.noreply.github.com> Date: Wed, 19 Oct 2022 13:22:07 -0600 Subject: [PATCH 13/48] merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> From f5335ab7e9b32ad86a3208f06c2d4d8c100e4ec3 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Mon, 14 Nov 2022 16:50:38 +0100 Subject: [PATCH 14/48] [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates --- signalfx-org-metrics/metrics.yaml | 632 ++++++++++++++++-------------- 1 file changed, 335 insertions(+), 297 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index ab26ae54..9f6a6169 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1,3 +1,72 @@ +sf.org.apm.grossContentBytesReceived: + brief: The volume of bytes Splunk APM receives off the wire before filtering + and throttling. + description: | + The volume of bytes Splunk APM receives off the wire before filtering + and throttling. This content could be compressed. + + * Dimension(s): `orgId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.grossContentBytesReceived + +sf.org.apm.grossSpanBytesReceived: + brief: The number of bytes Splunk APM receives from spans after decompression + but before filtering and throttling. + description: | + The number of bytes Splunk APM receives from spans after + decompression but before filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.grossSpanBytesReceived + +sf.org.apm.grossSpanBytesReceivedByToken: + brief: The number of bytes Splunk APM receives for a specific access token + from ingested span data after decompression but before filtering and + throttling. + description: | + The number of bytes Splunk APM receives for a specific access token + from ingested span data after decompression but before filtering and throttling. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.grossSpanBytesReceivedByToken + +sf.org.apm.grossSpansReceived: + brief: The number of spans Splunk APM received before filtering and throttling. + description: | + The number of spans Splunk APM received before filtering or throttling. + + * Dimension(s): `orgId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.grossSpansReceived + +sf.org.apm.ingestLatency.duration.ns.min: + brief: The minimum duration of the ingest latency in Splunk APM. + description: | + The minimum duration of the ingest latency in Splunk APM. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.apm.ingestLatency.duration.ns.min + +sf.org.apm.limit.spanBytes: + brief: The ingested span data limit in Splunk APM. + description: The ingested span data limit in Splunk APM. + metric_type: gauge + title: sf.org.apm.limit.spanBytes + +sf.org.apm.limit.troubleshootingMetricSets: + brief: The limit for troubleshooting Metric Sets in Splunk APM. + description: The limit for troubleshooting Metric Sets in Splunk APM. + metric_type: gauge + title: sf.org.apm.limit.troubleshootingMetricSets + sf.org.apm.numAddSpansCalls: brief: The number of calls to the `/v2/trace` endpoint. description: | @@ -37,18 +106,6 @@ sf.org.apm.numHosts: metric_type: gauge title: sf.org.apm.numHosts -sf.org.apm.grossSpanBytesReceived: - brief: The number of bytes Splunk APM receives from spans after decompression - but before filtering and throttling. - description: | - The number of bytes Splunk APM receives from spans after - decompression but before filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.apm.grossSpanBytesReceived - sf.org.apm.numSpanBytesReceived: brief: The number of bytes Splunk APM accepts from ingested span data after decompression after filtering and throttling. @@ -61,19 +118,6 @@ sf.org.apm.numSpanBytesReceived: metric_type: counter title: sf.org.apm.numSpanBytesReceived -sf.org.apm.grossSpanBytesReceivedByToken: - brief: The number of bytes Splunk APM receives for a specific access token - from ingested span data after decompression but before filtering and - throttling. - description: | - The number of bytes Splunk APM receives for a specific access token - from ingested span data after decompression but before filtering and throttling. - - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.apm.grossSpanBytesReceivedByToken - sf.org.apm.numSpanBytesReceivedByToken: brief: The number of bytes Splunk APM accepts for a specific access token for a span after decompression after filtering and throttling. @@ -157,25 +201,27 @@ sf.org.apm.numSpansDroppedThrottleByToken: metric_type: counter title: sf.org.apm.numSpansDroppedThrottleByToken -sf.org.apm.grossSpansReceived: - brief: The number of spans Splunk APM received before filtering and throttling. +sf.org.apm.numSpansReceived: + brief: The number of spans Splunk APM accepts after filtering and throttling. description: | - The number of spans Splunk APM received before filtering or throttling. + The number of spans Splunk APM accepts after filtering and throttling. * Dimension(s): `orgId` * Data resolution: 1 second metric_type: counter - title: sf.org.apm.grossSpansReceived + title: sf.org.apm.numSpansReceived -sf.org.apm.numSpansReceived: - brief: The number of spans Splunk APM accepts after filtering and throttling. +sf.org.apm.numSpansReceivedByToken: + brief: The number of spans Splunk APM received for a specific access token + after filtering and throttling. description: | - The number of spans Splunk APM accepts after filtering and throttling. + The number of spans Splunk APM received for a specific access token + after filtering and throttling. - * Dimension(s): `orgId` + * Dimension(s): `orgId`, `tokenId` * Data resolution: 1 second metric_type: counter - title: sf.org.apm.numSpansReceived + title: sf.org.apm.numSpansReceivedByToken sf.org.apm.grossSpansReceivedByToken: brief: The number of spans Splunk APM receives for a specific access token @@ -189,18 +235,6 @@ sf.org.apm.grossSpansReceivedByToken: metric_type: counter title: sf.org.apm.grossSpansReceivedByToken -sf.org.apm.numSpansReceivedByToken: - brief: The number of spans Splunk APM received for a specific access token - after filtering and throttling. - description: | - The number of spans Splunk APM received for a specific access token - after filtering and throttling. - - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.apm.numSpansReceivedByToken - sf.org.apm.subscription.containers: brief: The entitlement for the number of containers for your host-based subscription plan. description: | @@ -291,18 +325,6 @@ sf.org.apm.numTroubleshootingMetricSets: metric_type: counter title: sf.org.apm.numTroubleshootingMetricSets -sf.org.apm.grossContentBytesReceived: - brief: The volume of bytes Splunk APM receives off the wire before filtering - and throttling. - description: | - The volume of bytes Splunk APM receives off the wire before filtering - and throttling. This content could be compressed. - - * Dimension(s): `orgId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.apm.grossContentBytesReceived - sf.org.apm.numContentBytesReceived: brief: The volume of bytes Splunk APM accepts off the wire after filtering and throttling. @@ -346,18 +368,261 @@ sf.org.abortedDetectors: or data points, whichever caused the detector to stop metric_type: cumulative title: sf.org.abortedDetectors - + +sf.org.datapointsTotalCountByToken: + brief: Total datapoints by token + description: | + Total datapoints by token + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.datapointsTotalCountByToken + sf.org.grossDatapointsReceived: brief: Infrastructure Monitoring internal metric description: sf.org.grossDatapointsReceived is reserved for Infrastructure Monitoring internal use only. metric_type: cumulative title: sf.org.grossDatapointsReceived -sf.org.grossDatapointsReceivedByToken: - brief: Infrastructure Monitoring internal metric - description: sf.org.grossDatapointsReceivedByToken is reserved for Infrastructure Monitoring internal use only. - metric_type: cumulative - title: sf.org.grossDatapointsReceivedByToken +sf.org.grossDatapointsReceivedByToken: + brief: Infrastructure Monitoring internal metric + description: sf.org.grossDatapointsReceivedByToken is reserved for Infrastructure Monitoring internal use only. + metric_type: cumulative + title: sf.org.grossDatapointsReceivedByToken + +sf.org.grossDpmContentBytesReceived: + brief: Infrastructure Monitoring internal metric + description: sf.org.grossDpmContentBytesReceived is reserved for Infrastructure Monitoring internal use only. + metric_type: counter + title: sf.org.grossDpmContentBytesReceived + +sf.org.limit.activeTimeSeries: + brief: Number of active MTS allowed for your organization + description: | + Maximum number of active MTS, within a moving window of the past 25 hours, + that your organization can have. If you exceed this limit, Infrastructure Monitoring stops accepting data points for + new MTS, but continues to accept data points for existing MTS. To monitor your usage against the limit, + use the `metric sf.org.numActiveTimeSeries`. + + The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. + metric_type: gauge + title: sf.org.limit.activeTimeSeries + +sf.org.limit.containers: + brief: Maximum number of containers that can send data to your organization + description: | + Maximum number of containers that can send data to your + organization. This limit is higher than your contractual limit to allow for burst and overage usage. + If you exceed this limit, Infrastructure Monitoring drops datapoints from new containers but keeps + accepting data points for existing containers. To monitor your usage against the limit, use the metric + `sf.org.numResourcesMonitored` and filter for the dimension `resourceType:containers`. + metric_type: gauge + title: sf.org.limit.containers + +sf.org.limit.customMetricTimeSeries: + brief: Maximum number of active custom MTS you can have in your organization within a 1 hour time window + description: | + Maximum number of active custom MTS, within a moving window of the + previous 60 minutes, that you're allowed to have in your organization. If you exceed this limit, + Infrastructure Monitoring stops accepting data points for new custom MTS, but it continues to accept + data points for custom MTS that already existed. To see the number of MTS you're allowed to have, use the metric + `sf.org.numCustomMetrics`. To learn more about custom MTS, see the section + [About custom, bundled, and high-resolution metrics](https://docs.splunk.com/Observability/admin/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) + in the user documentation. + metric_type: gauge + title: sf.org.limit.customMetricTimeSeries + +sf.org.limit.detector: + brief: Maximum number of detectors you can use for your organization + description: | + Maximum number of detectors you can use for your organization. After you reach this limit, + you can't create more new detectors. + To monitor the number of detectors you create, + use the metric `sf.org.num.detector`. + metric_type: gauge + title: sf.org.limit.detector + +sf.org.limit.hosts: + brief: Maximum number of hosts that can send data to your organization + description: | + Maximum number of hosts that can send data to your organization. + This limit is higher than your contractual limit to allow for burst and overage usage. + If you exceed this limit, Infrastructure Monitoring drops data points from new hosts but + keeps accepting data points for existing hosts. To monitor your usage against the limit, use the metric + `sf.org.numResourcesMonitored` and filter for the dimension `resourceType:hosts`. + metric_type: gauge + title: sf.org.limit.hosts + +sf.org.limit.metricTimeSeriesCreatedPerMinute: + brief: Number of MTS you can create per minute + description: | + Maximum rate at which you can create new MTS + in your organization, measured in MTS per minute. If you exceed this rate, + Infrastructure Monitoring stops accepting data points for new MTS, but continues to accept data points for existing MTS. + To monitor the number of metrics you've created overall, use the metric `sf.org.numMetricTimeSeriesCreated`. + metric_type: gauge + title: sf.org.limit.metricTimeSeriesCreatedPerMinute + +sf.org.log.grossContentBytesReceived: + brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. + description: | + The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.grossContentBytesReceived + +sf.org.log.grossContentBytesReceivedByToken: + brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. + description: | + The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.grossContentBytesReceivedByToken + +sf.org.log.grossMessageBytesReceived: + brief: The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. + description: | + The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.grossMessageBytesReceived + +sf.org.log.grossMessageBytesReceivedByToken: + brief: The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression but before filtering and throttling are complete. + description: | + The number of bytes received by Splunk Log Observer for a specific access token from ingested logs after decompression but before filtering and throttling are complete. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.grossMessageBytesReceivedByToken + +sf.org.log.grossMessagesReceived: + brief: The total number of log messages Splunk Log Observer receives before filtering and throttling. + description: | + The total number of log messages Splunk Log Observer receives before filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.grossMessagesReceived + +sf.org.log.grossMessagesReceivedByToken: + brief: The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. + description: | + The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.grossMessagesReceivedByToken + +sf.org.log.numContentBytesReceived: + brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. + description: | + The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numContentBytesReceived + +sf.org.log.numContentBytesReceivedByToken: + brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. + description: | + The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numContentBytesReceivedByToken + +sf.org.log.numMessageBytesReceived: + brief: The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. + description: | + The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numMessageBytesReceived + +sf.org.log.numMessageBytesReceivedByToken: + brief: The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. + description: | + The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numMessageBytesReceivedByToken + +sf.org.log.numMessagesDroppedThrottle: + brief: The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. + description: | + The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numMessagesDroppedThrottle + +sf.org.log.numMessagesDroppedOversize: + brief: The number of log messages Splunk Log Observer receives that are too large to process. + description: | + The number of log messages Splunk Log Observer receives that are too large to process. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numMessagesDroppedOversize + +sf.org.log.numMessagesDroppedOversizeByToken: + brief: The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. + description: | + The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numMessagesDroppedOversizeByToken + +sf.org.log.numMessagesDroppedThrottleByToken: + brief: The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. + description: | + The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numMessagesDroppedThrottleByToken + +sf.org.log.numMessagesReceived: + brief: The total number of log messages Splunk Log Observer accepts after filtering and throttling. + description: | + The total number of log messages Splunk Log Observer accepts after filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numMessagesReceived + +sf.org.log.numMessagesReceivedByToken: + brief: The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. + description: | + The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numMessagesReceivedByToken sf.org.num.alertmuting: brief: Total number of alert muting rules @@ -1467,239 +1732,6 @@ sf.org.subscription.datapointsPerMinute: metric_type: gauge title: sf.org.subscription.datapointsPerMinute -sf.org.ui.num.pagevisits: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. - metric_type: null - title: sf.org.ui.num.pagevisits - -sf.org.limit.activeTimeSeries: - brief: Number of active MTS allowed for your organization - description: | - Maximum number of active MTS, within a moving window of the past 25 hours, - that your organization can have. If you exceed this limit, Infrastructure Monitoring stops accepting data points for - new MTS, but continues to accept data points for existing MTS. To monitor your usage against the limit, - use the `metric sf.org.numActiveTimeSeries`. - - The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. - metric_type: gauge - title: sf.org.limit.activeTimeSeries - -sf.org.limit.containers: - brief: Maximum number of containers that can send data to your organization - description: | - Maximum number of containers that can send data to your - organization. This limit is higher than your contractual limit to allow for burst and overage usage. - If you exceed this limit, Infrastructure Monitoring drops datapoints from new containers but keeps - accepting data points for existing containers. To monitor your usage against the limit, use the metric - `sf.org.numResourcesMonitored` and filter for the dimension `resourceType:containers`. - metric_type: gauge - title: sf.org.limit.containers - -sf.org.limit.customMetricTimeSeries: - brief: Maximum number of active custom MTS you can have in your organization within a 1 hour time window - description: | - Maximum number of active custom MTS, within a moving window of the - previous 60 minutes, that you're allowed to have in your organization. If you exceed this limit, - Infrastructure Monitoring stops accepting data points for new custom MTS, but it continues to accept - data points for custom MTS that already existed. To see the number of MTS you're allowed to have, use the metric - `sf.org.numCustomMetrics`. To learn more about custom MTS, see the section - [About custom, bundled, and high-resolution metrics](https://docs.splunk.com/Observability/admin/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) - in the user documentation. - metric_type: gauge - title: sf.org.limit.customMetricTimeSeries - -sf.org.limit.detector: - brief: Maximum number of detectors you can use for your organization - description: | - Maximum number of detectors you can use for your organization. After you reach this limit, - you can't create more new detectors. - To monitor the number of detectors you create, - use the metric `sf.org.num.detector`. - metric_type: gauge - title: sf.org.limit.detector - -sf.org.limit.hosts: - brief: Maximum number of hosts that can send data to your organization - description: | - Maximum number of hosts that can send data to your organization. - This limit is higher than your contractual limit to allow for burst and overage usage. - If you exceed this limit, Infrastructure Monitoring drops data points from new hosts but - keeps accepting data points for existing hosts. To monitor your usage against the limit, use the metric - `sf.org.numResourcesMonitored` and filter for the dimension `resourceType:hosts`. - metric_type: gauge - title: sf.org.limit.hosts - -sf.org.limit.metricTimeSeriesCreatedPerMinute: - brief: Number of MTS you can create per minute - description: | - Maximum rate at which you can create new MTS - in your organization, measured in MTS per minute. If you exceed this rate, - Infrastructure Monitoring stops accepting data points for new MTS, but continues to accept data points for existing MTS. - To monitor the number of metrics you've created overall, use the metric `sf.org.numMetricTimeSeriesCreated`. - metric_type: gauge - title: sf.org.limit.metricTimeSeriesCreatedPerMinute - -sf.org.log.numMessagesReceived: - brief: The total number of log messages Splunk Log Observer accepts after filtering and throttling. - description: | - The total number of log messages Splunk Log Observer accepts after filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numMessagesReceived - -sf.org.log.numContentBytesReceived: - brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. - description: | - The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numContentBytesReceived - -sf.org.log.grossMessagesReceived: - brief: The total number of log messages Splunk Log Observer receives before filtering and throttling. - description: | - The total number of log messages Splunk Log Observer receives before filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.grossMessagesReceived - -sf.org.log.numMessageBytesReceived: - brief: The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. - description: | - The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numMessageBytesReceived - -sf.org.log.grossContentBytesReceived: - brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. - description: | - The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.grossContentBytesReceived - -sf.org.log.numMessagesReceivedByToken: - brief: The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. - description: | - The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numMessagesReceivedByToken - -sf.org.log.numMessagesDroppedOversize: - brief: The number of log messages Splunk Log Observer receives that are too large to process. - description: | - The number of log messages Splunk Log Observer receives that are too large to process. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numMessagesDroppedOversize - -sf.org.log.numMessagesDroppedThrottle: - brief: The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. - description: | - The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numMessagesDroppedThrottle - -sf.org.log.grossMessageBytesReceived: - brief: The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. - description: | - The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.grossMessageBytesReceived - -sf.org.log.numMessagesDroppedOversizeByToken: - brief: The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. - description: | - The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numMessagesDroppedOversizeByToken - -sf.org.log.grossContentBytesReceivedByToken: - brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. - description: | - The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.grossContentBytesReceivedByToken - -sf.org.log.numMessagesDroppedThrottleByToken: - brief: The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. - description: | - The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numMessagesDroppedThrottleByToken - -sf.org.log.grossMessageBytesReceivedByToken: - brief: The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression but before filtering and throttling are complete. - description: | - The number of bytes received by Splunk Log Observer for a specific access token from ingested logs after decompression but before filtering and throttling are complete. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.grossMessageBytesReceivedByToken - -sf.org.log.numMessageBytesReceivedByToken: - brief: The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. - description: | - The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numMessageBytesReceivedByToken - -sf.org.log.grossMessagesReceivedByToken: - brief: The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. - description: | - The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.grossMessagesReceivedByToken - -sf.org.log.numContentBytesReceivedByToken: - brief: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. - description: | - The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. - - * Dimension(s): `orgId` - * Data resolution: 10 second - metric_type: counter - title: sf.org.log.numContentBytesReceivedByToken - sf.org.subscription.containers: brief: Number of containers. description: | @@ -1745,3 +1777,9 @@ sf.org.subscription.function: * Data resolution: 2 minutes metric_type: gauge title: sf.org.subscription.function + +sf.org.ui.num.pagevisits: + brief: Infrastructure Monitoring internal metric + description: Reserved for Infrastructure Monitoring internal use only. + metric_type: null + title: sf.org.ui.num.pagevisits From 57402854fad3a6346daa278739bed198b36cfee2 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Wed, 23 Nov 2022 08:45:48 +0100 Subject: [PATCH 15/48] DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A --- signalfx-org-metrics/metrics.yaml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 9f6a6169..f881e3f1 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -735,6 +735,16 @@ sf.org.num.credentials: * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.credentials + +sf.org.num.crosslink: + brief: Total number of crosslinks + description: | + Total number of crosslinks. + + * Dimension(s): `orgId` + * Data resolution: 15 minutes + metric_type: gauge + title: sf.org.num.crosslink sf.org.num.dashboard: brief: Total number of dashboards @@ -862,6 +872,12 @@ sf.org.num.migrationmarker: metric_type: gauge title: sf.org.num.migrationmarker +sf.org.num.mutingactive: + brief: Infrastructure Monitoring internal metric + description: Reserved for Infrastructure Monitoring internal use only. + metric_type: gauge + title: sf.org.num.mutingactive + sf.org.num.namedtoken: brief: Number of access tokens description: | From 079c121bb4b61c5dbb44f41035676234cbd2b3c7 Mon Sep 17 00:00:00 2001 From: Antoine Toulme Date: Thu, 5 Jan 2023 13:35:42 -0800 Subject: [PATCH 16/48] update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability --- activemq/SMART_AGENT_MONITOR.md | 6 ++--- cassandra/SMART_AGENT_MONITOR.md | 2 +- collectd-cpu/SMART_AGENT_MONITOR.md | 2 +- consul/SMART_AGENT_MONITOR.md | 2 +- docker/SMART_AGENT_MONITOR.md | 2 +- etcd/SMART_AGENT_MONITOR.md | 2 +- gitlab/SMART_AGENT_MONITOR.md | 2 +- hadoop/SMART_AGENT_MONITOR.md | 2 +- java/SMART_AGENT_MONITOR.md | 4 ++-- jenkins/SMART_AGENT_MONITOR.md | 4 ++-- jenkins/smart_agent_config.yaml | 2 +- kafka/SMART_AGENT_MONITOR.md | 4 ++-- kong/SMART_AGENT_MONITOR.md | 2 +- logstash/SMART_AGENT_MONITOR.md | 2 +- marathon/SMART_AGENT_MONITOR.md | 4 ++-- memcached/SMART_AGENT_MONITOR.md | 2 +- mongodb-atlas/SMART_AGENT_MONITOR.md | 2 +- mongodb/SMART_AGENT_MONITOR.md | 24 +++++++++++++++++-- nginx/SMART_AGENT_MONITOR.md | 2 +- openstack/SMART_AGENT_MONITOR.md | 2 +- postgresql/SMART_AGENT_MONITOR.md | 6 ++--- postgresql/smart_agent_config.yaml | 2 +- rabbitmq/SMART_AGENT_MONITOR.md | 2 +- redis/SMART_AGENT_MONITOR.md | 2 +- signalfx-agent/README.md | 2 +- .../agent_docs/agent-install-awsecs.md | 8 +++---- .../agent_docs/agent-install-config-mgmt.md | 8 +++---- .../agent_docs/agent-install-packages.md | 6 ++--- .../agent-install-standalone-linux.md | 6 ++--- .../agent-install-standalone-windows.md | 8 +++---- .../agent_docs/agent-k8s-install-helm.md | 6 ++--- .../agent_docs/agent-k8s-install-kubectl.md | 8 +++---- signalfx-agent/agent_docs/config-schema.md | 8 +++---- signalfx-agent/agent_docs/monitor-config.md | 8 +++---- signalfx-agent/agent_docs/monitors/appmesh.md | 2 +- .../agent_docs/monitors/aspdotnet.md | 2 +- .../agent_docs/monitors/cadvisor.md | 2 +- signalfx-agent/agent_docs/monitors/cgroups.md | 4 ++-- .../monitors/cloudfoundry-firehose-nozzle.md | 2 +- .../agent_docs/monitors/collectd-activemq.md | 6 ++--- .../agent_docs/monitors/collectd-apache.md | 2 +- .../agent_docs/monitors/collectd-cassandra.md | 2 +- .../agent_docs/monitors/collectd-consul.md | 2 +- .../agent_docs/monitors/collectd-couchbase.md | 2 +- .../agent_docs/monitors/collectd-cpu.md | 2 +- .../agent_docs/monitors/collectd-cpufreq.md | 2 +- .../agent_docs/monitors/collectd-df.md | 2 +- .../agent_docs/monitors/collectd-disk.md | 2 +- .../monitors/collectd-elasticsearch.md | 2 +- .../agent_docs/monitors/collectd-etcd.md | 2 +- .../monitors/collectd-genericjmx.md | 2 +- .../agent_docs/monitors/collectd-hadoop.md | 2 +- .../agent_docs/monitors/collectd-hadoopjmx.md | 2 +- .../agent_docs/monitors/collectd-interface.md | 2 +- .../agent_docs/monitors/collectd-jenkins.md | 4 ++-- .../agent_docs/monitors/collectd-kafka.md | 4 ++-- .../monitors/collectd-kafka_consumer.md | 2 +- .../monitors/collectd-kafka_producer.md | 2 +- .../agent_docs/monitors/collectd-kong.md | 2 +- .../agent_docs/monitors/collectd-load.md | 2 +- .../agent_docs/monitors/collectd-marathon.md | 4 ++-- .../agent_docs/monitors/collectd-memcached.md | 2 +- .../agent_docs/monitors/collectd-memory.md | 2 +- .../agent_docs/monitors/collectd-mongodb.md | 24 +++++++++++++++++-- .../agent_docs/monitors/collectd-mysql.md | 2 +- .../agent_docs/monitors/collectd-nginx.md | 2 +- .../agent_docs/monitors/collectd-opcache.md | 2 +- .../agent_docs/monitors/collectd-openstack.md | 2 +- .../agent_docs/monitors/collectd-php-fpm.md | 2 +- .../monitors/collectd-postgresql.md | 2 +- .../agent_docs/monitors/collectd-processes.md | 2 +- .../agent_docs/monitors/collectd-protocols.md | 2 +- .../agent_docs/monitors/collectd-rabbitmq.md | 2 +- .../agent_docs/monitors/collectd-redis.md | 2 +- .../monitors/collectd-signalfx-metadata.md | 2 +- .../agent_docs/monitors/collectd-solr.md | 2 +- .../agent_docs/monitors/collectd-spark.md | 2 +- .../agent_docs/monitors/collectd-statsd.md | 2 +- .../agent_docs/monitors/collectd-systemd.md | 2 +- .../agent_docs/monitors/collectd-tomcat.md | 2 +- .../agent_docs/monitors/collectd-uptime.md | 2 +- .../agent_docs/monitors/collectd-vmem.md | 2 +- .../agent_docs/monitors/collectd-zookeeper.md | 2 +- signalfx-agent/agent_docs/monitors/conviva.md | 2 +- signalfx-agent/agent_docs/monitors/coredns.md | 2 +- signalfx-agent/agent_docs/monitors/cpu.md | 2 +- signalfx-agent/agent_docs/monitors/disk-io.md | 4 ++-- .../monitors/docker-container-stats.md | 2 +- signalfx-agent/agent_docs/monitors/dotnet.md | 2 +- .../agent_docs/monitors/ecs-metadata.md | 2 +- .../agent_docs/monitors/elasticsearch.md | 2 +- signalfx-agent/agent_docs/monitors/etcd.md | 2 +- signalfx-agent/agent_docs/monitors/expvar.md | 2 +- .../agent_docs/monitors/filesystems.md | 6 ++--- .../agent_docs/monitors/gitlab-gitaly.md | 2 +- .../agent_docs/monitors/gitlab-runner.md | 2 +- .../agent_docs/monitors/gitlab-sidekiq.md | 2 +- .../agent_docs/monitors/gitlab-unicorn.md | 2 +- .../agent_docs/monitors/gitlab-workhorse.md | 2 +- signalfx-agent/agent_docs/monitors/gitlab.md | 2 +- signalfx-agent/agent_docs/monitors/hana.md | 2 +- signalfx-agent/agent_docs/monitors/haproxy.md | 2 +- .../agent_docs/monitors/heroku-metadata.md | 2 +- .../agent_docs/monitors/host-metadata.md | 2 +- signalfx-agent/agent_docs/monitors/http.md | 2 +- .../agent_docs/monitors/internal-metrics.md | 2 +- signalfx-agent/agent_docs/monitors/jmx.md | 2 +- .../monitors/kube-controller-manager.md | 2 +- .../agent_docs/monitors/kubelet-metrics.md | 2 +- .../agent_docs/monitors/kubelet-stats.md | 2 +- .../monitors/kubernetes-apiserver.md | 2 +- .../agent_docs/monitors/kubernetes-cluster.md | 4 ++-- .../agent_docs/monitors/kubernetes-proxy.md | 2 +- .../monitors/kubernetes-scheduler.md | 2 +- .../agent_docs/monitors/kubernetes-volumes.md | 2 +- signalfx-agent/agent_docs/monitors/load.md | 2 +- .../agent_docs/monitors/logstash.md | 2 +- signalfx-agent/agent_docs/monitors/memory.md | 2 +- .../agent_docs/monitors/mongodb-atlas.md | 2 +- signalfx-agent/agent_docs/monitors/nagios.md | 6 ++--- signalfx-agent/agent_docs/monitors/net-io.md | 4 ++-- signalfx-agent/agent_docs/monitors/ntp.md | 2 +- .../agent_docs/monitors/openshift-cluster.md | 4 ++-- .../agent_docs/monitors/postgresql.md | 6 ++--- signalfx-agent/agent_docs/monitors/process.md | 6 ++--- .../agent_docs/monitors/prometheus-go.md | 2 +- .../monitors/prometheus-nginx-ingress.md | 2 +- .../monitors/prometheus-nginx-vts.md | 2 +- .../agent_docs/monitors/prometheus-node.md | 2 +- .../monitors/prometheus-postgres.md | 2 +- .../monitors/prometheus-prometheus.md | 2 +- .../agent_docs/monitors/prometheus-redis.md | 2 +- .../agent_docs/monitors/prometheus-velero.md | 2 +- .../agent_docs/monitors/supervisor.md | 2 +- .../agent_docs/monitors/telegraf-dns.md | 2 +- .../agent_docs/monitors/telegraf-ntpq.md | 2 +- .../agent_docs/monitors/telegraf-procstat.md | 2 +- .../agent_docs/monitors/telegraf-sqlserver.md | 2 +- .../agent_docs/monitors/telegraf-varnish.md | 2 +- .../monitors/telegraf-win_services.md | 2 +- signalfx-agent/agent_docs/monitors/traefik.md | 2 +- signalfx-agent/agent_docs/monitors/vmem.md | 2 +- signalfx-agent/agent_docs/monitors/vsphere.md | 2 +- .../agent_docs/monitors/windows-iis.md | 2 +- .../agent_docs/monitors/windows-legacy.md | 2 +- signalfx-agent/agent_docs/quick-install.md | 2 +- .../smartagent-deprecation-notice.md | 8 +++++-- solr/SMART_AGENT_MONITOR.md | 2 +- spark/SMART_AGENT_MONITOR.md | 2 +- traefik/SMART_AGENT_MONITOR.md | 2 +- zookeeper/SMART_AGENT_MONITOR.md | 2 +- 151 files changed, 248 insertions(+), 204 deletions(-) diff --git a/activemq/SMART_AGENT_MONITOR.md b/activemq/SMART_AGENT_MONITOR.md index bcee4532..a4bc3fe4 100644 --- a/activemq/SMART_AGENT_MONITOR.md +++ b/activemq/SMART_AGENT_MONITOR.md @@ -19,7 +19,7 @@ Below is an overview of that monitor. SignalFx's integration with ActiveMQ wraps the [Collectd GenericJMX -monitor](https://docs.signalfx.com/en/latest/integrations/agent/monitors/collectd-genericjmx.html) +monitor](https://docs.splunk.com/observability/gdi/genericjmx/genericjmx.html) to monitor ActiveMQ. Use this monitor to gather the following types of information from ActiveMQ: @@ -29,7 +29,7 @@ Use this monitor to gather the following types of information from ActiveMQ: * Topic (Topic status) To monitor the age of messages inside ActiveMQ queues, see [ActiveMQ -message age listener](https://docs.signalfx.com/en/latest/integrations/integrations-reference/integrations.activemq.message.age.listener.html)[](sfx_link:amq-message-age). +message age listener](https://docs.splunk.com/observability/gdi/activemq/activemq.html)[](sfx_link:amq-message-age). ## Example config @@ -100,7 +100,7 @@ The **nested** `values` config object has the following fields: ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/cassandra/SMART_AGENT_MONITOR.md b/cassandra/SMART_AGENT_MONITOR.md index 8c0b82d3..149bf304 100644 --- a/cassandra/SMART_AGENT_MONITOR.md +++ b/cassandra/SMART_AGENT_MONITOR.md @@ -92,7 +92,7 @@ The **nested** `values` config object has the following fields: ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/collectd-cpu/SMART_AGENT_MONITOR.md b/collectd-cpu/SMART_AGENT_MONITOR.md index 2e8a706d..9d100b57 100644 --- a/collectd-cpu/SMART_AGENT_MONITOR.md +++ b/collectd-cpu/SMART_AGENT_MONITOR.md @@ -52,7 +52,7 @@ This monitor has no configuration options. ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/consul/SMART_AGENT_MONITOR.md b/consul/SMART_AGENT_MONITOR.md index 01296982..1bee0767 100644 --- a/consul/SMART_AGENT_MONITOR.md +++ b/consul/SMART_AGENT_MONITOR.md @@ -85,7 +85,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/docker/SMART_AGENT_MONITOR.md b/docker/SMART_AGENT_MONITOR.md index 7b3401e9..d4796224 100644 --- a/docker/SMART_AGENT_MONITOR.md +++ b/docker/SMART_AGENT_MONITOR.md @@ -69,7 +69,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/etcd/SMART_AGENT_MONITOR.md b/etcd/SMART_AGENT_MONITOR.md index 881f052c9..0beca17d 100644 --- a/etcd/SMART_AGENT_MONITOR.md +++ b/etcd/SMART_AGENT_MONITOR.md @@ -54,7 +54,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/gitlab/SMART_AGENT_MONITOR.md b/gitlab/SMART_AGENT_MONITOR.md index 1ef5f6d2..ac34a12e 100644 --- a/gitlab/SMART_AGENT_MONITOR.md +++ b/gitlab/SMART_AGENT_MONITOR.md @@ -196,7 +196,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/hadoop/SMART_AGENT_MONITOR.md b/hadoop/SMART_AGENT_MONITOR.md index a3c40568..d5745698 100644 --- a/hadoop/SMART_AGENT_MONITOR.md +++ b/hadoop/SMART_AGENT_MONITOR.md @@ -81,7 +81,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/java/SMART_AGENT_MONITOR.md b/java/SMART_AGENT_MONITOR.md index 60ff0e99..bdf55033 100644 --- a/java/SMART_AGENT_MONITOR.md +++ b/java/SMART_AGENT_MONITOR.md @@ -114,7 +114,7 @@ The easiest thing to do here is to make sure the `com.sun.management.jmxremote.rmi.port` property in your Java app is set to the same port as the JMX connect port. There may be other variations of this that say `Connection reset` or `Connection refused` but they all -generaly indicate a similar cause. +generally indicate a similar cause. ## Configuration @@ -174,7 +174,7 @@ The **nested** `values` config object has the following fields: ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/jenkins/SMART_AGENT_MONITOR.md b/jenkins/SMART_AGENT_MONITOR.md index 50ac88da..6e8baaaa 100644 --- a/jenkins/SMART_AGENT_MONITOR.md +++ b/jenkins/SMART_AGENT_MONITOR.md @@ -96,7 +96,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor | `path` | no | `string` | | | `metricsKey` | **yes** | `string` | Key required for collecting metrics. The access key located at `Manage Jenkins > Configure System > Metrics > ADD.` If empty, click `Generate`. | | `enhancedMetrics` | no | `bool` | Whether to enable enhanced metrics (**default:** `false`) | -| `excludeJobMetrics` | no | `bool` | Set to *true* to to exclude job metrics retrieved from `/api/json` endpoint (**default:** `false`) | +| `excludeJobMetrics` | no | `bool` | Set to *true* to exclude job metrics retrieved from `/api/json` endpoint (**default:** `false`) | | `includeMetrics` | no | `list of strings` | Used to enable individual enhanced metrics when `enhancedMetrics` is false | | `username` | no | `string` | User with security access to jenkins | | `apiToken` | no | `string` | API Token of the user | @@ -110,7 +110,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics All metrics of this integration are emitted by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. These are the metrics available for this integration. diff --git a/jenkins/smart_agent_config.yaml b/jenkins/smart_agent_config.yaml index 2c3b6434..48f38839 100644 --- a/jenkins/smart_agent_config.yaml +++ b/jenkins/smart_agent_config.yaml @@ -41,7 +41,7 @@ collectd/jenkins: type: bool yamlName: enhancedMetrics - default: 'false' - doc: Set to *true* to to exclude job metrics retrieved from `/api/json` endpoint + doc: Set to *true* to exclude job metrics retrieved from `/api/json` endpoint elementKind: '' required: false type: bool diff --git a/kafka/SMART_AGENT_MONITOR.md b/kafka/SMART_AGENT_MONITOR.md index 844a211d..c249ec46 100644 --- a/kafka/SMART_AGENT_MONITOR.md +++ b/kafka/SMART_AGENT_MONITOR.md @@ -33,7 +33,7 @@ apart from the list of default metrics, kafka.server:type=ZooKeeperClientMetrics is a good metric to monitor since it gives an understanding of how long brokers wait for requests to Zookeeper to be completed. Since Zookeeper is an integral part of a Kafka cluster, monitoring it using the [Zookeeper -monitor](https://docs.signalfx.com/en/latest/integrations/agent/monitors/collectd-zookeeper.html)[](sfx_link:zookeeper) +monitor](https://docs.splunk.com/observability/gdi/zookeeper/zookeeper.html)[](sfx_link:zookeeper) is recommended. It is also a good idea to monitor disk utilization and network metrics of the underlying host. @@ -96,7 +96,7 @@ The **nested** `values` config object has the following fields: ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/kong/SMART_AGENT_MONITOR.md b/kong/SMART_AGENT_MONITOR.md index 377510fe..d4d063a6 100644 --- a/kong/SMART_AGENT_MONITOR.md +++ b/kong/SMART_AGENT_MONITOR.md @@ -173,7 +173,7 @@ The **nested** `metrics` config object has the following fields: ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/logstash/SMART_AGENT_MONITOR.md b/logstash/SMART_AGENT_MONITOR.md index 6d01d4db..8d7786b6 100644 --- a/logstash/SMART_AGENT_MONITOR.md +++ b/logstash/SMART_AGENT_MONITOR.md @@ -158,7 +158,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/marathon/SMART_AGENT_MONITOR.md b/marathon/SMART_AGENT_MONITOR.md index 19052660..2186b509 100644 --- a/marathon/SMART_AGENT_MONITOR.md +++ b/marathon/SMART_AGENT_MONITOR.md @@ -22,7 +22,7 @@ Monitors a Mesos Marathon instance using the [collectd Marathon Python plugin](https://github.com/signalfx/collectd-marathon). See the [integrations -doc](https://docs.signalfx.com/en/latest/integrations/integrations-reference/integrations.marathon.html) +doc](https://docs.splunk.com/observability/gdi/marathon/marathon.html) for more information on configuration. Sample YAML configuration: @@ -76,7 +76,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics All metrics of this integration are emitted by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. These are the metrics available for this integration. diff --git a/memcached/SMART_AGENT_MONITOR.md b/memcached/SMART_AGENT_MONITOR.md index dfee45a1..a6dbe437 100644 --- a/memcached/SMART_AGENT_MONITOR.md +++ b/memcached/SMART_AGENT_MONITOR.md @@ -58,7 +58,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/mongodb-atlas/SMART_AGENT_MONITOR.md b/mongodb-atlas/SMART_AGENT_MONITOR.md index 3a0b1bb7..2849f893 100644 --- a/mongodb-atlas/SMART_AGENT_MONITOR.md +++ b/mongodb-atlas/SMART_AGENT_MONITOR.md @@ -75,7 +75,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/mongodb/SMART_AGENT_MONITOR.md b/mongodb/SMART_AGENT_MONITOR.md index 41781e57..bc39e89f 100644 --- a/mongodb/SMART_AGENT_MONITOR.md +++ b/mongodb/SMART_AGENT_MONITOR.md @@ -44,11 +44,31 @@ Documentation for MongoDB can be found [here](http://docs.mongodb.org/manual/). If you're monitoring a secured MongoDB deployment, it is a good practice to create a MongoDB user with minimal read-only roles, as follows: +If the monitor is configured to send collection level metrics, you need to create and add this role so your user has permission to run collStats and indexStats +against system collections and any collection in the db you're monitoring. +In the below role, we're adding the appropriate permissions for system collections under the admin db. +For more details on how to add all your non-admin collections, check https://www.mongodb.com/docs/manual/reference/resource-document/ + +``` +use admin +db.createRole( + { + role: "splunkMonitor", + privileges: [ { resource: { db: 'admin', collection: 'system.roles' }, actions: [ 'collStats', 'indexStats' ] }, + { resource: { db: 'admin', collection: 'system.users' }, actions: [ 'collStats', 'indexStats' ] }, + { resource: { db: 'admin', collection: 'system.version' }, actions: [ 'collStats', 'indexStats' ] } ], + roles: [ { role: "read", db: "admin" } ] + }, + { w: "majority" , wtimeout: 5000 } +) +``` + ``` +use admin db.createUser( { user: "collectd", pwd: "collectd", - roles: [ { role: "readAnyDatabase", db: "admin" }, { role: "clusterMonitor", db: "admin" } ] + roles: [ { role: "readAnyDatabase", db: "admin" }, { role: "clusterMonitor", db: "admin" }, {role: "splunkMonitor", db: "admin"} ] }); ``` @@ -88,7 +108,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/nginx/SMART_AGENT_MONITOR.md b/nginx/SMART_AGENT_MONITOR.md index 3080ad9f..26f6b073 100644 --- a/nginx/SMART_AGENT_MONITOR.md +++ b/nginx/SMART_AGENT_MONITOR.md @@ -63,7 +63,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/openstack/SMART_AGENT_MONITOR.md b/openstack/SMART_AGENT_MONITOR.md index f2b662e4..a3314b84 100644 --- a/openstack/SMART_AGENT_MONITOR.md +++ b/openstack/SMART_AGENT_MONITOR.md @@ -105,7 +105,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/postgresql/SMART_AGENT_MONITOR.md b/postgresql/SMART_AGENT_MONITOR.md index 07d05498..f2d39457 100644 --- a/postgresql/SMART_AGENT_MONITOR.md +++ b/postgresql/SMART_AGENT_MONITOR.md @@ -109,7 +109,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor | `masterDBName` | no | `string` | The "master" database to which the agent first connects to query the list of databases available in the server. This database should be accessible to the user specified with `connectionString` and `params` below, and that user should have permission to query `pg_database`. If you want to filter which databases are monitored, use the `databases` option below. (**default:** `postgres`) | | `connectionString` | no | `string` | See https://godoc.org/github.com/lib/pq#hdr-Connection_String_Parameters. | | `params` | no | `map of strings` | Parameters to the connection string that can be templated into the connection string with the syntax `{{.key}}`. | -| `databases` | no | `list of strings` | List of databases to send database-specific metrics about. If omitted, metrics about all databases will be sent. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters). (**default:** `[*]`) | +| `databases` | no | `list of strings` | List of databases to send database-specific metrics about. If omitted, metrics about all databases will be sent. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). (**default:** `[*]`) | | `databasePollIntervalSeconds` | no | `integer` | How frequently to poll for new/deleted databases in the DB server. Defaults to the same as `intervalSeconds` if not set. (**default:** `0`) | | `logQueries` | no | `bool` | If true, queries will be logged at the info level. (**default:** `false`) | | `topQueryLimit` | no | `integer` | The number of top queries to consider when publishing query-related metrics (**default:** `10`) | @@ -118,7 +118,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. @@ -133,7 +133,7 @@ These are the metrics available for this integration. - `postgres_pct_connections` (*gauge*)
The number of connections to this database as a fraction of the maximum number of allowed connections. - ***`postgres_query_count`*** (*cumulative*)
Total number of queries executed on the `database`, broken down by `user`. Note that the accuracy of this metric depends on the PostgreSQL [pg_stat_statements.max config option](https://www.postgresql.org/docs/9.3/pgstatstatements.html#AEN160631) being large enough to hold all queries. - - ***`postgres_query_time`*** (*cumulative*)
Total time taken to execute queries on the `database`, broken down by `user`. + - ***`postgres_query_time`*** (*cumulative*)
Total time taken to execute queries on the `database`, broken down by `user`. Measured in ms unless otherwise indicated. - ***`postgres_rows_deleted`*** (*cumulative*)
Number of rows deleted from the `table`. - ***`postgres_rows_inserted`*** (*cumulative*)
Number of rows inserted into the `table`. - ***`postgres_rows_updated`*** (*cumulative*)
Number of rows updated in the `table`. diff --git a/postgresql/smart_agent_config.yaml b/postgresql/smart_agent_config.yaml index fd92f7c6..f8910525 100644 --- a/postgresql/smart_agent_config.yaml +++ b/postgresql/smart_agent_config.yaml @@ -38,7 +38,7 @@ postgresql: yamlName: params - default: '[*]' doc: List of databases to send database-specific metrics about. If omitted, metrics - about all databases will be sent. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters). + about all databases will be sent. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). elementKind: string required: false type: list diff --git a/rabbitmq/SMART_AGENT_MONITOR.md b/rabbitmq/SMART_AGENT_MONITOR.md index 8f6df974..aecad061 100644 --- a/rabbitmq/SMART_AGENT_MONITOR.md +++ b/rabbitmq/SMART_AGENT_MONITOR.md @@ -71,7 +71,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/redis/SMART_AGENT_MONITOR.md b/redis/SMART_AGENT_MONITOR.md index c85d15cc..9f99149c 100644 --- a/redis/SMART_AGENT_MONITOR.md +++ b/redis/SMART_AGENT_MONITOR.md @@ -116,7 +116,7 @@ The **nested** `sendListLengths` config object has the following fields: ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/signalfx-agent/README.md b/signalfx-agent/README.md index 34e13d4b..39b89864 100644 --- a/signalfx-agent/README.md +++ b/signalfx-agent/README.md @@ -11,7 +11,7 @@ SignalFx Smart Agent is deprecated. For details, see the [Deprecation Notice](ht SignalFx Smart Agent Integration installs the Smart Agent application on a single host machine from which you want to collect monitoring data. Smart Agent collects infrastructure monitoring, µAPM, and Kubernetes data. For other installation options, including bulk deployments to production, -see [Install and Configure the Smart Agent](https://docs.signalfx.com/en/latest/integrations/agent/agent-install-methods.html). +see [Install and Configure the Smart Agent](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#install-the-smart-agent). ## Installation diff --git a/signalfx-agent/agent_docs/agent-install-awsecs.md b/signalfx-agent/agent_docs/agent-install-awsecs.md index c8855692..a146baa2 100644 --- a/signalfx-agent/agent_docs/agent-install-awsecs.md +++ b/signalfx-agent/agent_docs/agent-install-awsecs.md @@ -34,7 +34,7 @@ Edit the signalfx-agent-task.json file and make these replacements: | `MY_ACCESS_TOKEN` | Your SignalFx access token. See [Prerequisites](#prerequisites). | | `MY_INGEST_URL` | `https://ingest..signalfx.com`. Replace `` with your realm. See [Prerequisites](#prerequisites) | | `MY_API_URL` | `https://api..signalfx.com`. Replace `` with your realm. See [Prerequisites](#prerequisites) | -| `MY_TRACE_ENDPOINT_URL` | `null`. The Smart Agent only uses the property for Microservices APM. To learn more about the Smart Agent and Microservice APM, see [Deploy a SignalFx Smart Agent for µAPM](https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-smart-agent.html). | +| `MY_TRACE_ENDPOINT_URL` | `null`. The Smart Agent only uses the property for Microservices APM. To learn more about the Smart Agent and Microservice APM, see [Deploy a SignalFx Smart Agent for µAPM](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html). | ### Edit additional options @@ -110,7 +110,7 @@ To create this service in the ECS web admin console: The charts display metrics from the infrastructure for that node. - To learn more, see [Built-In Dashboards and Charts](https://docs.signalfx.com/en/latest/getting-started/built-in-content/built-in-dashboards.html). + To learn more, see [Built-In Dashboards and Charts](https://docs.splunk.com/observability/data-visualization/dashboards/built-in-dashboards.html). * For Kubernetes monitoring, perform these steps: 1. In SignalFx, from the main menu select **Infrastructure** > **Kubernetes Navigator** > **Cluster map**. @@ -119,10 +119,10 @@ To create this service in the ECS web admin console: The detail pane on the right hand side of the page displays details of that cluster and nodes. - To learn more, see [Getting Around the Kubernetes Navigator](https://docs.signalfx.com/en/latest/integrations/kubernetes/get-around-k8s-navigator.html). + To learn more, see [Getting Around the Kubernetes Navigator](https://docs.splunk.com/observability/infrastructure/monitor/k8s.html). * For APM monitoring, learn how to install, configure, and verify the Smart Agent for Microservices APM (**µAPM**). See -[Get started with SignalFx µAPM](https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-index.html). +[Get started with SignalFx µAPM](https://docs.splunk.com/observability/apm/intro-to-apm.html#nav-Introduction-to-Splunk-APM). ### Uninstall the Smart Agent diff --git a/signalfx-agent/agent_docs/agent-install-config-mgmt.md b/signalfx-agent/agent_docs/agent-install-config-mgmt.md index a6d76377..b7aceac7 100644 --- a/signalfx-agent/agent_docs/agent-install-config-mgmt.md +++ b/signalfx-agent/agent_docs/agent-install-config-mgmt.md @@ -55,7 +55,7 @@ To install the role from GitHub: The Smart Agent Ansible role uses the following variables: * `sfx_agent_config`: A mapping that Ansible converts to the Smart Agent configuration YAML file. - See [Agent Configuration](https://docs.signalfx.com/en/latest/integrations/agent/config-schema.html) + See [Agent Configuration](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#configure-the-smart-agent) for a full list of acceptable options and their default values. In this mapping, replace `` with the access token value you obtained previously, as described in the section [Prerequisites for all platforms](#prerequisites-for-all-platforms). @@ -289,7 +289,7 @@ To verify that your installation and configuration is working: The charts display metrics from your infrastructure. - To learn more, see [Built-In Dashboards and Charts](https://docs.signalfx.com/en/latest/getting-started/built-in-content/built-in-dashboards.html). + To learn more, see [Built-In Dashboards and Charts](https://docs.splunk.com/observability/data-visualization/dashboards/built-in-dashboards.html). * For Kubernetes monitoring, perform these steps: 1. In SignalFx, from the main menu select **Infrastructure** > **Kubernetes Navigator** > **Cluster map**. @@ -298,10 +298,10 @@ To verify that your installation and configuration is working: The detail pane displays details of your cluster and nodes. - To learn more, see [Getting Around the Kubernetes Navigator](https://docs.signalfx.com/en/latest/integrations/kubernetes/get-around-k8s-navigator.html) + To learn more, see [Getting Around the Kubernetes Navigator](https://docs.splunk.com/observability/infrastructure/monitor/k8s.html) * For APM monitoring, learn how to install, configure, and verify the Smart Agent for Microservices APM (**µAPM**). See -[Get started with SignalFx µAPM](https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-index.html). +[Get started with SignalFx µAPM](https://docs.splunk.com/observability/apm/intro-to-apm.html#nav-Introduction-to-Splunk-APM). ## Install the Smart Agent using a Puppet module diff --git a/signalfx-agent/agent_docs/agent-install-packages.md b/signalfx-agent/agent_docs/agent-install-packages.md index 23175d7d..49e958e1 100644 --- a/signalfx-agent/agent_docs/agent-install-packages.md +++ b/signalfx-agent/agent_docs/agent-install-packages.md @@ -118,7 +118,7 @@ For Debian or RPM, verify that your installation and configuration are working. The charts display metrics from your infrastructure. - To learn more, see [Built-In Dashboards and Charts](https://docs.signalfx.com/en/latest/getting-started/built-in-content/built-in-dashboards.html). + To learn more, see [Built-In Dashboards and Charts](https://docs.splunk.com/observability/data-visualization/dashboards/built-in-dashboards.html). * For Kubernetes monitoring, perform these steps: 1. In SignalFx, from the main menu select **Infrastructure** > **Kubernetes Navigator** > **Cluster map**. @@ -127,10 +127,10 @@ For Debian or RPM, verify that your installation and configuration are working. The detail pane displays details of your cluster and nodes. - To learn more, see [Getting Around the Kubernetes Navigator](https://docs.signalfx.com/en/latest/integrations/kubernetes/get-around-k8s-navigator.html). + To learn more, see [Getting Around the Kubernetes Navigator](https://docs.splunk.com/observability/infrastructure/monitor/k8s.html). * For SignalFx Microservice APM monitoring, learn how to install, configure, and verify the SignalFx Smart Agent for Microservices APM (**µAPM**). See - [Get started with SignalFx µAPM](https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-index.html). + [Get started with SignalFx µAPM](https://docs.splunk.com/observability/apm/intro-to-apm.html#nav-Introduction-to-Splunk-APM). ### Uninstall the Smart Agent diff --git a/signalfx-agent/agent_docs/agent-install-standalone-linux.md b/signalfx-agent/agent_docs/agent-install-standalone-linux.md index 4e5dee46..8c5c5695 100644 --- a/signalfx-agent/agent_docs/agent-install-standalone-linux.md +++ b/signalfx-agent/agent_docs/agent-install-standalone-linux.md @@ -97,7 +97,7 @@ To verify that your installation and configuration, perform these steps: The charts display metrics from your infrastructure. - To learn more, see [Built-In Dashboards and Charts](https://docs.signalfx.com/en/latest/getting-started/built-in-content/built-in-dashboards.html). + To learn more, see [Built-In Dashboards and Charts](https://docs.splunk.com/observability/data-visualization/dashboards/built-in-dashboards.html). * For Kubernetes monitoring, perform these steps: 1. In SignalFx, from the main menu select **Infrastructure** > **Kubernetes Navigator** > **Cluster map**. @@ -106,10 +106,10 @@ To verify that your installation and configuration, perform these steps: The detail pane displays details of your cluster and nodes. - To learn more, see [Getting Around the Kubernetes Navigator](https://docs.signalfx.com/en/latest/integrations/kubernetes/get-around-k8s-navigator.html). + To learn more, see [Getting Around the Kubernetes Navigator](https://docs.splunk.com/observability/infrastructure/monitor/k8s.html). * For APM monitoring, learn how to install, configure, and verify the Smart Agent for Microservices APM (**µAPM**). See - [Get started with SignalFx µAPM](https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-index.html). + [Get started with SignalFx µAPM](https://docs.splunk.com/observability/apm/intro-to-apm.html#nav-Introduction-to-Splunk-APM). ### Uninstall the Smart Agent diff --git a/signalfx-agent/agent_docs/agent-install-standalone-windows.md b/signalfx-agent/agent_docs/agent-install-standalone-windows.md index 373e374b..1d4c79a1 100644 --- a/signalfx-agent/agent_docs/agent-install-standalone-windows.md +++ b/signalfx-agent/agent_docs/agent-install-standalone-windows.md @@ -97,7 +97,7 @@ To start the Smart Agent as a Windows service, run the following command in a co ``` To learn about other Windows service options, see -[Service Configuration](https://docs.signalfx.com/en/latest/integrations/agent/windows.html#service-configuration). +[Service Configuration](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#install-the-smart-agent). ### Verify the Smart Agent @@ -109,7 +109,7 @@ To verify your installation and configuration, perform these steps: The charts display metrics from your infrastructure. - To learn more, see [Built-In Dashboards and Charts](https://docs.signalfx.com/en/latest/getting-started/built-in-content/built-in-dashboards.html). + To learn more, see [Built-In Dashboards and Charts](https://docs.splunk.com/observability/data-visualization/dashboards/built-in-dashboards.html). * For Kubernetes monitoring, perform these steps: 1. In SignalFx, from the main menu select **Infrastructure** > **Kubernetes Navigator** > **Cluster map**. @@ -118,10 +118,10 @@ To verify your installation and configuration, perform these steps: The detail pane on the right hand side of the page displays details of your cluster and nodes. - To learn more, see [Getting Around the Kubernetes Navigator](https://docs.signalfx.com/en/latest/integrations/kubernetes/get-around-k8s-navigator.html) + To learn more, see [Getting Around the Kubernetes Navigator](https://docs.splunk.com/observability/infrastructure/monitor/k8s.html) * For APM monitoring, learn how to install, configure, and verify the Smart Agent for Microservices APM (**µAPM**). See - [Get started with SignalFx µAPM](https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-index.html). + [Get started with SignalFx µAPM](https://docs.splunk.com/observability/apm/intro-to-apm.html#nav-Introduction-to-Splunk-APM). ### Uninstall the Smart Agent diff --git a/signalfx-agent/agent_docs/agent-k8s-install-helm.md b/signalfx-agent/agent_docs/agent-k8s-install-helm.md index 42090f8b..05f55289 100644 --- a/signalfx-agent/agent_docs/agent-k8s-install-helm.md +++ b/signalfx-agent/agent_docs/agent-k8s-install-helm.md @@ -108,7 +108,7 @@ To verify that your installation and config is working: The charts display metrics from the infrastructure for that node. - To learn more, see [Built-In Dashboards and Charts](https://docs.signalfx.com/en/latest/getting-started/built-in-content/built-in-dashboards.html). + To learn more, see [Built-In Dashboards and Charts](https://docs.splunk.com/observability/data-visualization/dashboards/built-in-dashboards.html). * For Kubernetes monitoring: 1. In SignalFx UI, from the main menu select **Infrastructure** > **Kubernetes Navigator** > **Cluster map**. @@ -117,10 +117,10 @@ To verify that your installation and config is working: The detail pane on the right hand side of the page displays details of your cluster and nodes. - To learn more, see [Getting Around the Kubernetes Navigator](https://docs.signalfx.com/en/latest/integrations/kubernetes/get-around-k8s-navigator.html). + To learn more, see [Getting Around the Kubernetes Navigator](https://docs.splunk.com/observability/infrastructure/monitor/k8s.html). * For APM monitoring, learn how to install, configure, and verify the Smart Agent for Microservices APM (**µAPM**). See - [Get started with SignalFx µAPM](https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-index.html). + [Get started with SignalFx µAPM](https://docs.splunk.com/observability/apm/intro-to-apm.html#nav-Introduction-to-Splunk-APM). ### Uninstall the Smart Agent diff --git a/signalfx-agent/agent_docs/agent-k8s-install-kubectl.md b/signalfx-agent/agent_docs/agent-k8s-install-kubectl.md index 3e40ad56..cf931a39 100644 --- a/signalfx-agent/agent_docs/agent-k8s-install-kubectl.md +++ b/signalfx-agent/agent_docs/agent-k8s-install-kubectl.md @@ -52,7 +52,7 @@ On the same host, download the following configuration files from the - Cluster name: For each of your Kubernetes clusters, replace `MY-CLUSTER` with a unique cluster name. - Realm: Update the value of `signalFxRealm` with the name of your SignalFx realm. - To avoid sending docker and cadvisor metrics from some containers, - update the `datapointsToExclude` property. To learn more, see [Filtering](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#filtering). + update the `datapointsToExclude` property. To learn more, see [Filtering](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). 2. In the clusterrolebinding.yaml file, update `MY_AGENT_NAMESPACE` or the service account token reference with the Smart Agent namespace in which you're deploying the agent. @@ -120,7 +120,7 @@ In addition, you can do the following in SignalFx: The charts display metrics from the infrastructure for that node. - To learn more, see [Built-In Dashboards and Charts](https://docs.signalfx.com/en/latest/getting-started/built-in-content/built-in-dashboards.html). + To learn more, see [Built-In Dashboards and Charts](https://docs.splunk.com/observability/data-visualization/dashboards/built-in-dashboards.html). * For Kubernetes monitoring: 1. In SignalFx, from the main menu select **Infrastructure** > **Kubernetes Navigator** > **Cluster map**. @@ -129,10 +129,10 @@ In addition, you can do the following in SignalFx: The detail pane displays details of that cluster and nodes. - To learn more, see [Getting Around the Kubernetes Navigator](https://docs.signalfx.com/en/latest/integrations/kubernetes/get-around-k8s-navigator.html). + To learn more, see [Getting Around the Kubernetes Navigator](https://docs.splunk.com/observability/infrastructure/monitor/k8s.html). * For APM monitoring, learn how to install, configure, and verify the Smart Agent for Microservices APM (**µAPM**). See -[Get started with SignalFx µAPM](https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-index.html). +[Get started with SignalFx µAPM](https://docs.splunk.com/observability/apm/intro-to-apm.html#nav-Introduction-to-Splunk-APM). ### Uninstall the Smart Agent diff --git a/signalfx-agent/agent_docs/config-schema.md b/signalfx-agent/agent_docs/config-schema.md index f01c3df1..dbbdfe7b 100644 --- a/signalfx-agent/agent_docs/config-schema.md +++ b/signalfx-agent/agent_docs/config-schema.md @@ -102,10 +102,10 @@ The following are generic options that apply to all monitors. Each monitor type | `validateDiscoveryRule` | no | bool | If true, a warning will be emitted if a discovery rule contains variables that will never possibly match a rule. If using multiple observers, it is convenient to set this to false to suppress spurious errors. The top-level setting `validateDiscoveryRules` acts as a default if this isn't set. (**default:** `"false"`) | | `extraDimensions` | no | map of strings | A set of extra dimensions (key:value pairs) to include on datapoints emitted by the monitor(s) created from this configuration. To specify metrics from this monitor should be high-resolution, add the dimension `sf_hires: 1` | | `extraSpanTags` | no | map of strings | A set of extra span tags (key:value pairs) to include on spans emitted by the monitor(s) created from this configuration. | -| `extraSpanTagsFromEndpoint` | no | map of strings | A mapping of extra span tag names to a [discovery rule expression](https://docs.signalfx.com/en/latest/integrations/agent/auto-discovery.html) that is used to derive the value of the span tag. For example, to use a certain container label as a span tag, you could use something like this in your monitor config block: `extraSpanTagsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}`. This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | +| `extraSpanTagsFromEndpoint` | no | map of strings | A mapping of extra span tag names to a [discovery rule expression](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#service-discovery-using-the-smart-agent) that is used to derive the value of the span tag. For example, to use a certain container label as a span tag, you could use something like this in your monitor config block: `extraSpanTagsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}`. This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | | `defaultSpanTags` | no | map of strings | A set of default span tags (key:value pairs) to include on spans emitted by the monitor(s) created from this configuration. | -| `defaultSpanTagsFromEndpoint` | no | map of strings | A mapping of default span tag names to a [discovery rule expression](https://docs.signalfx.com/en/latest/integrations/agent/auto-discovery.html) that is used to derive the default value of the span tag. For example, to use a certain container label as a span tag, you could use something like this in your monitor config block: `defaultSpanTagsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}` This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | -| `extraDimensionsFromEndpoint` | no | map of strings | A mapping of extra dimension names to a [discovery rule expression](https://docs.signalfx.com/en/latest/integrations/agent/auto-discovery.html) that is used to derive the value of the dimension. For example, to use a certain container label as a dimension, you could use something like this in your monitor config block: `extraDimensionsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}`. This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | +| `defaultSpanTagsFromEndpoint` | no | map of strings | A mapping of default span tag names to a [discovery rule expression](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#service-discovery-using-the-smart-agent) that is used to derive the default value of the span tag. For example, to use a certain container label as a span tag, you could use something like this in your monitor config block: `defaultSpanTagsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}` This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | +| `extraDimensionsFromEndpoint` | no | map of strings | A mapping of extra dimension names to a [discovery rule expression](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#service-discovery-using-the-smart-agent) that is used to derive the value of the dimension. For example, to use a certain container label as a dimension, you could use something like this in your monitor config block: `extraDimensionsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}`. This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | | `configEndpointMappings` | no | map of strings | A set of mappings from a configuration option on this monitor to attributes of a discovered endpoint. The keys are the config option on this monitor and the value can be any valid expression used in discovery rules. | | `intervalSeconds` | no | integer | The interval (in seconds) at which to emit datapoints from the monitor(s) created by this configuration. If not set (or set to 0), the global agent intervalSeconds config option will be used instead. (**default:** `0`) | | `solo` | no | bool | If one or more configurations have this set to true, only those configurations will be considered. This setting can be useful for testing. (**default:** `false`) | @@ -114,7 +114,7 @@ The following are generic options that apply to all monitors. Each monitor type | `disableEndpointDimensions` | no | bool | This can be set to true if you don't want to include the dimensions that are specific to the endpoint that was discovered by an observer. This is useful when you have an endpoint whose identity is not particularly important since it acts largely as a proxy or adapter for other metrics. (**default:** `false`) | | `metricNameTransformations` | no | map | A map from _original_ metric name to a replacement value. The keys are intepreted as regular expressions and the values can contain backreferences. This means that you should escape any RE characters in the original metric name with `\` (the most common escape necessary will be `\.` as period is interpreted as "all characters" if unescaped). The [Go regexp language](https://github.com/google/re2/wiki/Syntax), and backreferences are of the form `$1`. If there are multiple entries in list of maps, they will each be run in sequence, using the transformation from the previous entry as the input the subsequent transformation. To add a common prefix to all metrics coming out of a monitor, use a mapping like this: `(.*): myprefix.$1` | | `dimensionTransformations` | no | map of strings | A map from dimension names emitted by the monitor to the desired dimension name that will be emitted in the datapoint that goes to SignalFx. This can be useful if you have custom metrics from your applications and want to make the dimensions from a monitor match those. Also can be useful when scraping free-form metrics, say with the `prometheus-exporter` monitor. Right now, only static key/value transformations are supported. Note that filtering by dimensions will be done on the *original* dimension name and not the new name. Note that it is possible to remove unwanted dimensions via this configuration, by making the desired dimension name an empty string. | -| `extraMetrics` | no | list of strings | Extra metrics to enable besides the default included ones. This is an [overridable filter](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filtering). | +| `extraMetrics` | no | list of strings | Extra metrics to enable besides the default included ones. This is an [overridable filter](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). | | `extraGroups` | no | list of strings | Extra metric groups to enable in addition to the metrics that are emitted by default. A metric group is simply a collection of metrics, and they are defined in each monitor's documentation. | diff --git a/signalfx-agent/agent_docs/monitor-config.md b/signalfx-agent/agent_docs/monitor-config.md index 7a46ef0c..519dde0b 100644 --- a/signalfx-agent/agent_docs/monitor-config.md +++ b/signalfx-agent/agent_docs/monitor-config.md @@ -30,10 +30,10 @@ The following config options are common to all monitors: | `validateDiscoveryRule` | `false` | no | `bool` | If true, a warning will be emitted if a discovery rule contains variables that will never possibly match a rule. If using multiple observers, it is convenient to set this to false to suppress spurious errors. The top-level setting `validateDiscoveryRules` acts as a default if this isn't set. | | `extraDimensions` | | no | `map of strings` | A set of extra dimensions (key:value pairs) to include on datapoints emitted by the monitor(s) created from this configuration. To specify metrics from this monitor should be high-resolution, add the dimension `sf_hires: 1` | | `extraSpanTags` | | no | `map of strings` | A set of extra span tags (key:value pairs) to include on spans emitted by the monitor(s) created from this configuration. | -| `extraSpanTagsFromEndpoint` | | no | `map of strings` | A mapping of extra span tag names to a [discovery rule expression](https://docs.signalfx.com/en/latest/integrations/agent/auto-discovery.html) that is used to derive the value of the span tag. For example, to use a certain container label as a span tag, you could use something like this in your monitor config block: `extraSpanTagsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}`. This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | +| `extraSpanTagsFromEndpoint` | | no | `map of strings` | A mapping of extra span tag names to a [discovery rule expression](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#service-discovery-using-the-smart-agent) that is used to derive the value of the span tag. For example, to use a certain container label as a span tag, you could use something like this in your monitor config block: `extraSpanTagsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}`. This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | | `defaultSpanTags` | | no | `map of strings` | A set of default span tags (key:value pairs) to include on spans emitted by the monitor(s) created from this configuration. | -| `defaultSpanTagsFromEndpoint` | | no | `map of strings` | A mapping of default span tag names to a [discovery rule expression](https://docs.signalfx.com/en/latest/integrations/agent/auto-discovery.html) that is used to derive the default value of the span tag. For example, to use a certain container label as a span tag, you could use something like this in your monitor config block: `defaultSpanTagsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}` This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | -| `extraDimensionsFromEndpoint` | | no | `map of strings` | A mapping of extra dimension names to a [discovery rule expression](https://docs.signalfx.com/en/latest/integrations/agent/auto-discovery.html) that is used to derive the value of the dimension. For example, to use a certain container label as a dimension, you could use something like this in your monitor config block: `extraDimensionsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}`. This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | +| `defaultSpanTagsFromEndpoint` | | no | `map of strings` | A mapping of default span tag names to a [discovery rule expression](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#service-discovery-using-the-smart-agent) that is used to derive the default value of the span tag. For example, to use a certain container label as a span tag, you could use something like this in your monitor config block: `defaultSpanTagsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}` This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | +| `extraDimensionsFromEndpoint` | | no | `map of strings` | A mapping of extra dimension names to a [discovery rule expression](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#service-discovery-using-the-smart-agent) that is used to derive the value of the dimension. For example, to use a certain container label as a dimension, you could use something like this in your monitor config block: `extraDimensionsFromEndpoint: {env: 'Get(container_labels, "myapp.com/environment")'}`. This only applies when the monitor has a `discoveryRule` or was dynamically instantiated by an endpoint. It does nothing, for example, in the `signalfx-forwarder` montior. | | `configEndpointMappings` | | no | `map of strings` | A set of mappings from a configuration option on this monitor to attributes of a discovered endpoint. The keys are the config option on this monitor and the value can be any valid expression used in discovery rules. | | `intervalSeconds` | `0` | no | `integer` | The interval (in seconds) at which to emit datapoints from the monitor(s) created by this configuration. If not set (or set to 0), the global agent intervalSeconds config option will be used instead. | | `solo` | `false` | no | `bool` | If one or more configurations have this set to true, only those configurations will be considered. This setting can be useful for testing. | @@ -42,7 +42,7 @@ The following config options are common to all monitors: | `disableEndpointDimensions` | `false` | no | `bool` | This can be set to true if you don't want to include the dimensions that are specific to the endpoint that was discovered by an observer. This is useful when you have an endpoint whose identity is not particularly important since it acts largely as a proxy or adapter for other metrics. | | `metricNameTransformations` | | no | `map` | A map from _original_ metric name to a replacement value. The keys are intepreted as regular expressions and the values can contain backreferences. This means that you should escape any RE characters in the original metric name with `\` (the most common escape necessary will be `\.` as period is interpreted as "all characters" if unescaped). The [Go regexp language](https://github.com/google/re2/wiki/Syntax), and backreferences are of the form `$1`. If there are multiple entries in list of maps, they will each be run in sequence, using the transformation from the previous entry as the input the subsequent transformation. To add a common prefix to all metrics coming out of a monitor, use a mapping like this: `(.*): myprefix.$1` | | `dimensionTransformations` | | no | `map of strings` | A map from dimension names emitted by the monitor to the desired dimension name that will be emitted in the datapoint that goes to SignalFx. This can be useful if you have custom metrics from your applications and want to make the dimensions from a monitor match those. Also can be useful when scraping free-form metrics, say with the `prometheus-exporter` monitor. Right now, only static key/value transformations are supported. Note that filtering by dimensions will be done on the *original* dimension name and not the new name. Note that it is possible to remove unwanted dimensions via this configuration, by making the desired dimension name an empty string. | -| `extraMetrics` | | no | `list of strings` | Extra metrics to enable besides the default included ones. This is an [overridable filter](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filtering). | +| `extraMetrics` | | no | `list of strings` | Extra metrics to enable besides the default included ones. This is an [overridable filter](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). | | `extraGroups` | | no | `list of strings` | Extra metric groups to enable in addition to the metrics that are emitted by default. A metric group is simply a collection of metrics, and they are defined in each monitor's documentation. | diff --git a/signalfx-agent/agent_docs/monitors/appmesh.md b/signalfx-agent/agent_docs/monitors/appmesh.md index 36c4a1a0..aa847c3e 100644 --- a/signalfx-agent/agent_docs/monitors/appmesh.md +++ b/signalfx-agent/agent_docs/monitors/appmesh.md @@ -74,7 +74,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/aspdotnet.md b/signalfx-agent/agent_docs/monitors/aspdotnet.md index 20ae20f5..adfd8c8d 100644 --- a/signalfx-agent/agent_docs/monitors/aspdotnet.md +++ b/signalfx-agent/agent_docs/monitors/aspdotnet.md @@ -58,7 +58,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/cadvisor.md b/signalfx-agent/agent_docs/monitors/cadvisor.md index 46afde24..8aafa102 100644 --- a/signalfx-agent/agent_docs/monitors/cadvisor.md +++ b/signalfx-agent/agent_docs/monitors/cadvisor.md @@ -51,7 +51,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/cgroups.md b/signalfx-agent/agent_docs/monitors/cgroups.md index 2c33fc56..7f7fd23e 100644 --- a/signalfx-agent/agent_docs/monitors/cgroups.md +++ b/signalfx-agent/agent_docs/monitors/cgroups.md @@ -52,14 +52,14 @@ Configuration](../monitor-config.html#common-configuration).** | Config option | Required | Type | Description | | --- | --- | --- | --- | -| `cgroups` | no | `list of strings` | The cgroup names to include/exclude, based on the full hierarchy path. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters). If not provided, this defaults to all cgroups. E.g. to monitor all Docker container cgroups, you could use a value of `["/docker/*"]`. | +| `cgroups` | no | `list of strings` | The cgroup names to include/exclude, based on the full hierarchy path. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). If not provided, this defaults to all cgroups. E.g. to monitor all Docker container cgroups, you could use a value of `["/docker/*"]`. | ## Metrics These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/cloudfoundry-firehose-nozzle.md b/signalfx-agent/agent_docs/monitors/cloudfoundry-firehose-nozzle.md index 16ebe178..f765a653 100644 --- a/signalfx-agent/agent_docs/monitors/cloudfoundry-firehose-nozzle.md +++ b/signalfx-agent/agent_docs/monitors/cloudfoundry-firehose-nozzle.md @@ -79,7 +79,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-activemq.md b/signalfx-agent/agent_docs/monitors/collectd-activemq.md index 7a25299a..f8f91d18 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-activemq.md +++ b/signalfx-agent/agent_docs/monitors/collectd-activemq.md @@ -13,7 +13,7 @@ Monitor Type: `collectd/activemq` ([Source](https://github.com/signalfx/signalfx ## Overview SignalFx's integration with ActiveMQ wraps the [Collectd GenericJMX -monitor](https://docs.signalfx.com/en/latest/integrations/agent/monitors/collectd-genericjmx.html) +monitor](https://docs.splunk.com/observability/gdi/genericjmx/genericjmx.html) to monitor ActiveMQ. Use this monitor to gather the following types of information from ActiveMQ: @@ -23,7 +23,7 @@ Use this monitor to gather the following types of information from ActiveMQ: * Topic (Topic status) To monitor the age of messages inside ActiveMQ queues, see [ActiveMQ -message age listener](https://docs.signalfx.com/en/latest/integrations/integrations-reference/integrations.activemq.message.age.listener.html). +message age listener](https://docs.splunk.com/observability/gdi/activemq/activemq.html). ## Example config @@ -95,7 +95,7 @@ The **nested** `values` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-apache.md b/signalfx-agent/agent_docs/monitors/collectd-apache.md index e2692cbf..1838af75 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-apache.md +++ b/signalfx-agent/agent_docs/monitors/collectd-apache.md @@ -103,7 +103,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-cassandra.md b/signalfx-agent/agent_docs/monitors/collectd-cassandra.md index ba83e0df..fddda5ae 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-cassandra.md +++ b/signalfx-agent/agent_docs/monitors/collectd-cassandra.md @@ -87,7 +87,7 @@ The **nested** `values` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-consul.md b/signalfx-agent/agent_docs/monitors/collectd-consul.md index a48a3b09..153bce4f 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-consul.md +++ b/signalfx-agent/agent_docs/monitors/collectd-consul.md @@ -80,7 +80,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-couchbase.md b/signalfx-agent/agent_docs/monitors/collectd-couchbase.md index f12311e2..cabdc8c5 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-couchbase.md +++ b/signalfx-agent/agent_docs/monitors/collectd-couchbase.md @@ -85,7 +85,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-cpu.md b/signalfx-agent/agent_docs/monitors/collectd-cpu.md index c0dd7193..d5848460 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-cpu.md +++ b/signalfx-agent/agent_docs/monitors/collectd-cpu.md @@ -45,7 +45,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-cpufreq.md b/signalfx-agent/agent_docs/monitors/collectd-cpufreq.md index bfed1e6f..885a6490 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-cpufreq.md +++ b/signalfx-agent/agent_docs/monitors/collectd-cpufreq.md @@ -38,7 +38,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/collectd-df.md b/signalfx-agent/agent_docs/monitors/collectd-df.md index 352bf0d8..5b9f235f 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-df.md +++ b/signalfx-agent/agent_docs/monitors/collectd-df.md @@ -51,7 +51,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-disk.md b/signalfx-agent/agent_docs/monitors/collectd-disk.md index 4e8748dd..9adb535d 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-disk.md +++ b/signalfx-agent/agent_docs/monitors/collectd-disk.md @@ -49,7 +49,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-elasticsearch.md b/signalfx-agent/agent_docs/monitors/collectd-elasticsearch.md index da343809..14e448ea 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-elasticsearch.md +++ b/signalfx-agent/agent_docs/monitors/collectd-elasticsearch.md @@ -60,7 +60,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-etcd.md b/signalfx-agent/agent_docs/monitors/collectd-etcd.md index b2215211..f73bf08d 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-etcd.md +++ b/signalfx-agent/agent_docs/monitors/collectd-etcd.md @@ -49,7 +49,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-genericjmx.md b/signalfx-agent/agent_docs/monitors/collectd-genericjmx.md index d40688c5..5eb24f89 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-genericjmx.md +++ b/signalfx-agent/agent_docs/monitors/collectd-genericjmx.md @@ -169,7 +169,7 @@ The **nested** `values` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-hadoop.md b/signalfx-agent/agent_docs/monitors/collectd-hadoop.md index 4f0884ad..8215827b 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-hadoop.md +++ b/signalfx-agent/agent_docs/monitors/collectd-hadoop.md @@ -76,7 +76,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-hadoopjmx.md b/signalfx-agent/agent_docs/monitors/collectd-hadoopjmx.md index 996429ec..d99d95b5 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-hadoopjmx.md +++ b/signalfx-agent/agent_docs/monitors/collectd-hadoopjmx.md @@ -136,7 +136,7 @@ The **nested** `values` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-interface.md b/signalfx-agent/agent_docs/monitors/collectd-interface.md index d9661964..d85c2a91 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-interface.md +++ b/signalfx-agent/agent_docs/monitors/collectd-interface.md @@ -48,7 +48,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-jenkins.md b/signalfx-agent/agent_docs/monitors/collectd-jenkins.md index e161f37d..3ccdcc17 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-jenkins.md +++ b/signalfx-agent/agent_docs/monitors/collectd-jenkins.md @@ -90,7 +90,7 @@ Configuration](../monitor-config.html#common-configuration).** | `path` | no | `string` | | | `metricsKey` | **yes** | `string` | Key required for collecting metrics. The access key located at `Manage Jenkins > Configure System > Metrics > ADD.` If empty, click `Generate`. | | `enhancedMetrics` | no | `bool` | Whether to enable enhanced metrics (**default:** `false`) | -| `excludeJobMetrics` | no | `bool` | Set to *true* to to exclude job metrics retrieved from `/api/json` endpoint (**default:** `false`) | +| `excludeJobMetrics` | no | `bool` | Set to *true* to exclude job metrics retrieved from `/api/json` endpoint (**default:** `false`) | | `includeMetrics` | no | `list of strings` | Used to enable individual enhanced metrics when `enhancedMetrics` is false | | `username` | no | `string` | User with security access to jenkins | | `apiToken` | no | `string` | API Token of the user | @@ -105,7 +105,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/collectd-kafka.md b/signalfx-agent/agent_docs/monitors/collectd-kafka.md index d7cdf4d4..338075ee 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-kafka.md +++ b/signalfx-agent/agent_docs/monitors/collectd-kafka.md @@ -27,7 +27,7 @@ apart from the list of default metrics, kafka.server:type=ZooKeeperClientMetrics is a good metric to monitor since it gives an understanding of how long brokers wait for requests to Zookeeper to be completed. Since Zookeeper is an integral part of a Kafka cluster, monitoring it using the [Zookeeper -monitor](https://docs.signalfx.com/en/latest/integrations/agent/monitors/collectd-zookeeper.html) +monitor](https://docs.splunk.com/observability/gdi/zookeeper/zookeeper.html) is recommended. It is also a good idea to monitor disk utilization and network metrics of the underlying host. @@ -91,7 +91,7 @@ The **nested** `values` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-kafka_consumer.md b/signalfx-agent/agent_docs/monitors/collectd-kafka_consumer.md index 836c546b..6506e324 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-kafka_consumer.md +++ b/signalfx-agent/agent_docs/monitors/collectd-kafka_consumer.md @@ -95,7 +95,7 @@ The **nested** `values` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-kafka_producer.md b/signalfx-agent/agent_docs/monitors/collectd-kafka_producer.md index 779f7e1c..8cd0fdc9 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-kafka_producer.md +++ b/signalfx-agent/agent_docs/monitors/collectd-kafka_producer.md @@ -87,7 +87,7 @@ The **nested** `values` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-kong.md b/signalfx-agent/agent_docs/monitors/collectd-kong.md index eb853b0e..d9a1e24f 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-kong.md +++ b/signalfx-agent/agent_docs/monitors/collectd-kong.md @@ -176,7 +176,7 @@ The **nested** `metrics` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-load.md b/signalfx-agent/agent_docs/monitors/collectd-load.md index 5e6beb0b..a763d9dc 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-load.md +++ b/signalfx-agent/agent_docs/monitors/collectd-load.md @@ -40,7 +40,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-marathon.md b/signalfx-agent/agent_docs/monitors/collectd-marathon.md index 9f16986f..aef6f35b 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-marathon.md +++ b/signalfx-agent/agent_docs/monitors/collectd-marathon.md @@ -16,7 +16,7 @@ Monitors a Mesos Marathon instance using the [collectd Marathon Python plugin](https://github.com/signalfx/collectd-marathon). See the [integrations -doc](https://docs.signalfx.com/en/latest/integrations/integrations-reference/integrations.marathon.html) +doc](https://docs.splunk.com/observability/gdi/marathon/marathon.html) for more information on configuration. Sample YAML configuration: @@ -71,7 +71,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/collectd-memcached.md b/signalfx-agent/agent_docs/monitors/collectd-memcached.md index e7444c42..67a2728c 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-memcached.md +++ b/signalfx-agent/agent_docs/monitors/collectd-memcached.md @@ -53,7 +53,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-memory.md b/signalfx-agent/agent_docs/monitors/collectd-memory.md index e915e20f..156ea59d 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-memory.md +++ b/signalfx-agent/agent_docs/monitors/collectd-memory.md @@ -36,7 +36,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-mongodb.md b/signalfx-agent/agent_docs/monitors/collectd-mongodb.md index ef9d6f4b..0fd98179 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-mongodb.md +++ b/signalfx-agent/agent_docs/monitors/collectd-mongodb.md @@ -38,11 +38,31 @@ Documentation for MongoDB can be found [here](http://docs.mongodb.org/manual/). If you're monitoring a secured MongoDB deployment, it is a good practice to create a MongoDB user with minimal read-only roles, as follows: +If the monitor is configured to send collection level metrics, you need to create and add this role so your user has permission to run collStats and indexStats +against system collections and any collection in the db you're monitoring. +In the below role, we're adding the appropriate permissions for system collections under the admin db. +For more details on how to add all your non-admin collections, check https://www.mongodb.com/docs/manual/reference/resource-document/ + +``` +use admin +db.createRole( + { + role: "splunkMonitor", + privileges: [ { resource: { db: 'admin', collection: 'system.roles' }, actions: [ 'collStats', 'indexStats' ] }, + { resource: { db: 'admin', collection: 'system.users' }, actions: [ 'collStats', 'indexStats' ] }, + { resource: { db: 'admin', collection: 'system.version' }, actions: [ 'collStats', 'indexStats' ] } ], + roles: [ { role: "read", db: "admin" } ] + }, + { w: "majority" , wtimeout: 5000 } +) +``` + ``` +use admin db.createUser( { user: "collectd", pwd: "collectd", - roles: [ { role: "readAnyDatabase", db: "admin" }, { role: "clusterMonitor", db: "admin" } ] + roles: [ { role: "readAnyDatabase", db: "admin" }, { role: "clusterMonitor", db: "admin" }, {role: "splunkMonitor", db: "admin"} ] }); ``` @@ -83,7 +103,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-mysql.md b/signalfx-agent/agent_docs/monitors/collectd-mysql.md index bbe9d8c1..85c2b9e8 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-mysql.md +++ b/signalfx-agent/agent_docs/monitors/collectd-mysql.md @@ -107,7 +107,7 @@ The **nested** `databases` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-nginx.md b/signalfx-agent/agent_docs/monitors/collectd-nginx.md index 5af37050..42464098 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-nginx.md +++ b/signalfx-agent/agent_docs/monitors/collectd-nginx.md @@ -58,7 +58,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-opcache.md b/signalfx-agent/agent_docs/monitors/collectd-opcache.md index cdbe3ee9..c4e36fde 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-opcache.md +++ b/signalfx-agent/agent_docs/monitors/collectd-opcache.md @@ -125,7 +125,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. **All of the metrics emitted from this monitor are categorized as -[custom](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics)** +[custom](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics)** but the ones that are emitted by default from the monitor are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-openstack.md b/signalfx-agent/agent_docs/monitors/collectd-openstack.md index bb9aff23..b4a3b58d 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-openstack.md +++ b/signalfx-agent/agent_docs/monitors/collectd-openstack.md @@ -100,7 +100,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-php-fpm.md b/signalfx-agent/agent_docs/monitors/collectd-php-fpm.md index 9cf1a434..6bba841f 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-php-fpm.md +++ b/signalfx-agent/agent_docs/monitors/collectd-php-fpm.md @@ -100,7 +100,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-postgresql.md b/signalfx-agent/agent_docs/monitors/collectd-postgresql.md index 3302ffeb..b56ebfbd 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-postgresql.md +++ b/signalfx-agent/agent_docs/monitors/collectd-postgresql.md @@ -142,7 +142,7 @@ The **nested** `results` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-processes.md b/signalfx-agent/agent_docs/monitors/collectd-processes.md index 6aab6173..859bfbe9 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-processes.md +++ b/signalfx-agent/agent_docs/monitors/collectd-processes.md @@ -66,7 +66,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/collectd-protocols.md b/signalfx-agent/agent_docs/monitors/collectd-protocols.md index 086876ae..de5b4bbf 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-protocols.md +++ b/signalfx-agent/agent_docs/monitors/collectd-protocols.md @@ -37,7 +37,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-rabbitmq.md b/signalfx-agent/agent_docs/monitors/collectd-rabbitmq.md index eab436bf..12cbf24f 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-rabbitmq.md +++ b/signalfx-agent/agent_docs/monitors/collectd-rabbitmq.md @@ -66,7 +66,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-redis.md b/signalfx-agent/agent_docs/monitors/collectd-redis.md index 7ded319d..cc6efe03 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-redis.md +++ b/signalfx-agent/agent_docs/monitors/collectd-redis.md @@ -111,7 +111,7 @@ The **nested** `sendListLengths` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-signalfx-metadata.md b/signalfx-agent/agent_docs/monitors/collectd-signalfx-metadata.md index fa8646d7..31dbf7d0 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-signalfx-metadata.md +++ b/signalfx-agent/agent_docs/monitors/collectd-signalfx-metadata.md @@ -57,7 +57,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-solr.md b/signalfx-agent/agent_docs/monitors/collectd-solr.md index ec8a8179..24d1a1e0 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-solr.md +++ b/signalfx-agent/agent_docs/monitors/collectd-solr.md @@ -66,7 +66,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-spark.md b/signalfx-agent/agent_docs/monitors/collectd-spark.md index 9c033c46..a8908b10 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-spark.md +++ b/signalfx-agent/agent_docs/monitors/collectd-spark.md @@ -77,7 +77,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-statsd.md b/signalfx-agent/agent_docs/monitors/collectd-statsd.md index 5019883c..88d24e19 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-statsd.md +++ b/signalfx-agent/agent_docs/monitors/collectd-statsd.md @@ -66,7 +66,7 @@ implementation by Etsy. If you are only looking at the counts generated by each reporting interval, equivalent to -[Counters](https://docs.signalfx.com/en/latest/metrics-metadata/metric-types.html?highlight=Counters) +[Counters](https://docs.splunk.com/observability/metrics-and-metadata/metric-types.html?highlight=Counters#nav-Identify-metric-types) in SignalFx then we'd recommend that you set CounterSum to `True`. It will send in an additional counter metric with a prefix of `count`. diff --git a/signalfx-agent/agent_docs/monitors/collectd-systemd.md b/signalfx-agent/agent_docs/monitors/collectd-systemd.md index 9fd8d926..b3618b09 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-systemd.md +++ b/signalfx-agent/agent_docs/monitors/collectd-systemd.md @@ -79,7 +79,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-tomcat.md b/signalfx-agent/agent_docs/monitors/collectd-tomcat.md index e1bad9ca..23fc5234 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-tomcat.md +++ b/signalfx-agent/agent_docs/monitors/collectd-tomcat.md @@ -81,7 +81,7 @@ The **nested** `values` config object has the following fields: These are the metrics available for this monitor. **All of the metrics emitted from this monitor are categorized as -[custom](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics)** +[custom](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics)** but the ones that are emitted by default from the monitor are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-uptime.md b/signalfx-agent/agent_docs/monitors/collectd-uptime.md index abacfde6..57530b94 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-uptime.md +++ b/signalfx-agent/agent_docs/monitors/collectd-uptime.md @@ -37,7 +37,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-vmem.md b/signalfx-agent/agent_docs/monitors/collectd-vmem.md index 8f4bfa9a..0be16dd1 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-vmem.md +++ b/signalfx-agent/agent_docs/monitors/collectd-vmem.md @@ -42,7 +42,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/collectd-zookeeper.md b/signalfx-agent/agent_docs/monitors/collectd-zookeeper.md index f65961cd..be08a711 100644 --- a/signalfx-agent/agent_docs/monitors/collectd-zookeeper.md +++ b/signalfx-agent/agent_docs/monitors/collectd-zookeeper.md @@ -45,7 +45,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/conviva.md b/signalfx-agent/agent_docs/monitors/conviva.md index 5932bbbe..af850632 100644 --- a/signalfx-agent/agent_docs/monitors/conviva.md +++ b/signalfx-agent/agent_docs/monitors/conviva.md @@ -173,7 +173,7 @@ The **nested** `metricConfigs` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/coredns.md b/signalfx-agent/agent_docs/monitors/coredns.md index e2db0138..e56cbc9c 100644 --- a/signalfx-agent/agent_docs/monitors/coredns.md +++ b/signalfx-agent/agent_docs/monitors/coredns.md @@ -64,7 +64,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/cpu.md b/signalfx-agent/agent_docs/monitors/cpu.md index 2c6bd184..dd2596a2 100644 --- a/signalfx-agent/agent_docs/monitors/cpu.md +++ b/signalfx-agent/agent_docs/monitors/cpu.md @@ -49,7 +49,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/disk-io.md b/signalfx-agent/agent_docs/monitors/disk-io.md index b8c7a9b0..7df0607c 100644 --- a/signalfx-agent/agent_docs/monitors/disk-io.md +++ b/signalfx-agent/agent_docs/monitors/disk-io.md @@ -42,7 +42,7 @@ Configuration](../monitor-config.html#common-configuration).** | Config option | Required | Type | Description | | --- | --- | --- | --- | -| `disks` | no | `list of strings` | The devices to include/exclude. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters). (**default:** `[* !/^loop[0-9]+$/ !/^dm-[0-9]+$/]`) | +| `disks` | no | `list of strings` | The devices to include/exclude. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). (**default:** `[* !/^loop[0-9]+$/ !/^dm-[0-9]+$/]`) | | `counterRefreshInterval` | no | `int64` | (Windows Only) The frequency that wildcards in counter paths should be expanded and how often to refresh counters from configuration. This is expressed as a duration. (**default:** `60s`) | | `printValid` | no | `bool` | (Windows Only) Print out the configurations that match available performance counters. This used for debugging. (**default:** `false`) | @@ -51,7 +51,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/docker-container-stats.md b/signalfx-agent/agent_docs/monitors/docker-container-stats.md index 37a0a205..04c85c48 100644 --- a/signalfx-agent/agent_docs/monitors/docker-container-stats.md +++ b/signalfx-agent/agent_docs/monitors/docker-container-stats.md @@ -64,7 +64,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/dotnet.md b/signalfx-agent/agent_docs/monitors/dotnet.md index bd831494..c87b4e17 100644 --- a/signalfx-agent/agent_docs/monitors/dotnet.md +++ b/signalfx-agent/agent_docs/monitors/dotnet.md @@ -66,7 +66,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/ecs-metadata.md b/signalfx-agent/agent_docs/monitors/ecs-metadata.md index e85ce20f..0df94095 100644 --- a/signalfx-agent/agent_docs/monitors/ecs-metadata.md +++ b/signalfx-agent/agent_docs/monitors/ecs-metadata.md @@ -50,7 +50,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/elasticsearch.md b/signalfx-agent/agent_docs/monitors/elasticsearch.md index f0dfb513..4cf14a9d 100644 --- a/signalfx-agent/agent_docs/monitors/elasticsearch.md +++ b/signalfx-agent/agent_docs/monitors/elasticsearch.md @@ -181,7 +181,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/etcd.md b/signalfx-agent/agent_docs/monitors/etcd.md index 20f3a409..547a9e3c 100644 --- a/signalfx-agent/agent_docs/monitors/etcd.md +++ b/signalfx-agent/agent_docs/monitors/etcd.md @@ -75,7 +75,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/expvar.md b/signalfx-agent/agent_docs/monitors/expvar.md index 019bd793..0cd3bfa9 100644 --- a/signalfx-agent/agent_docs/monitors/expvar.md +++ b/signalfx-agent/agent_docs/monitors/expvar.md @@ -264,7 +264,7 @@ The **nested** `dimensions` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/filesystems.md b/signalfx-agent/agent_docs/monitors/filesystems.md index ebdef072..21426248 100644 --- a/signalfx-agent/agent_docs/monitors/filesystems.md +++ b/signalfx-agent/agent_docs/monitors/filesystems.md @@ -66,8 +66,8 @@ Configuration](../monitor-config.html#common-configuration).** | Config option | Required | Type | Description | | --- | --- | --- | --- | | `hostFSPath` | no | `string` | Path to the root of the host filesystem. Useful when running in a container and the host filesystem is mounted in some subdirectory under /. The disk usage metrics emitted will be based at this path. | -| `fsTypes` | no | `list of strings` | The filesystem types to include/exclude. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters). If this is not set, the default value is the set of all **non-logical/virtual filesystems** on the system. On Linux this list is determined by reading the `/proc/filesystems` file and choosing the filesystems that do not have the `nodev` modifier. | -| `mountPoints` | no | `list of strings` | The mount paths to include/exclude. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters). NOTE: If you are using the hostFSPath option you should not include the `/hostfs/` mount in the filter. If both this and `fsTypes` is specified, the two filters combine in an AND relationship. | +| `fsTypes` | no | `list of strings` | The filesystem types to include/exclude. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). If this is not set, the default value is the set of all **non-logical/virtual filesystems** on the system. On Linux this list is determined by reading the `/proc/filesystems` file and choosing the filesystems that do not have the `nodev` modifier. | +| `mountPoints` | no | `list of strings` | The mount paths to include/exclude. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). NOTE: If you are using the hostFSPath option you should not include the `/hostfs/` mount in the filter. If both this and `fsTypes` is specified, the two filters combine in an AND relationship. | | `sendModeDimension` | no | `bool` | Set to true to emit the "mode" dimension, which represents whether the mount is "rw" or "ro". (**default:** `false`) | @@ -75,7 +75,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/gitlab-gitaly.md b/signalfx-agent/agent_docs/monitors/gitlab-gitaly.md index 3f26de0d..311da5c4 100644 --- a/signalfx-agent/agent_docs/monitors/gitlab-gitaly.md +++ b/signalfx-agent/agent_docs/monitors/gitlab-gitaly.md @@ -53,7 +53,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/gitlab-runner.md b/signalfx-agent/agent_docs/monitors/gitlab-runner.md index c88e217d..71ff53be 100644 --- a/signalfx-agent/agent_docs/monitors/gitlab-runner.md +++ b/signalfx-agent/agent_docs/monitors/gitlab-runner.md @@ -64,7 +64,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/gitlab-sidekiq.md b/signalfx-agent/agent_docs/monitors/gitlab-sidekiq.md index 85631872..9201fd34 100644 --- a/signalfx-agent/agent_docs/monitors/gitlab-sidekiq.md +++ b/signalfx-agent/agent_docs/monitors/gitlab-sidekiq.md @@ -53,7 +53,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/gitlab-unicorn.md b/signalfx-agent/agent_docs/monitors/gitlab-unicorn.md index 6ff68714..a89f4b0d 100644 --- a/signalfx-agent/agent_docs/monitors/gitlab-unicorn.md +++ b/signalfx-agent/agent_docs/monitors/gitlab-unicorn.md @@ -72,7 +72,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/gitlab-workhorse.md b/signalfx-agent/agent_docs/monitors/gitlab-workhorse.md index 7c9c8dd9..87ec92d5 100644 --- a/signalfx-agent/agent_docs/monitors/gitlab-workhorse.md +++ b/signalfx-agent/agent_docs/monitors/gitlab-workhorse.md @@ -67,7 +67,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/gitlab.md b/signalfx-agent/agent_docs/monitors/gitlab.md index 65554e5d..0470bd4d 100644 --- a/signalfx-agent/agent_docs/monitors/gitlab.md +++ b/signalfx-agent/agent_docs/monitors/gitlab.md @@ -191,7 +191,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/hana.md b/signalfx-agent/agent_docs/monitors/hana.md index 89afc0a0..6d12da07 100644 --- a/signalfx-agent/agent_docs/monitors/hana.md +++ b/signalfx-agent/agent_docs/monitors/hana.md @@ -50,7 +50,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/haproxy.md b/signalfx-agent/agent_docs/monitors/haproxy.md index 7d73f4ae..76d582f7 100644 --- a/signalfx-agent/agent_docs/monitors/haproxy.md +++ b/signalfx-agent/agent_docs/monitors/haproxy.md @@ -91,7 +91,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/heroku-metadata.md b/signalfx-agent/agent_docs/monitors/heroku-metadata.md index 23655fe3..873747b3 100644 --- a/signalfx-agent/agent_docs/monitors/heroku-metadata.md +++ b/signalfx-agent/agent_docs/monitors/heroku-metadata.md @@ -39,7 +39,7 @@ This monitor has no configuration options. ## Properties The following -[properties](https://docs.signalfx.com/en/latest/metrics-metadata/metrics-metadata.html#properties) +[properties](https://docs.splunk.com/observability/metrics-and-metadata/metrics-dimensions-mts.html#properties) are set on the dimension values of the dimension specified. | Name | Dimension | Description | diff --git a/signalfx-agent/agent_docs/monitors/host-metadata.md b/signalfx-agent/agent_docs/monitors/host-metadata.md index ecce0001..16ec4fd0 100644 --- a/signalfx-agent/agent_docs/monitors/host-metadata.md +++ b/signalfx-agent/agent_docs/monitors/host-metadata.md @@ -57,7 +57,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/http.md b/signalfx-agent/agent_docs/monitors/http.md index 075d6318..8795f210 100644 --- a/signalfx-agent/agent_docs/monitors/http.md +++ b/signalfx-agent/agent_docs/monitors/http.md @@ -192,7 +192,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/internal-metrics.md b/signalfx-agent/agent_docs/monitors/internal-metrics.md index efbd918f..5ba956bf 100644 --- a/signalfx-agent/agent_docs/monitors/internal-metrics.md +++ b/signalfx-agent/agent_docs/monitors/internal-metrics.md @@ -53,7 +53,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/jmx.md b/signalfx-agent/agent_docs/monitors/jmx.md index d7153c23..9af023d1 100644 --- a/signalfx-agent/agent_docs/monitors/jmx.md +++ b/signalfx-agent/agent_docs/monitors/jmx.md @@ -143,7 +143,7 @@ Configuration](../monitor-config.html#common-configuration).** | `host` | no | `string` | Host will be filled in by auto-discovery if this monitor has a discovery rule. | | `port` | no | `integer` | Port will be filled in by auto-discovery if this monitor has a discovery rule. (**default:** `0`) | | `serviceURL` | no | `string` | The service URL for the JMX RMI/JMXMP endpoint. If empty it will be filled in with values from `host` and `port` using a standard JMX RMI template: `service:jmx:rmi:///jndi/rmi://:/jmxrmi`. If overridden, `host` and `port` will have no effect. For JMXMP endpoint the service URL must be specified. The JMXMP endpoint URL format is `service:jmx:jmxmp://:`. | -| `groovyScript` | **yes** | `string` | A literal Groovy script that generates datapoints from JMX MBeans. See the top-level `jmx` monitor doc for more information on how to write this script. You can put the Groovy script in a separate file and refer to it here with the [remote config reference](https://docs.signalfx.com/en/latest/integrations/agent/remote-config.html) `{"#from": "/path/to/file.groovy", raw: true}`, or you can put it straight in YAML by using the `|` heredoc syntax. | +| `groovyScript` | **yes** | `string` | A literal Groovy script that generates datapoints from JMX MBeans. See the top-level `jmx` monitor doc for more information on how to write this script. You can put the Groovy script in a separate file and refer to it here with the [remote config reference](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#configure-the-smart-agent) `{"#from": "/path/to/file.groovy", raw: true}`, or you can put it straight in YAML by using the `|` heredoc syntax. | | `username` | no | `string` | Username for JMX authentication, if applicable. | | `password` | no | `string` | Password for JMX authentication, if applicable. | | `keyStorePath` | no | `string` | The key store path is required if client authentication is enabled on the target JVM. | diff --git a/signalfx-agent/agent_docs/monitors/kube-controller-manager.md b/signalfx-agent/agent_docs/monitors/kube-controller-manager.md index 6619f0ad..ddfff8f5 100644 --- a/signalfx-agent/agent_docs/monitors/kube-controller-manager.md +++ b/signalfx-agent/agent_docs/monitors/kube-controller-manager.md @@ -70,7 +70,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/kubelet-metrics.md b/signalfx-agent/agent_docs/monitors/kubelet-metrics.md index 7367a659..0b067510 100644 --- a/signalfx-agent/agent_docs/monitors/kubelet-metrics.md +++ b/signalfx-agent/agent_docs/monitors/kubelet-metrics.md @@ -69,7 +69,7 @@ The **nested** `kubeletAPI` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/kubelet-stats.md b/signalfx-agent/agent_docs/monitors/kubelet-stats.md index 9e8df900..2162395c 100644 --- a/signalfx-agent/agent_docs/monitors/kubelet-stats.md +++ b/signalfx-agent/agent_docs/monitors/kubelet-stats.md @@ -90,7 +90,7 @@ The **nested** `kubeletAPI` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/kubernetes-apiserver.md b/signalfx-agent/agent_docs/monitors/kubernetes-apiserver.md index d51face7..5533d1c3 100644 --- a/signalfx-agent/agent_docs/monitors/kubernetes-apiserver.md +++ b/signalfx-agent/agent_docs/monitors/kubernetes-apiserver.md @@ -65,7 +65,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/kubernetes-cluster.md b/signalfx-agent/agent_docs/monitors/kubernetes-cluster.md index c511cbd6..ffc8a67b 100644 --- a/signalfx-agent/agent_docs/monitors/kubernetes-cluster.md +++ b/signalfx-agent/agent_docs/monitors/kubernetes-cluster.md @@ -74,7 +74,7 @@ The **nested** `kubernetesAPI` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. @@ -167,7 +167,7 @@ dimensions may be specific to certain metrics. ## Properties The following -[properties](https://docs.signalfx.com/en/latest/metrics-metadata/metrics-metadata.html#properties) +[properties](https://docs.splunk.com/observability/metrics-and-metadata/metrics-dimensions-mts.html#properties) are set on the dimension values of the dimension specified. | Name | Dimension | Description | diff --git a/signalfx-agent/agent_docs/monitors/kubernetes-proxy.md b/signalfx-agent/agent_docs/monitors/kubernetes-proxy.md index f2e6b30f..99753e4c 100644 --- a/signalfx-agent/agent_docs/monitors/kubernetes-proxy.md +++ b/signalfx-agent/agent_docs/monitors/kubernetes-proxy.md @@ -68,7 +68,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/kubernetes-scheduler.md b/signalfx-agent/agent_docs/monitors/kubernetes-scheduler.md index defb9427..99ee95ec 100644 --- a/signalfx-agent/agent_docs/monitors/kubernetes-scheduler.md +++ b/signalfx-agent/agent_docs/monitors/kubernetes-scheduler.md @@ -53,7 +53,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/kubernetes-volumes.md b/signalfx-agent/agent_docs/monitors/kubernetes-volumes.md index 205c3d04..cdb3fdd2 100644 --- a/signalfx-agent/agent_docs/monitors/kubernetes-volumes.md +++ b/signalfx-agent/agent_docs/monitors/kubernetes-volumes.md @@ -89,7 +89,7 @@ The **nested** `kubernetesAPI` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/load.md b/signalfx-agent/agent_docs/monitors/load.md index 49e4cf4a..c0a8ce75 100644 --- a/signalfx-agent/agent_docs/monitors/load.md +++ b/signalfx-agent/agent_docs/monitors/load.md @@ -46,7 +46,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/logstash.md b/signalfx-agent/agent_docs/monitors/logstash.md index 3e77d420..13da55b3 100644 --- a/signalfx-agent/agent_docs/monitors/logstash.md +++ b/signalfx-agent/agent_docs/monitors/logstash.md @@ -43,7 +43,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/memory.md b/signalfx-agent/agent_docs/monitors/memory.md index 8f4fe3e9..82e0f5ac 100644 --- a/signalfx-agent/agent_docs/monitors/memory.md +++ b/signalfx-agent/agent_docs/monitors/memory.md @@ -45,7 +45,7 @@ This monitor has no configuration options. These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/mongodb-atlas.md b/signalfx-agent/agent_docs/monitors/mongodb-atlas.md index e492ac52..c3390b25 100644 --- a/signalfx-agent/agent_docs/monitors/mongodb-atlas.md +++ b/signalfx-agent/agent_docs/monitors/mongodb-atlas.md @@ -70,7 +70,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/nagios.md b/signalfx-agent/agent_docs/monitors/nagios.md index efb5b725..7c7b9f1f 100644 --- a/signalfx-agent/agent_docs/monitors/nagios.md +++ b/signalfx-agent/agent_docs/monitors/nagios.md @@ -19,14 +19,14 @@ It will run the script set in `command` parameter and send the [state](https://nagios-plugins.org/doc/guidelines.html#AEN78) of the check depending on the exit code of the command. -It is very similar to [telegraf/exec](https://docs.signalfx.com/en/latest/integrations/agent/monitors/telegraf-exec.html) +It is very similar to [telegraf/exec](https://docs.splunk.com/observability/gdi/exec/telegraf-exec.html) monitor configured with `dataFormat: nagios` but: - it does not retrieve perfdata metrics, only the state of the script for alerting purpose. - it will override the state if exit code == 0 but output string starts with `warn`, `crit` or `unkn` (not case sensitive). Also the main advantage and purpose of this monitor is to add more context to this status check state -thougth SignalFx [events](https://docs.signalfx.com/en/latest/detect-alert/events-intro.html). +thougth SignalFx [events](https://docs.splunk.com/observability/metrics-and-metadata/view-data-events.html). Indeed, in addition to the state metric, it will send an event which includes the output and the error caught from the command execution. @@ -68,7 +68,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. **All of the metrics emitted from this monitor are categorized as -[custom](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics)** +[custom](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics)** but the ones that are emitted by default from the monitor are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/net-io.md b/signalfx-agent/agent_docs/monitors/net-io.md index cedd0d89..3a1ecf95 100644 --- a/signalfx-agent/agent_docs/monitors/net-io.md +++ b/signalfx-agent/agent_docs/monitors/net-io.md @@ -42,14 +42,14 @@ Configuration](../monitor-config.html#common-configuration).** | Config option | Required | Type | Description | | --- | --- | --- | --- | -| `interfaces` | no | `list of strings` | The network interfaces to send metrics about. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters). (**default:** `[* !/^lo\d*$/ !/^docker.*/ !/^t(un|ap)\d*$/ !/^veth.*$/ !/^Loopback*/]`) | +| `interfaces` | no | `list of strings` | The network interfaces to send metrics about. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). (**default:** `[* !/^lo\d*$/ !/^docker.*/ !/^t(un|ap)\d*$/ !/^veth.*$/ !/^Loopback*/]`) | ## Metrics These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/ntp.md b/signalfx-agent/agent_docs/monitors/ntp.md index 373a1d13..197065de 100644 --- a/signalfx-agent/agent_docs/monitors/ntp.md +++ b/signalfx-agent/agent_docs/monitors/ntp.md @@ -44,7 +44,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/openshift-cluster.md b/signalfx-agent/agent_docs/monitors/openshift-cluster.md index 09ad02df..1aa3db7c 100644 --- a/signalfx-agent/agent_docs/monitors/openshift-cluster.md +++ b/signalfx-agent/agent_docs/monitors/openshift-cluster.md @@ -75,7 +75,7 @@ The **nested** `kubernetesAPI` config object has the following fields: These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. @@ -196,7 +196,7 @@ dimensions may be specific to certain metrics. ## Properties The following -[properties](https://docs.signalfx.com/en/latest/metrics-metadata/metrics-metadata.html#properties) +[properties](https://docs.splunk.com/observability/metrics-and-metadata/metrics-dimensions-mts.html#properties) are set on the dimension values of the dimension specified. | Name | Dimension | Description | diff --git a/signalfx-agent/agent_docs/monitors/postgresql.md b/signalfx-agent/agent_docs/monitors/postgresql.md index 97f68bdb..f8eeef59 100644 --- a/signalfx-agent/agent_docs/monitors/postgresql.md +++ b/signalfx-agent/agent_docs/monitors/postgresql.md @@ -103,7 +103,7 @@ Configuration](../monitor-config.html#common-configuration).** | `masterDBName` | no | `string` | The "master" database to which the agent first connects to query the list of databases available in the server. This database should be accessible to the user specified with `connectionString` and `params` below, and that user should have permission to query `pg_database`. If you want to filter which databases are monitored, use the `databases` option below. (**default:** `postgres`) | | `connectionString` | no | `string` | See https://godoc.org/github.com/lib/pq#hdr-Connection_String_Parameters. | | `params` | no | `map of strings` | Parameters to the connection string that can be templated into the connection string with the syntax `{{.key}}`. | -| `databases` | no | `list of strings` | List of databases to send database-specific metrics about. If omitted, metrics about all databases will be sent. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters). (**default:** `[*]`) | +| `databases` | no | `list of strings` | List of databases to send database-specific metrics about. If omitted, metrics about all databases will be sent. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent). (**default:** `[*]`) | | `databasePollIntervalSeconds` | no | `integer` | How frequently to poll for new/deleted databases in the DB server. Defaults to the same as `intervalSeconds` if not set. (**default:** `0`) | | `logQueries` | no | `bool` | If true, queries will be logged at the info level. (**default:** `false`) | | `topQueryLimit` | no | `integer` | The number of top queries to consider when publishing query-related metrics (**default:** `10`) | @@ -113,7 +113,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. @@ -127,7 +127,7 @@ Metrics that are categorized as - `postgres_pct_connections` (*gauge*)
The number of connections to this database as a fraction of the maximum number of allowed connections. - ***`postgres_query_count`*** (*cumulative*)
Total number of queries executed on the `database`, broken down by `user`. Note that the accuracy of this metric depends on the PostgreSQL [pg_stat_statements.max config option](https://www.postgresql.org/docs/9.3/pgstatstatements.html#AEN160631) being large enough to hold all queries. - - ***`postgres_query_time`*** (*cumulative*)
Total time taken to execute queries on the `database`, broken down by `user`. + - ***`postgres_query_time`*** (*cumulative*)
Total time taken to execute queries on the `database`, broken down by `user`. Measured in ms unless otherwise indicated. - ***`postgres_rows_deleted`*** (*cumulative*)
Number of rows deleted from the `table`. - ***`postgres_rows_inserted`*** (*cumulative*)
Number of rows inserted into the `table`. - ***`postgres_rows_updated`*** (*cumulative*)
Number of rows updated in the `table`. diff --git a/signalfx-agent/agent_docs/monitors/process.md b/signalfx-agent/agent_docs/monitors/process.md index 0e7ab3ab..e1683378 100644 --- a/signalfx-agent/agent_docs/monitors/process.md +++ b/signalfx-agent/agent_docs/monitors/process.md @@ -30,15 +30,15 @@ Configuration](../monitor-config.html#common-configuration).** | Config option | Required | Type | Description | | --- | --- | --- | --- | -| `processes` | no | `list of strings` | A list of process command names to match and send metrics about. This is the name contained in /proc//comm and is limited to just 15 characters on Linux. Only one of `processes` or `executables` must match a process for it to have metrics generated about it. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters) that supports regexp and glob values. | -| `executables` | no | `list of strings` | A list of process executable paths to match against and send metrics about. This is the binary executable that is symlinked in the /proc//exe file on Linux. This must match the full path. Only one of `processes` or `executables` must match a process for it to have metrics generated about it. This is an [overridable set](https://docs.signalfx.com/en/latest/integrations/agent/filtering.html#overridable-filters) that supports regexp and glob values. | +| `processes` | no | `list of strings` | A list of process command names to match and send metrics about. This is the name contained in /proc//comm and is limited to just 15 characters on Linux. Only one of `processes` or `executables` must match a process for it to have metrics generated about it. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent) that supports regexp and glob values. | +| `executables` | no | `list of strings` | A list of process executable paths to match against and send metrics about. This is the binary executable that is symlinked in the /proc//exe file on Linux. This must match the full path. Only one of `processes` or `executables` must match a process for it to have metrics generated about it. This is an [overridable set](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#filtering-data-using-the-smart-agent) that supports regexp and glob values. | ## Metrics These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/prometheus-go.md b/signalfx-agent/agent_docs/monitors/prometheus-go.md index 2efee186..4650090a 100644 --- a/signalfx-agent/agent_docs/monitors/prometheus-go.md +++ b/signalfx-agent/agent_docs/monitors/prometheus-go.md @@ -59,7 +59,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/prometheus-nginx-ingress.md b/signalfx-agent/agent_docs/monitors/prometheus-nginx-ingress.md index 9a6efb86..b4c9d39a 100644 --- a/signalfx-agent/agent_docs/monitors/prometheus-nginx-ingress.md +++ b/signalfx-agent/agent_docs/monitors/prometheus-nginx-ingress.md @@ -78,7 +78,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/prometheus-nginx-vts.md b/signalfx-agent/agent_docs/monitors/prometheus-nginx-vts.md index 10269ab0..6a8ab12a 100644 --- a/signalfx-agent/agent_docs/monitors/prometheus-nginx-vts.md +++ b/signalfx-agent/agent_docs/monitors/prometheus-nginx-vts.md @@ -57,7 +57,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/prometheus-node.md b/signalfx-agent/agent_docs/monitors/prometheus-node.md index 3944c10a..72b391bf 100644 --- a/signalfx-agent/agent_docs/monitors/prometheus-node.md +++ b/signalfx-agent/agent_docs/monitors/prometheus-node.md @@ -57,7 +57,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/prometheus-postgres.md b/signalfx-agent/agent_docs/monitors/prometheus-postgres.md index c5ea88ef..7a31bfcc 100644 --- a/signalfx-agent/agent_docs/monitors/prometheus-postgres.md +++ b/signalfx-agent/agent_docs/monitors/prometheus-postgres.md @@ -57,7 +57,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/prometheus-prometheus.md b/signalfx-agent/agent_docs/monitors/prometheus-prometheus.md index 82cb299a..56c45fde 100644 --- a/signalfx-agent/agent_docs/monitors/prometheus-prometheus.md +++ b/signalfx-agent/agent_docs/monitors/prometheus-prometheus.md @@ -57,7 +57,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/prometheus-redis.md b/signalfx-agent/agent_docs/monitors/prometheus-redis.md index 32ca8319..770bfafe 100644 --- a/signalfx-agent/agent_docs/monitors/prometheus-redis.md +++ b/signalfx-agent/agent_docs/monitors/prometheus-redis.md @@ -57,7 +57,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/prometheus-velero.md b/signalfx-agent/agent_docs/monitors/prometheus-velero.md index abe348d1..f4ba8400 100644 --- a/signalfx-agent/agent_docs/monitors/prometheus-velero.md +++ b/signalfx-agent/agent_docs/monitors/prometheus-velero.md @@ -74,7 +74,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/supervisor.md b/signalfx-agent/agent_docs/monitors/supervisor.md index a646775f..517aa0b4 100644 --- a/signalfx-agent/agent_docs/monitors/supervisor.md +++ b/signalfx-agent/agent_docs/monitors/supervisor.md @@ -43,7 +43,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/telegraf-dns.md b/signalfx-agent/agent_docs/monitors/telegraf-dns.md index 4a058943..97e42967 100644 --- a/signalfx-agent/agent_docs/monitors/telegraf-dns.md +++ b/signalfx-agent/agent_docs/monitors/telegraf-dns.md @@ -45,7 +45,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/telegraf-ntpq.md b/signalfx-agent/agent_docs/monitors/telegraf-ntpq.md index f36cf36f..99cd6462 100644 --- a/signalfx-agent/agent_docs/monitors/telegraf-ntpq.md +++ b/signalfx-agent/agent_docs/monitors/telegraf-ntpq.md @@ -42,7 +42,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. This monitor will also emit by default any metrics that are not listed below. diff --git a/signalfx-agent/agent_docs/monitors/telegraf-procstat.md b/signalfx-agent/agent_docs/monitors/telegraf-procstat.md index 706c86ca..3546970b 100644 --- a/signalfx-agent/agent_docs/monitors/telegraf-procstat.md +++ b/signalfx-agent/agent_docs/monitors/telegraf-procstat.md @@ -66,7 +66,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/telegraf-sqlserver.md b/signalfx-agent/agent_docs/monitors/telegraf-sqlserver.md index dd37408e..b3868891 100644 --- a/signalfx-agent/agent_docs/monitors/telegraf-sqlserver.md +++ b/signalfx-agent/agent_docs/monitors/telegraf-sqlserver.md @@ -91,7 +91,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/telegraf-varnish.md b/signalfx-agent/agent_docs/monitors/telegraf-varnish.md index a4a5ee1c..dbbaec57 100644 --- a/signalfx-agent/agent_docs/monitors/telegraf-varnish.md +++ b/signalfx-agent/agent_docs/monitors/telegraf-varnish.md @@ -55,7 +55,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/telegraf-win_services.md b/signalfx-agent/agent_docs/monitors/telegraf-win_services.md index 2fdcc914..2c146d81 100644 --- a/signalfx-agent/agent_docs/monitors/telegraf-win_services.md +++ b/signalfx-agent/agent_docs/monitors/telegraf-win_services.md @@ -55,7 +55,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. This monitor emits all metrics by default; however, **none are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) -- they are all custom**. diff --git a/signalfx-agent/agent_docs/monitors/traefik.md b/signalfx-agent/agent_docs/monitors/traefik.md index c40b258c..461e21e9 100644 --- a/signalfx-agent/agent_docs/monitors/traefik.md +++ b/signalfx-agent/agent_docs/monitors/traefik.md @@ -105,7 +105,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/vmem.md b/signalfx-agent/agent_docs/monitors/vmem.md index bd277491..c6226176 100644 --- a/signalfx-agent/agent_docs/monitors/vmem.md +++ b/signalfx-agent/agent_docs/monitors/vmem.md @@ -51,7 +51,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/vsphere.md b/signalfx-agent/agent_docs/monitors/vsphere.md index 8df451c9..5b133e02 100644 --- a/signalfx-agent/agent_docs/monitors/vsphere.md +++ b/signalfx-agent/agent_docs/monitors/vsphere.md @@ -79,7 +79,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/windows-iis.md b/signalfx-agent/agent_docs/monitors/windows-iis.md index 74545970..d9fcafe5 100644 --- a/signalfx-agent/agent_docs/monitors/windows-iis.md +++ b/signalfx-agent/agent_docs/monitors/windows-iis.md @@ -58,7 +58,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/monitors/windows-legacy.md b/signalfx-agent/agent_docs/monitors/windows-legacy.md index 889226be..0d1fc4c8 100644 --- a/signalfx-agent/agent_docs/monitors/windows-legacy.md +++ b/signalfx-agent/agent_docs/monitors/windows-legacy.md @@ -56,7 +56,7 @@ Configuration](../monitor-config.html#common-configuration).** These are the metrics available for this monitor. Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. diff --git a/signalfx-agent/agent_docs/quick-install.md b/signalfx-agent/agent_docs/quick-install.md index 8afe8ed0..9e9c3b73 100644 --- a/signalfx-agent/agent_docs/quick-install.md +++ b/signalfx-agent/agent_docs/quick-install.md @@ -8,7 +8,7 @@ SignalFx Smart Agent is deprecated. For details, see the [Deprecation Notice](./ SignalFx Smart Agent Integration installs the Smart Agent application on a single host machine from which you want to collect monitoring data. Smart Agent collects infrastructure monitoring, µAPM, and Kubernetes data. For other installation options, including bulk deployments to production, -see [Install and Configure the Smart Agent](https://docs.signalfx.com/en/latest/integrations/agent/agent-install-methods.html). +see [Install and Configure the Smart Agent](https://docs.splunk.com/observability/gdi/smart-agent/smart-agent-resources.html#install-the-smart-agent). ## Installation diff --git a/signalfx-agent/agent_docs/smartagent-deprecation-notice.md b/signalfx-agent/agent_docs/smartagent-deprecation-notice.md index 4cfa1dc7..ae25c17e 100644 --- a/signalfx-agent/agent_docs/smartagent-deprecation-notice.md +++ b/signalfx-agent/agent_docs/smartagent-deprecation-notice.md @@ -1,9 +1,13 @@ > # :warning: Deprecation Notice for SignalFx Smart Agent -> **The SignalFx Smart Agent is deprecated and will reach End of Support on December 17th, 2022. After that date, this repository will be archived and no longer receive updates. Until then, only critical security fixes and bug fixes will be provided.** +> **The SignalFx Smart Agent is deprecated and will reach End of Support on June 30th, 2023. After that date, this repository will be archived and no longer receive updates. Until then, only critical security fixes and bug fixes will be provided.** > ->Going forward, you should use the [Splunk Distribution of OpenTelemetry Connector](https://docs.splunk.com/Observability/gdi/opentelemetry/resources.html), which fully supports the OpenTelemetry standard and includes customizations for: +>Going forward, you should use the [Splunk Distribution of OpenTelemetry Collector](https://docs.splunk.com/observability/gdi/opentelemetry/resources.html), which fully supports the OpenTelemetry standard and includes customizations for: >* Splunk products >* Fluentd for log capture >* Tools to support migration from SignalFx products + +> Please see [this](https://docs.splunk.com/observability/gdi/opentelemetry/smart-agent-migration-to-otel-collector.html#nav-Migrating-from-SignalFx-Smart-Agent-to-Splunk-Distribution-of-OpenTelemetry-Collector) documentation for details to assist with moving to the Splunk Distribution of OpenTelemetry Collector. + +>Note that the date affects the standalone agent; the Smart Agent monitors will be available and supported with the [Smart Agent receiver](https://github.com/signalfx/splunk-otel-collector/blob/main/pkg/receiver/smartagent/README.md) in the Splunk Distribution of OpenTelemetry Collector. diff --git a/solr/SMART_AGENT_MONITOR.md b/solr/SMART_AGENT_MONITOR.md index afadb863..13dee562 100644 --- a/solr/SMART_AGENT_MONITOR.md +++ b/solr/SMART_AGENT_MONITOR.md @@ -71,7 +71,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/spark/SMART_AGENT_MONITOR.md b/spark/SMART_AGENT_MONITOR.md index 33048065..425df498 100644 --- a/spark/SMART_AGENT_MONITOR.md +++ b/spark/SMART_AGENT_MONITOR.md @@ -82,7 +82,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/traefik/SMART_AGENT_MONITOR.md b/traefik/SMART_AGENT_MONITOR.md index e68968a2..73589f9a 100644 --- a/traefik/SMART_AGENT_MONITOR.md +++ b/traefik/SMART_AGENT_MONITOR.md @@ -110,7 +110,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. diff --git a/zookeeper/SMART_AGENT_MONITOR.md b/zookeeper/SMART_AGENT_MONITOR.md index f4f63ab1..71d50a17 100644 --- a/zookeeper/SMART_AGENT_MONITOR.md +++ b/zookeeper/SMART_AGENT_MONITOR.md @@ -50,7 +50,7 @@ Configuration](https://github.com/signalfx/signalfx-agent/tree/main/docs/monitor ## Metrics Metrics that are categorized as -[container/host](https://docs.signalfx.com/en/latest/admin-guide/usage.html#about-custom-bundled-and-high-resolution-metrics) +[container/host](https://docs.splunk.com/observability/admin/subscription-usage/monitor-imm-billing-usage.html#about-custom-bundled-and-high-resolution-metrics) (*default*) are ***in bold and italics*** in the list below. These are the metrics available for this integration. From a99f582bb91b37b21f3ea981453754e2d4d7e2d7 Mon Sep 17 00:00:00 2001 From: Antoine Toulme Date: Thu, 5 Jan 2023 13:36:34 -0800 Subject: [PATCH 17/48] remove CircleCI, use github actions (#995) --- .circleci/config.yml | 24 ------------------------ .github/workflows/test.yml | 27 +++++++++++++++++++++++++++ check-links | 10 ---------- 3 files changed, 27 insertions(+), 34 deletions(-) delete mode 100644 .circleci/config.yml create mode 100644 .github/workflows/test.yml delete mode 100755 check-links diff --git a/.circleci/config.yml b/.circleci/config.yml deleted file mode 100644 index c098bd24..00000000 --- a/.circleci/config.yml +++ /dev/null @@ -1,24 +0,0 @@ ---- -version: 2.1 -jobs: - checklinks: - docker: - - image: golang:1.13 - steps: - - checkout - # Do hacky things to install a tool with go modules. - - run: | - cd ~ && go mod init test && go get -u github.com/raviqqe/liche@4db4b8909d21d62ce97d31a07891183e1440cc7b - - run: ./check-links - build-tile: - docker: - - image: python:3.7 - steps: - - checkout - - run: pip install -r requirements.txt - - run: ./build -workflows: - build_test: - jobs: - - checklinks - - build-tile diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml new file mode 100644 index 00000000..68e6d3e2 --- /dev/null +++ b/.github/workflows/test.yml @@ -0,0 +1,27 @@ +name: build-and-test + +on: + push: + branches: + - main + pull_request: + +jobs: + checklinks: + runs-on: ubuntu-latest + steps: + - name: Check + uses: gaurav-nelson/github-action-markdown-link-check@v1 + build-tile: + runs-on: ubuntu-latest + steps: + - name: Check out the codebase. + uses: actions/checkout@v3 + - uses: actions/setup-python@v4 + with: + python-version: '3.10' + cache: 'pip' # caching pip dependencies + - name: Install requirements + run: pip install -r requirements.txt + + - run: ./build \ No newline at end of file diff --git a/check-links b/check-links deleted file mode 100755 index bf374396..00000000 --- a/check-links +++ /dev/null @@ -1,10 +0,0 @@ -#!/bin/sh - -# Ensures that all links in the repo are valid. - -liche --recursive \ - --concurrency 50 \ - --timeout 30 \ - --document-root / \ - --exclude '(localhost|leader\.mesos|YOUR_SIGNALFX_ORG_ID|YOUR_SIGNALFX_REALM|ingest.*signalfx.com|127\.0\.0\.1|kb\.vmware\.com|support\.signalfx\.com|signalfx-agent/agent_docs|169\.254\.170\.2|log-stream)' \ - . From f690c73a9853059c2f31b4f20262e3f55d22a45e Mon Sep 17 00:00:00 2001 From: Antoine Toulme Date: Thu, 5 Jan 2023 13:48:49 -0800 Subject: [PATCH 18/48] Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test --- .github/workflows/{test.yml => build-and-test.yml} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename .github/workflows/{test.yml => build-and-test.yml} (95%) diff --git a/.github/workflows/test.yml b/.github/workflows/build-and-test.yml similarity index 95% rename from .github/workflows/test.yml rename to .github/workflows/build-and-test.yml index 68e6d3e2..15026c46 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/build-and-test.yml @@ -10,7 +10,7 @@ jobs: checklinks: runs-on: ubuntu-latest steps: - - name: Check + - name: Check links uses: gaurav-nelson/github-action-markdown-link-check@v1 build-tile: runs-on: ubuntu-latest From 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f Mon Sep 17 00:00:00 2001 From: bhillmer <86490494+bhillmer@users.noreply.github.com> Date: Mon, 23 Jan 2023 09:54:39 -0700 Subject: [PATCH 19/48] add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates --- signalfx-org-metrics/metrics.yaml | 59 ++++++++++++++++++++++++++++++- 1 file changed, 58 insertions(+), 1 deletion(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index f881e3f1..c324390f 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -106,6 +106,31 @@ sf.org.apm.numHosts: metric_type: gauge title: sf.org.apm.numHosts +sf.org.apm.grossSpanBytesReceived: + brief: The number of bytes Splunk APM receives from spans after decompression + but before filtering and throttling. + description: | + The number of bytes Splunk APM receives from spans after + decompression but before filtering and throttling. + + * Dimension(s): `orgId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.grossSpanBytesReceived + +sf.org.apm.grossSpanBytesReceivedByToken: + brief: The number of bytes Splunk APM receives for a specific access token + from ingested span data after decompression but before filtering and + throttling. + description: | + The number of bytes Splunk APM receives for a specific access token + from ingested span data after decompression but before filtering and throttling. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.grossSpanBytesReceivedByToken + sf.org.apm.numSpanBytesReceived: brief: The number of bytes Splunk APM accepts from ingested span data after decompression after filtering and throttling. @@ -201,6 +226,28 @@ sf.org.apm.numSpansDroppedThrottleByToken: metric_type: counter title: sf.org.apm.numSpansDroppedThrottleByToken +sf.org.apm.grossSpansReceived: + brief: The number of spans Splunk APM received before filtering and throttling. + description: | + The number of spans Splunk APM received before filtering or throttling. + + * Dimension(s): `orgId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.grossSpansReceived + +sf.org.apm.grossSpansReceivedByToken: + brief: The number of spans Splunk APM receives for a specific access token + before filtering and throttling. + description: | + The number of spans Splunk APM receives for a specific access token + before filtering or throttling. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.grossSpansReceivedByToken + sf.org.apm.numSpansReceived: brief: The number of spans Splunk APM accepts after filtering and throttling. description: | @@ -1180,13 +1227,23 @@ sf.org.numDatapointsDroppedExceededQuotaByToken: sf.org.numDatapointsDroppedInvalid: brief: Number of data points dropped because they didn't follow documented guidelines for data points. description: | - 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 that are 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. * Dimension(s): `orgId` * Data resolution: 10 seconds metric_type: counter title: sf.org.numDatapointsDroppedInvalid +sf.org.numDatapointsDroppedInvalidByToken: + brief: Number of data points dropped because they didn't follow documented guidelines for data points. + description: | + Number of data points for a specific access token that are 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. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numDatapointsDroppedInvalidByToken + sf.org.numDatapointsDroppedInTimeout: brief: Number of data points Observability Cloud didn't attempt to create because your account was throttled or limited in the previous few seconds. description: | From 546a160e9b447b868b1c8951100de54393af45ac Mon Sep 17 00:00:00 2001 From: bhillmer <86490494+bhillmer@users.noreply.github.com> Date: Mon, 23 Jan 2023 10:02:18 -0700 Subject: [PATCH 20/48] Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. --- signalfx-org-metrics/metrics.yaml | 59 +------------------------------ 1 file changed, 1 insertion(+), 58 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index c324390f..f881e3f1 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -106,31 +106,6 @@ sf.org.apm.numHosts: metric_type: gauge title: sf.org.apm.numHosts -sf.org.apm.grossSpanBytesReceived: - brief: The number of bytes Splunk APM receives from spans after decompression - but before filtering and throttling. - description: | - The number of bytes Splunk APM receives from spans after - decompression but before filtering and throttling. - - * Dimension(s): `orgId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.apm.grossSpanBytesReceived - -sf.org.apm.grossSpanBytesReceivedByToken: - brief: The number of bytes Splunk APM receives for a specific access token - from ingested span data after decompression but before filtering and - throttling. - description: | - The number of bytes Splunk APM receives for a specific access token - from ingested span data after decompression but before filtering and throttling. - - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.apm.grossSpanBytesReceivedByToken - sf.org.apm.numSpanBytesReceived: brief: The number of bytes Splunk APM accepts from ingested span data after decompression after filtering and throttling. @@ -226,28 +201,6 @@ sf.org.apm.numSpansDroppedThrottleByToken: metric_type: counter title: sf.org.apm.numSpansDroppedThrottleByToken -sf.org.apm.grossSpansReceived: - brief: The number of spans Splunk APM received before filtering and throttling. - description: | - The number of spans Splunk APM received before filtering or throttling. - - * Dimension(s): `orgId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.apm.grossSpansReceived - -sf.org.apm.grossSpansReceivedByToken: - brief: The number of spans Splunk APM receives for a specific access token - before filtering and throttling. - description: | - The number of spans Splunk APM receives for a specific access token - before filtering or throttling. - - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.apm.grossSpansReceivedByToken - sf.org.apm.numSpansReceived: brief: The number of spans Splunk APM accepts after filtering and throttling. description: | @@ -1227,23 +1180,13 @@ sf.org.numDatapointsDroppedExceededQuotaByToken: sf.org.numDatapointsDroppedInvalid: brief: Number of data points dropped because they didn't follow documented guidelines for data points. description: | - Number of data points that are 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 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. * Dimension(s): `orgId` * Data resolution: 10 seconds metric_type: counter title: sf.org.numDatapointsDroppedInvalid -sf.org.numDatapointsDroppedInvalidByToken: - brief: Number of data points dropped because they didn't follow documented guidelines for data points. - description: | - Number of data points for a specific access token that are 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. - - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 seconds - metric_type: counter - title: sf.org.numDatapointsDroppedInvalidByToken - sf.org.numDatapointsDroppedInTimeout: brief: Number of data points Observability Cloud didn't attempt to create because your account was throttled or limited in the previous few seconds. description: | From 1eec1d93bab841333f3b800b9d6aaca148600062 Mon Sep 17 00:00:00 2001 From: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Date: Wed, 25 Jan 2023 10:25:34 -0800 Subject: [PATCH 21/48] DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions --- signalfx-org-metrics/metrics.yaml | 157 +++++++++++++++++++++++++++++- 1 file changed, 154 insertions(+), 3 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index f881e3f1..ee108915 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -75,7 +75,7 @@ sf.org.apm.numAddSpansCalls: * Dimension(s): `orgId` * Data resolution: 1 second metric_type: counter - title: sf.org.apm.numAddSpansCallsByToken + title: sf.org.apm.numAddSpansCalls sf.org.apm.numAddSpansCallsByToken: brief: The number of calls to the `/v2/trace` endpoint for a specific access token. @@ -1271,7 +1271,7 @@ sf.org.numDatapointsReceivedByToken: sf.org.numEventTimeSeriesCreated: brief: Number of event time series created - description: | + description: | Total number of event time series (ETS) created. For MTS values, see `sf.org.numMetricTimeSeriesCreated`. * Dimension(s): `orgId` @@ -1790,7 +1790,8 @@ sf.org.subscription.function: description: | Number of serverless functions included in the subscription. - * Data resolution: 2 minutes + * Data resolution: 10 seconds + metric_type: gauge title: sf.org.subscription.function @@ -1799,3 +1800,153 @@ sf.org.ui.num.pagevisits: description: Reserved for Infrastructure Monitoring internal use only. metric_type: null title: sf.org.ui.num.pagevisits + +sf.org.rum.numSpansReceived: + brief: The number of spans Splunk RUM accepts after filtering and throttling. + description: | + Number of spans received. + + * Dimension: orgId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numSpansReceived + +sf.org.rum.numSpansReceivedByToken: + brief: The number of spans Splunk RUM received for a specific access token + after filtering and throttling. + description: | + The number of spans Splunk RUM received for a specific access token + after filtering and throttling. + + * Dimension: orgId, tokenId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numSpansReceivedByToken + + +sf.org.rum.numAddSpansCalls: + brief: The number of calls to the `/v1/rum?auth={AUTH_TOKEN}` endpoint. + description: | + The number of calls to the `/v1/rum?auth={AUTH_TOKEN}` endpoint. + + * Dimension: orgId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numAddSpansCalls + +sf.org.rum.numAddSpansCallsByToken: + brief: The number of calls to the `/v1/rum?auth={AUTH_TOKEN}` endpoint for a specific access token. + description: | + The number of calls to the `/v1/rum?auth={AUTH_TOKEN}` endpoint for a specific access token. + + * Dimension: orgId, tokenId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numAddSpansCalls + +sf.org.rum.numSpansDroppedInvalid: + brief: Number of spans dropped because they were invalid. + description: | + Number of spans dropped because they were invalid. Some of the reasons that spans are invalid are: spans are too large, missing required tags and invalid Trace IDs. Look through the reason column in the data table to see details for specific spans. + + * Dimension: orgId, reason, + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numSpansDroppedInvalid + +sf.org.rum.numSpansDroppedInvalidByToken: + brief: The number of invalid spans Splunk RUM receives for a specific access + token. + description: | + The number of invalid spans Splunk RUM receives for a specific + access token. Some of the reasons that spans are invalid are: spans are too large, missing required tags and invalid Trace IDs. Look through the reason column in the data table to see details for specific spans. + + * Dimensions: orgId, tokenId, reason + * Data resolution: 10 seconds + + metric_type: Counter + title: sf.org.rum.numSpansDroppedInvalidByToken + +sf.org.rum.numSpansDroppedThrottle: + brief: The number of spans Splunk RUM dropped after you exceeded the allowed ingest volume. + description: | + The number of spans Splunk RUM dropped after you exceeded the allowed ingest volume. + + * Dimension: orgId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numSpansDroppedThrottle + +sf.org.rum.numSpansDroppedThrottleByToken: + brief: The number of spans Splunk RUM dropped after you exceeded the allowed ingest volume for a specific access token. + description: | + The number of spans Splunk RUM dropped after you exceeded the allowed ingest volume for a specific access token. + + * Dimension: orgId, tokenId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numSpansDroppedThrottleByToken + + +sf.org.rum.numSpanBytesReceived: + brief: The bytes of all the spans accepted and counted by the metric numSpansReceived. + description: | + The bytes of all the spans accepted and counted by the metric numSpansReceived. + + * Dimensions: orgId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numSpanBytesReceived + +sf.org.rum.numSpanBytesReceivedByToken: + brief: The bytes of all the spans accepted and counted by the metric numSpansReceived by token. + description: | + The bytes of all the spans accepted and counted by the metric numSpansReceived by token. + + * Dimensions: orgId, tokenId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numSpanBytesReceivedByToken + + +sf.org.rum.grossSpanBytesReceivedByToken: + brief: The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. + description: | + The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. + + * Dimensions: orgId, tokenId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.grossSpanBytesReceivedByToken + +sf.org.rum.numContentBytesReceived: + brief: The volume of bytes Splunk RUM receives after filtering and throttling. + description: | + The volume of bytes Splunk RUM receives after filtering and throttling. + + * Dimensions: orgId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.numContentBytesReceived + +sf.org.rum.grossContentBytesReceivedByToken: + brief: The possibly compressed wire size of the payloads before the payloads are decompressed and decoded by token. + description: | + The possibly compressed wire size of the payloads before the payloads are decompressed and decoded by token. + + * Dimensions: orgId, tokenId + * Data resolution: 10 seconds + metric_type: Counter + title: sf.org.rum.grossContentBytesReceivedByToken + + +sf.org.rum.grossContentBytesReceived: + brief: The possibly compressed wire size of the payloads before the payloads are decompressed and decoded. + description: | + The possibly compressed wire size of the payloads before the payloads are decompressed and decoded. + + * Dimensions: orgId + * Data resolution: 10 seconds + + metric_type: Counter + title: sf.org.rum.grossContentBytesReceived \ No newline at end of file From 9102b6dc421eb09ebc373d2f64c33599f72e802d Mon Sep 17 00:00:00 2001 From: bhillmer <86490494+bhillmer@users.noreply.github.com> Date: Fri, 27 Jan 2023 13:34:28 -0700 Subject: [PATCH 22/48] add sf.org.numDatapointsDroppedInvalidByToken (#999) --- signalfx-org-metrics/metrics.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index ee108915..3218791c 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1187,6 +1187,15 @@ sf.org.numDatapointsDroppedInvalid: metric_type: counter title: sf.org.numDatapointsDroppedInvalid + sf.org.numDatapointsDroppedInvalidByToken: + brief: Number of data points dropped because they didn't follow documented guidelines for data points. + description: | + Number of data points for a specific access token that are 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. + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numDatapointsDroppedInvalidByToken + sf.org.numDatapointsDroppedInTimeout: brief: Number of data points Observability Cloud didn't attempt to create because your account was throttled or limited in the previous few seconds. description: | From 7d53956f3a9d969a597667644523d06f15453f19 Mon Sep 17 00:00:00 2001 From: bhillmer <86490494+bhillmer@users.noreply.github.com> Date: Mon, 30 Jan 2023 10:28:40 -0700 Subject: [PATCH 23/48] Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. --- signalfx-org-metrics/metrics.yaml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 3218791c..ee108915 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1187,15 +1187,6 @@ sf.org.numDatapointsDroppedInvalid: metric_type: counter title: sf.org.numDatapointsDroppedInvalid - sf.org.numDatapointsDroppedInvalidByToken: - brief: Number of data points dropped because they didn't follow documented guidelines for data points. - description: | - Number of data points for a specific access token that are 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. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 seconds - metric_type: counter - title: sf.org.numDatapointsDroppedInvalidByToken - sf.org.numDatapointsDroppedInTimeout: brief: Number of data points Observability Cloud didn't attempt to create because your account was throttled or limited in the previous few seconds. description: | From 6ea23f6b2ff3c9a0d1c5d238b84f9d5e7f546f97 Mon Sep 17 00:00:00 2001 From: bhillmer <86490494+bhillmer@users.noreply.github.com> Date: Mon, 30 Jan 2023 11:45:03 -0700 Subject: [PATCH 24/48] DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation --- signalfx-org-metrics/metrics.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index ee108915..078ae3a0 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1187,6 +1187,15 @@ sf.org.numDatapointsDroppedInvalid: metric_type: counter title: sf.org.numDatapointsDroppedInvalid +sf.org.numDatapointsDroppedInvalidByToken: + brief: Number of data points dropped because they didn't follow documented guidelines for data points. + description: | + Number of data points for a specific access token that are 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. + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numDatapointsDroppedInvalidByToken + sf.org.numDatapointsDroppedInTimeout: brief: Number of data points Observability Cloud didn't attempt to create because your account was throttled or limited in the previous few seconds. description: | From eaa4fc9cbde619866ac84886b695a33201677e58 Mon Sep 17 00:00:00 2001 From: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Date: Mon, 30 Jan 2023 15:07:27 -0800 Subject: [PATCH 25/48] add metric sf.org.log.numMessagesReceivedByToken (#1001) --- signalfx-org-metrics/metrics.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 078ae3a0..cd8eb167 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -624,6 +624,16 @@ sf.org.log.numMessagesReceivedByToken: metric_type: counter title: sf.org.log.numMessagesReceivedByToken +sf.org.log.numMessageBytesIndexed: + brief: Bytes of data stored in Log Observer index after applying pipeline management rules. + description: | + Bytes of data stored in the Log Observer index after applying pipeline management rules. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.log.numMessageBytesIndexed + sf.org.num.alertmuting: brief: Total number of alert muting rules description: | From a2561f89f204dbe12e5f06f5648bc2f463039341 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Mon, 20 Feb 2023 08:49:30 +0100 Subject: [PATCH 26/48] Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. --- signalfx-org-metrics/metrics.yaml | 34 ------------------------------- 1 file changed, 34 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index cd8eb167..4e7cb14a 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1254,40 +1254,6 @@ sf.org.numDatapointsDroppedThrottleByToken: metric_type: counter title: sf.org.numDatapointsDroppedThrottleByToken -sf.org.numDatapointsReceived: - brief: Number of data points Infrastructure Monitoring received - description: | - One value per metric type, each representing the number of data points that - Infrastructure Monitoring received and processed. - 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). - 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. - - * Dimension(s): `category, orgId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.numDatapointsReceived - -sf.org.numDatapointsReceivedByToken: - brief: Per token number of data points Infrastructure Monitoring received - description: | - 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; 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). - The sum of all the values might be less than the value of `sf.org.numDatapointsReceived`. - To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - - * Dimension(s): `category`, `orgId`, `tokenId` - * Data resolution: 1 second - metric_type: counter - title: sf.org.numDatapointsReceivedByToken - sf.org.numEventTimeSeriesCreated: brief: Number of event time series created description: | From 422e76c4192121211a2f81fc88c8b135cf189000 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Wed, 22 Feb 2023 11:40:34 +0100 Subject: [PATCH 27/48] Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension --- signalfx-org-metrics/metrics.yaml | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 4e7cb14a..037b1b4e 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1254,9 +1254,33 @@ sf.org.numDatapointsDroppedThrottleByToken: metric_type: counter title: sf.org.numDatapointsDroppedThrottleByToken +sf.org.numDatapointsReceived: + brief: Number of data points Infrastructure Monitoring received + description: | + One value per metric type, each representing the number of data points that + Infrastructure Monitoring received and processed. + You can have up to three MTS for this metric. To + learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type). + 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. + +sf.org.numDatapointsReceivedByToken: + brief: Per token number of data points Infrastructure Monitoring received + description: | + 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. To learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type). + The sum of all the values might be less than the value of `sf.org.numDatapointsReceived`. + To learn more, see [Metrics for values by token](#metrics-for-values-by-token). + * Data resolution: 1 second + metric_type: counter + title: sf.org.numDatapointsReceivedByToken + sf.org.numEventTimeSeriesCreated: brief: Number of event time series created - description: | + description: | Total number of event time series (ETS) created. For MTS values, see `sf.org.numMetricTimeSeriesCreated`. * Dimension(s): `orgId` From 87774a7ae8cf83c1c13cd42c4e371badac253464 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Mon, 20 Mar 2023 11:09:11 +0100 Subject: [PATCH 28/48] [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions --- signalfx-org-metrics/metrics.yaml | 40 +++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 037b1b4e..463ba701 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -378,6 +378,46 @@ sf.org.datapointsTotalCountByToken: * Data resolution: 10 seconds metric_type: counter title: sf.org.datapointsTotalCountByToken + +sf.org.datainventory.datapointsAdded: + brief: Number of data points retrieved from the AWS integration + description: | + Number of data points retrieved from the AWS integration + + * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` + * Data resolution: 10 seconds + metric_type: count + title: sf.org.datainventory.datapointsAdded + +sf.org.datainventory.latestTimestamp: + brief: Timestamp of the last data point retrieved from an integration + description: | + Timestamp of the last data point retrieved from an integration + + * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.datainventory.latestTimestamp + +sf.org.datainventory.mtses: + brief: Number of MTS retrieved from an AWS integration + description: | + Number of Metric Time Series retrieved from an AWS integration. It’s only generated when AWS metrics are polled, and is not available with Metric Streams + + * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.datainventory.mtses + +sf.org.datainventory.resources: + brief: Number of AWS resources polled by an AWS integration + description: | + Number of AWS resources polled by an AWS integration. It's only generated when AWS metrics are polled, and is not available with Metric Streams + + * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.datainventory.resources sf.org.grossDatapointsReceived: brief: Infrastructure Monitoring internal metric From 997123e838e3d5be261d21c06b824fa9a5c45383 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Tue, 21 Mar 2023 11:32:50 +0100 Subject: [PATCH 29/48] Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> --- signalfx-org-metrics/metrics.yaml | 57 ++++++++++++++++++++++--------- 1 file changed, 40 insertions(+), 17 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 463ba701..2055c2db 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -865,9 +865,11 @@ sf.org.num.eventtype: metric_type: gauge title: sf.org.num.eventtype -sf.org.num.gcpStackdriverClientCallCount: +sf.org.num.gcpStackdriverClientCallCount (DEPRECATED): brief: Number of calls to each Stackdriver client method description: | + THIS METRIC IS DEPRECATED AND WILL BE REMOVED. + PLEASE USE `sf.org.num.gcpServiceClientCallCount` INSTEAD Number of calls to each Stackdriver client method. * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) @@ -875,9 +877,11 @@ sf.org.num.gcpStackdriverClientCallCount: metric_type: counter title: sf.org.num.gcpStackdriverClientCallCount -sf.org.num.gcpStackdriverClientCallCountErrors: +sf.org.num.gcpStackdriverClientCallCountErrors (DEPRECATED): brief: Number of calls to each Stackdriver client method that threw errors description: | + THIS METRIC IS DEPRECATED AND WILL BE REMOVED. + PLEASE USE `sf.org.num.gcpServiceClientCallCountErrors` INSTEAD Number of calls to each Stackdriver client method that threw errors. * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) @@ -885,9 +889,11 @@ sf.org.num.gcpStackdriverClientCallCountErrors: metric_type: counter title: sf.org.num.gcpStackdriverClientCallCountErrors -sf.org.num.gcpStackdriverClientCallCountThrottles: +sf.org.num.gcpStackdriverClientCallCountThrottles (DEPRECATED): brief: Number of calls to each Stackdriver client method that were throttled description: | + THIS METRIC IS DEPRECATED AND WILL BE REMOVED. + PLEASE USE `sf.org.num.gcpServiceClientCallCountThrottles` INSTEAD Number of calls to each Stackdriver client method that were throttled. * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) @@ -895,6 +901,36 @@ sf.org.num.gcpStackdriverClientCallCountThrottles: metric_type: counter title: sf.org.num.gcpStackdriverClientCallCountThrottles +sf.org.num.gcpServiceClientCallCount: + brief: Number of calls to each GCP API client method + description: | + Number of calls to each GCP API client method. + + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second + metric_type: counter + title: sf.org.num.gcpSeviceClientCallCount + +sf.org.num.gcpServiceClientCallCountErrors: + brief: Number of calls to each GCP API client method that threw errors + description: | + Number of calls to each GCP API client method that threw errors. + + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second + metric_type: counter + title: sf.org.num.gcpServiceClientCallCountErrors + +sf.org.num.gcpServiceClientCallCountThrottles: + brief: Number of calls to each GCP API client method that were throttled + description: | + Number of calls to each GCP API client method that were throttled. + + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second + metric_type: counter + title: sf.org.num.gcpServiceClientCallCountThrottles + sf.org.num.metric: brief: Number of unique metrics across all MTS description: | @@ -1390,19 +1426,6 @@ sf.org.numEventsIngestedByToken: metric_type: counter title: sf.org.numEventsIngestedByToken -sf.org.numEventsReceived: - brief: Infrastructure Monitoring internal metric - description: | - Reserved for Infrastructure Monitoring internal use only. - metric_type: null - title: sf.org.numEventsReceived - -sf.org.numEventsReceivedByToken: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. - metric_type: null - title: sf.org.numEventsReceivedByToken - sf.org.numHighResolutionMetrics: brief: Number of high resolution metrics monitored description: | @@ -1998,4 +2021,4 @@ sf.org.rum.grossContentBytesReceived: * Data resolution: 10 seconds metric_type: Counter - title: sf.org.rum.grossContentBytesReceived \ No newline at end of file + title: sf.org.rum.grossContentBytesReceived From 6dbea7752ddbd6ae3afc97006036c036f3907d08 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Wed, 22 Mar 2023 10:47:52 +0100 Subject: [PATCH 30/48] Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> --- signalfx-org-metrics/metrics.yaml | 33 +++++++++++-------------------- 1 file changed, 11 insertions(+), 22 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 2055c2db..e28d6750 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1401,30 +1401,19 @@ sf.org.numEventsDroppedThrottleByToken: * Data resolution: 1 second metric_type: counter title: sf.org.numEventsDroppedThrottleByToken - -sf.org.numEventsIngested: - brief: Number of custom events received via the /event POST API - description: | - Number of custom events received by Infrastructure Monitoring through the /event POST - API. - - * Dimension(s): `orgId, category` - * Data resolution: 1 second - metric_type: counter - title: sf.org.numEventsIngested - -sf.org.numEventsIngestedByToken: - brief: | - For each token, this is the number of custom events sent by the *POST* `/event` operation. + +sf.org.numEventsReceived: + brief: Infrastructure Monitoring internal metric description: | - For each token, this is the number of custom events sent by the *POST* `/event` operation. - The sum of all the values might be less than the value of `sf.org.numEventsIngested`. To learn more, - see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type). + Reserved for Infrastructure Monitoring internal use only. + metric_type: null + title: sf.org.numEventsReceived - * Dimension(s): `orgId`, `tokenId`, `category` - * Data resolution: 1 second - metric_type: counter - title: sf.org.numEventsIngestedByToken +sf.org.numEventsReceivedByToken: + brief: Infrastructure Monitoring internal metric + description: Reserved for Infrastructure Monitoring internal use only. + metric_type: null + title: sf.org.numEventsReceivedByToken sf.org.numHighResolutionMetrics: brief: Number of high resolution metrics monitored From 6a03efd7b4f9e11b4d8291b2086a8b2bfb2cdeb3 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Thu, 23 Mar 2023 10:43:11 +0100 Subject: [PATCH 31/48] [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch --- signalfx-org-metrics/metrics.yaml | 79 +++++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index e28d6750..2258787b 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1029,6 +1029,15 @@ sf.org.num.property: metric_type: gauge title: sf.org.num.property +sf.org.num.role: + brief: Number of roles in your system + description: | + Number of roles in your system. + * Dimension(s): `orgId` + * Data resolution: 63 minutes + metric_type: gauge + title: sf.org.num.role + sf.org.num.service: brief: Infrastructure Monitoring internal metric description: Reserved for Infrastructure Monitoring internal use only. @@ -1137,6 +1146,36 @@ sf.org.numAddEventsCallsByToken: metric_type: counter title: sf.org.numAddEventsCallsByToken +sf.org.numApmApiCalls: + brief: Number of calls made to APM’s public APIs + description: | + Number of calls made to APM’s public APIs. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numApmApiCalls + +sf.org.numApmBundledMetrics: + brief: APM Bundled Metrics limit for your org + description: | + APM Bundled Metrics limit for your org. + + * Dimension(s): `orgId` + * Data resolution: 10 minutes + metric_type: gauge + title: sf.org.numApmBundledMetrics + +sf.org.numApmBundledMetricsByToken: + brief: APM Bundled Metrics limit for your org, for a token + description: | + APM Bundled Metrics limit for your org for a specific token. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 minutes + metric_type: gauge + title: sf.org.numApmBundledMetricsByToken + sf.org.numBackfillCalls: brief: Number of of times a backfill API call was used to send metrics to Infrastructure Monitoring description: | @@ -1169,6 +1208,46 @@ sf.org.numBackfillCallsByToken: metric_type: counter title: sf.org.numBackfillCallsByToken +sf.org.numBadDimensionMetricTimeSeriesCreateCalls: + brief: Number of bad calls to create MTS due to an error with dimensions + description: | + Number of calls to create MTS that have failed due to an error with dimensions. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numBadDimensionMetricTimeSeriesCreateCalls + +sf.org.numBadDimensionMetricTimeSeriesCreateCallsByToken: + brief: Number of bad calls to create MTS due to an error with dimensions, per token + description: | + Number of calls to create MTS that have failed due to an error with dimensions, per token. + + * Dimension(s): `orgId` + * Data resolution: 35 seconds + metric_type: counter + title: sf.org.numBadDimensionMetricTimeSeriesCreateCallsByToken + +sf.org.numBadMetricMetricTimeSeriesCreateCalls: + brief: Number of bad calls to create MTS due to an error with metrics + description: | + Number of calls to create MTS that have failed due to an error with metrics. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numBadMetricMetricTimeSeriesCreateCalls + +sf.org.numBadMetricMetricTimeSeriesCreateCallsByToken: + brief: Number of bad calls to create MTS due to an error with metrics, per token + description: | + Number of calls to create MTS that have failed due to an error with metrics, per token. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 35 seconds + metric_type: counter + title: sf.org.numBadMetricMetricTimeSeriesCreateCallsByToken + sf.org.numCustomMetrics: brief: Number of custom metrics monitored description: | From 0f8ef583c73f323971f1687c4a19daae61a898d3 Mon Sep 17 00:00:00 2001 From: akonarska <86464734+akonarska@users.noreply.github.com> Date: Tue, 11 Apr 2023 10:54:21 +0200 Subject: [PATCH 32/48] Add new Azure metrics and deprecate old ones (#1015) --- signalfx-org-metrics/metrics.yaml | 42 ++++++++++++++++++++++++++++--- 1 file changed, 39 insertions(+), 3 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 2258787b..2b63bbb4 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -730,9 +730,11 @@ sf.org.num.awsServiceCallThrottles: metric_type: gauge title: sf.org.num.awsServiceCallThrottles -sf.org.num.azureMonitorClientCallCount: +sf.org.num.azureMonitorClientCallCount (DEPRECATED): brief: Number of calls made to the Azure Monitor API description: | + THIS METRIC IS DEPRECATED AND WILL BE REMOVED. + PLEASE USE `sf.org.num.azureServiceClientCallCount` INSTEAD Total number of calls made to the Azure Monitor API. * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric @@ -741,9 +743,11 @@ sf.org.num.azureMonitorClientCallCount: metric_type: counter title: sf.org.num.azureMonitorClientCallCount -sf.org.num.azureMonitorClientCallCountErrors: +sf.org.num.azureMonitorClientCallCountErrors (DEPRECATED): brief: Number of calls to Azure Monitor API method that threw errors description: | + THIS METRIC IS DEPRECATED AND WILL BE REMOVED. + PLEASE USE `sf.org.num.azureServiceClientCallCountErrors` INSTEAD Number of calls to Azure Monitor API method that threw errors. * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric @@ -752,9 +756,11 @@ sf.org.num.azureMonitorClientCallCountErrors: metric_type: counter title: sf.org.num.azureMonitorClientCallCountErrors -sf.org.num.azureMonitorClientCallCountThrottles: +sf.org.num.azureMonitorClientCallCountThrottles (DEPRECATED): brief: Number of calls to Azure Monitor method that were throttled description: | + THIS METRIC IS DEPRECATED AND WILL BE REMOVED. + PLEASE USE `sf.org.num.azureServiceClientCallCountThrottles` INSTEAD Number of calls to Azure Monitor method that were throttled. * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric @@ -762,6 +768,36 @@ sf.org.num.azureMonitorClientCallCountThrottles: * Data resolution: 1 second metric_type: counter title: sf.org.num.azureMonitorClientCallCountThrottles + +sf.org.num.azureServiceClientCallCount: + brief: Number of calls made to the Azure API + description: | + Total number of calls made to the Azure API. + + * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) + * Data resolution: 5 seconds + metric_type: counter + title: sf.org.num.azureServiceClientCallCount + +sf.org.num.azureServiceClientCallCountErrors: + brief: Number of calls to Azure API that threw errors + description: | + Number of calls to Azure API that threw errors. + + * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) + * Data resolution: 1 second + metric_type: counter + title: sf.org.num.azureServiceClientCallCountErrors + +sf.org.num.azureServiceClientCallCountThrottles: + brief: Number of calls to Azure API that were throttled + description: | + Number of calls to Azure API that were throttled. + + * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) + * Data resolution: 1 second + metric_type: counter + title: sf.org.num.azureServiceClientCallCountThrottles sf.org.num.chart: brief: Total number of charts From d63ab47ddc09fd9d8bc07fb30f41deb5fb71f459 Mon Sep 17 00:00:00 2001 From: bhillmer <86490494+bhillmer@users.noreply.github.com> Date: Mon, 1 May 2023 10:01:23 -0600 Subject: [PATCH 33/48] add sf.org.log.numLogsDroppedIndexThrottle (#1016) --- signalfx-org-metrics/metrics.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 2b63bbb4..5d856b0d 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -584,6 +584,16 @@ sf.org.log.numContentBytesReceivedByToken: metric_type: counter title: sf.org.log.numContentBytesReceivedByToken +sf.org.log.numLogsDroppedIndexThrottle: + brief: The number of logs Splunk Log Observer drops after the organization's allowed logs index limit threshold is met. + description: | + The number of logs Splunk Log Observer drops after the organization's allowed logs index limit threshold is met. + + * Dimension(s): `orgId` + * Data resolution: 10 second + metric_type: counter + title: sf.org.log.numLogsDroppedIndexThrottle + sf.org.log.numMessageBytesReceived: brief: The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. description: | From 26dcdea34830436393e534f52ae2f651ac1cc02b Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Mon, 29 May 2023 08:10:36 +0200 Subject: [PATCH 34/48] OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> --- signalfx-org-metrics/metrics.yaml | 62 ++++++++++++++++++++++++++++++- 1 file changed, 61 insertions(+), 1 deletion(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 5d856b0d..912d5fb5 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1253,6 +1253,16 @@ sf.org.numBackfillCallsByToken: * Data resolution: 1 second metric_type: counter title: sf.org.numBackfillCallsByToken + +sf.org.numComputationsStarted: + brief: Rate at which you're starting new jobs + description: | + Number of computations started, use it to know the rate at which you're starting new jobs. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numComputationsStarted sf.org.numBadDimensionMetricTimeSeriesCreateCalls: brief: Number of bad calls to create MTS due to an error with dimensions @@ -1356,6 +1366,16 @@ sf.org.numDatapointsDroppedBatchSize: * Data resolution: 10 seconds metric_type: counter title: sf.org.numDatapointsDroppedBatchSize + +sf.org.numDatapointsDroppedBatchSizeByToken: + brief: Number of data points dropped because a single request contained more than 100,000 data points, by token. + description: | + Number of data points dropped because a single request contained more than 100,000 data points, per token. In this scenario, Observability Cloud drops data points because it perceives sending more than 100,000 data points in a single request as excessive. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 40 seconds + metric_type: counter + title: sf.org.numDatapointsDroppedBatchSizeByToken sf.org.numDatapointsDroppedExceededQuota: brief: Number of new data points not processed by Infrastructure Monitoring; exceeded subscription @@ -1479,6 +1499,46 @@ sf.org.numDatapointsReceivedByToken: metric_type: counter title: sf.org.numDatapointsReceivedByToken +sf.org.numDimensionObjectsCreated: + brief: Number of dimensions created + description: | + Total number of dimensions created. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.numDimensionObjectsCreated + +sf.org.numDimensionObjectsCreatedByToken: + brief: Number of dimensions created by token + description: | + Total number of dimensions created by token. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 40 seconds + metric_type: gauge + title: sf.org.numDimensionObjectsCreatedByToken + +sf.org.numEventSearches: + brief: Number of event searches + description: | + Number of event searches. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numEventSearches + +sf.org.numEventSearchesThrottled: + brief: Number of event searches that were throttled + description: | + Number of event searches that were throttled. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numEventSearchesThrottled + sf.org.numEventTimeSeriesCreated: brief: Number of event time series created description: | @@ -1539,7 +1599,7 @@ sf.org.numEventsReceivedByToken: description: Reserved for Infrastructure Monitoring internal use only. metric_type: null title: sf.org.numEventsReceivedByToken - + sf.org.numHighResolutionMetrics: brief: Number of high resolution metrics monitored description: | From d6730e9c9a2b1d98f9b4dacf5b2b291c63b71793 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Thu, 1 Jun 2023 09:08:50 +0200 Subject: [PATCH 35/48] Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> --- signalfx-org-metrics/metrics.yaml | 74 ++++++++++++++++++++++++++++++- 1 file changed, 73 insertions(+), 1 deletion(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 912d5fb5..5a843736 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1622,6 +1622,26 @@ sf.org.numHighResolutionMetricsByToken: * Data resolution: 10 minutes metric_type: counter title: sf.org.numHighResolutionMetricsByToken + +sf.org.numHostMetaDataEventsDroppedThrottle: + brief: Number of host metadata events dropped due to throttling + description: | + Number of host metadata events dropped because of throttling. + + * Dimension(s): `orgId` + * Data resolution: 40 seconds + metric_type: counter + title: sf.org.numHostMetaDataEventsDroppedThrottle + +sf.org.numHostMetaDataEventsDroppedThrottleByToken: + brief: Number of host metadata events dropped due to throttling by token + description: | + Number of host metadata events dropped because of throttling, per token. + + * Dimension(s): `orgId, tokenId` + * Data resolution: 40 seconds + metric_type: counter + title: sf.org.numHostMetaDataEventsDroppedThrottleByToken sf.org.numInactiveTimeSeries: brief: Number of inactive MTS @@ -1637,6 +1657,16 @@ sf.org.numInactiveTimeSeries: * Data resolution: 1 second metric_type: gauge title: sf.org.numInactiveTimeSeries + +sf.org.numInvalidEventsDropped: + brief: Number of events dropped as invalid + description: | + Number of events dropped due to being invalid. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: gauge + title: sf.org.numInvalidEventsDropped sf.org.numLimitedEventTimeSeriesCreateCalls: brief: Number of event time series over maximum ETS allowed @@ -1688,7 +1718,7 @@ sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryType: * Data resolution: 10 seconds metric_type: counter title: sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryType - + sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken: brief: Number of MTS not sent per token; over maximum allowed. description: | @@ -1726,6 +1756,16 @@ sf.org.numLimitedMetricTimeSeriesCreateCallsByToken: metric_type: counter title: sf.org.numLimitedMetricTimeSeriesCreateCallsByToken +sf.org.numLogsReceivedByToken: + brief: Number of logs received by token + description: | + Number of logs received by token. + + * Dimension(s): `orgId, tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numLogsReceivedByToken + sf.org.numMappingsAdded: brief: Infrastructure Monitoring internal metric description: Reserved for Infrastructure Monitoring internal use only. @@ -1791,6 +1831,16 @@ sf.org.numMetricTimeSeriesCreatedByToken: metric_type: counter title: sf.org.numMetricTimeSeriesCreatedByToken +sf.org.numMetricObjectsCreatedByToken: + brief: Number of metric objects created by token + description: | + Number of metric objects created by token. + + * Dimension(s): `tokenId`, `orgId` + * Data resolution: 40 seconds + metric_type: gauge + title: sf.org.numMetricObjectsCreatedByToken + sf.org.numNewDimensions: brief: Number of new dimensions that were created description: | @@ -1811,6 +1861,16 @@ sf.org.numNewDimensionsByName: * Data resolution: 5 minutes metric_type: counter title: sf.org.numNewDimensionsByName + +sf.org.numProcessDataEventsDroppedThrottleByToken: + brief: Number of data ingest process events dropped due to throttling by token + description: | + Per token, number of data ingest process events dropped due to throttling, because you exceeded your system limits. + + * Dimension(s): `orgId, tokenIn` + * Data resolution: 40 seconds + metric_type: counter + title: sf.org.numProcessDataEventsDroppedThrottleByToken sf.org.numPropertyLimitedMetricTimeSeriesCreateCalls: brief: Number of MTS that Infrastructure Monitoring was not able to create because you exceeded the dimension name limit @@ -1850,6 +1910,18 @@ sf.org.numResourceMetrics: metric_type: gauge title: sf.org.numResourceMetrics +sf.org.numResourceMetricsbyToken: + brief: Number of resource metric time series (MTS) monitored per token. + description: | + Number of resource metric time series (MTS) received from host and container categories, per token. + + The `resourceType` dimension indicates whether the value represents hosts or containers. + + * Dimension(s): `orgId`, `resourceType`, `tokenId` + * Data resolution: 10 minutes + metric_type: gauge + title: sf.org.numResourceMetricsbyToken + sf.org.numResourcesMonitored: brief: Number of host-based resources monitored description: | From 04e928b2d52140571a2c15e14142e698c8ddad36 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Wed, 7 Jun 2023 10:54:42 +0200 Subject: [PATCH 36/48] Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> --- signalfx-org-metrics/metrics.yaml | 68 +++++++++++++++---------------- 1 file changed, 34 insertions(+), 34 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 5a843736..13b2f1ef 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -999,14 +999,14 @@ sf.org.num.metrictimeseries: title: sf.org.num.metrictimeseries sf.org.num.migrationmarker: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of migration markers + description: Number of migration markers. metric_type: gauge title: sf.org.num.migrationmarker sf.org.num.mutingactive: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of active muting rules NBED + description: Number of active muting rules NBED. metric_type: gauge title: sf.org.num.mutingactive @@ -1031,14 +1031,14 @@ sf.org.num.navigator: title: sf.org.num.navigator sf.org.num.notifications: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of notifications + description: Number of notifications. metric_type: cumulative title: sf.org.num.notifications sf.org.num.orgpreference: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of org preferences + description: Number of org preferences. metric_type: null title: sf.org.num.orgpreference @@ -1085,20 +1085,20 @@ sf.org.num.role: title: sf.org.num.role sf.org.num.service: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of services + description: Number of services. metric_type: null title: sf.org.num.service sf.org.num.shareablesnapshot: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of shareable snapshots + description: Number of shareable snapshots. metric_type: null title: sf.org.num.shareablesnapshot sf.org.num.source: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of sources + description: Number of sources. metric_type: null title: sf.org.num.source @@ -1438,8 +1438,8 @@ sf.org.numDatapointsDroppedInTimeout: title: sf.org.numDatapointsDroppedInTimeout sf.org.numDatapointsDroppedInTimeoutByToken: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of data points Observability Cloud didn't attempt to create because your account was throttled or limited in the previous few seconds, per token + description: Per token, number of data points Observability Cloud didn't attempt to create because your account was throttled or limited in the previous few seconds and creation was very unlikely to succeed. metric_type: null title: sf.org.numDatapointsDroppedInTimeoutByToken @@ -1588,15 +1588,15 @@ sf.org.numEventsDroppedThrottleByToken: title: sf.org.numEventsDroppedThrottleByToken sf.org.numEventsReceived: - brief: Infrastructure Monitoring internal metric + brief: Number of events received description: | - Reserved for Infrastructure Monitoring internal use only. + Number of events received. metric_type: null title: sf.org.numEventsReceived sf.org.numEventsReceivedByToken: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of events received per token + description: Number of events received, per token. metric_type: null title: sf.org.numEventsReceivedByToken @@ -1767,38 +1767,38 @@ sf.org.numLogsReceivedByToken: title: sf.org.numLogsReceivedByToken sf.org.numMappingsAdded: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of mappings added + description: Number of mappings added. metric_type: null title: sf.org.numMappingsAdded sf.org.numMappingsAddedByToken: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of mappings added by token + description: Per token, number of mappings added. metric_type: null title: sf.org.numMappingsAddedByToken sf.org.numMetadataWrites: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of metadata writes + description: Number of metadata writes. metric_type: null title: sf.org.numMetadataWrites sf.org.numMetadataWritesByToken: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of metadata writes by token + description: Per token, number of metadata writes. metric_type: null title: sf.org.numMetadataWritesByToken sf.org.numMetadataWritesThrottled: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of metadata writes throttled + description: Number of metadata writes throttled. metric_type: null title: sf.org.numMetadataWritesThrottled sf.org.numMetadataWritesThrottledByToken: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of metadata writes throttled per token + description: Number of metadata writes throttled per token. metric_type: null title: sf.org.numMetadataWritesThrottledByToken @@ -2114,8 +2114,8 @@ sf.org.subscription.function: title: sf.org.subscription.function sf.org.ui.num.pagevisits: - brief: Infrastructure Monitoring internal metric - description: Reserved for Infrastructure Monitoring internal use only. + brief: Number of UI page visits + description: Number of UI page visits. metric_type: null title: sf.org.ui.num.pagevisits From 7f6ab20e44497f528fe9cd971be1882e3f82f78e Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Wed, 7 Jun 2023 11:49:52 +0200 Subject: [PATCH 37/48] Update metrics.yaml (#1027) --- signalfx-org-metrics/metrics.yaml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 13b2f1ef..03ce953a 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -420,20 +420,20 @@ sf.org.datainventory.resources: title: sf.org.datainventory.resources sf.org.grossDatapointsReceived: - brief: Infrastructure Monitoring internal metric - description: sf.org.grossDatapointsReceived is reserved for Infrastructure Monitoring internal use only. + brief: Number of data points received, but not necessarily admitted + description: Number of data points received, but not necessarily admitted. metric_type: cumulative title: sf.org.grossDatapointsReceived sf.org.grossDatapointsReceivedByToken: - brief: Infrastructure Monitoring internal metric - description: sf.org.grossDatapointsReceivedByToken is reserved for Infrastructure Monitoring internal use only. + brief: Number of data points received, but not necessarily admitted, per token + description: Number of data points receuved, but not necessarily admitted, per token. metric_type: cumulative title: sf.org.grossDatapointsReceivedByToken sf.org.grossDpmContentBytesReceived: - brief: Infrastructure Monitoring internal metric - description: sf.org.grossDpmContentBytesReceived is reserved for Infrastructure Monitoring internal use only. + brief: Number of content bytes received, but not necessarily admitted + description: Number of content bytes received, but not necessarily admitted. metric_type: counter title: sf.org.grossDpmContentBytesReceived @@ -874,8 +874,8 @@ sf.org.numDetectorsAborted: title: sf.org.numDetectorsAborted sf.org.num.detectortemplate: - brief: Infrastructure Monitoring internal metric - description: sf.org.num.detectortemplate is reserved for Infrastructure Monitoring internal use only. + brief: Number of detector templates + description: Number of detector templates. metric_type: cumulative title: sf.org.num.detectortemplate From b71440d1bac1e4e464d9aabfc9df0d6c3fec086a Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Tue, 27 Jun 2023 11:52:03 +0200 Subject: [PATCH 38/48] OD3972-dpm-faqs (#1028) See jira for more details. --- signalfx-org-metrics/metrics.yaml | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 03ce953a..7ba9e839 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1381,10 +1381,8 @@ sf.org.numDatapointsDroppedExceededQuota: brief: Number of new data points not processed by Infrastructure Monitoring; exceeded subscription limit description: | - Total number of new data points you sent to Infrastructure Monitoring but that 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 [this FAQ](https://docs.signalfx.com/en/latest/_sidebars-and-includes/dpm-faq.html). + Total number of new data points you sent to Infrastructure Monitoring but that Infrastructure Monitoring didn't accept, because your organization exceeded its subscription limit. + To learn more, see [Exceeding your system limits](https://docs.splunk.com/Observability/admin/subscription-usage/dpm-usage.html#exceeding-your-system-limits). * Dimension(s): `orgId` * Data resolution: 1 second @@ -1397,11 +1395,9 @@ sf.org.numDatapointsDroppedExceededQuotaByToken: description: | One value per token; number of new data points you sent to Infrastructure Monitoring but that 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 [DPM Limits - FAQ](https://docs.signalfx.com/en/latest/_sidebars-and-includes/dpm-faq.html). - The sum of all the values might be less than the value of `sf.org.numDatapointsDroppedExceededQuota`. - To learn more, see [Metrics for values by token](#metrics-for-values-by-token). + limit. To learn more, see [Exceeding your system limits](https://docs.splunk.com/Observability/admin/subscription-usage/dpm-usage.html#exceeding-your-system-limits). + + The sum of all the values might be less than the value of `sf.org.numDatapointsDroppedExceededQuota`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). * Dimension(s): `orgId, tokenId` * Data resolution: 1 second From 4f05f454e79f024e845053fdee0d5cdb8714ec71 Mon Sep 17 00:00:00 2001 From: jason plumb <75337021+breedx-splk@users.noreply.github.com> Date: Tue, 8 Aug 2023 08:28:04 -0700 Subject: [PATCH 39/48] update java lib (#1018) --- lib-java/README.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/lib-java/README.md b/lib-java/README.md index dc4f2d7f..a9a62a1b 100644 --- a/lib-java/README.md +++ b/lib-java/README.md @@ -1,4 +1,4 @@ -# ![](./img/integrations_java.png) Java client library for SignalFx +# ![](./img/integrations_java.png) Java instrumentation for Splunk Observability Cloud - [Description](#description) @@ -7,12 +7,14 @@ ### DESCRIPTION -This repository contains libraries for instrumenting Java applications and reporting metrics to Splunk Infrastructure Monitoring, using Codahale Metrics. - -You can also use the module `signalfx-java` to send metrics directly to Splunk Infrastructure Monitoring using protocol buffers, without using Codahale or Yammer metrics. - -For more information regarding installation, usage, and examples see https://github.com/signalfx/signalfx-java +Java instrumentation is available from the +[Splunk Distribution of OpenTelemetry Java](https://github.com/signalfx/splunk-otel-java). This instrumentation agent provides +feature-rich auto-instrumentation with very little manual configuration. +It is built on top of the industry standard [OpenTelemetry](https://opentelemetry.io/). +Users building manual instrumentation can also leverage the +[OpenTelemetry Java SDK](https://github.com/open-telemetry/opentelemetry-java) +to send telemetry to Splunk. ### LICENSE From ffd646fe433ea4e3ce951fba02ae0d5f6575ffd0 Mon Sep 17 00:00:00 2001 From: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> Date: Tue, 22 Aug 2023 14:37:59 -0400 Subject: [PATCH 40/48] Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review --- requirements.txt | 2 +- signalfx-org-metrics/metrics.yaml | 792 +++++++++++++++--------------- 2 files changed, 410 insertions(+), 384 deletions(-) diff --git a/requirements.txt b/requirements.txt index e13f6634..a341315b 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,3 +1,3 @@ MarkupSafe==2.0.1 Jinja2==2.11.3 -PyYAML==5.4 +PyYAML==6.0.1 diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 7ba9e839..beaae29a 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -5,8 +5,8 @@ sf.org.apm.grossContentBytesReceived: The volume of bytes Splunk APM receives off the wire before filtering and throttling. This content could be compressed. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.grossContentBytesReceived @@ -17,8 +17,8 @@ sf.org.apm.grossSpanBytesReceived: The number of bytes Splunk APM receives from spans after decompression but before filtering and throttling. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.grossSpanBytesReceived @@ -30,8 +30,8 @@ sf.org.apm.grossSpanBytesReceivedByToken: The number of bytes Splunk APM receives for a specific access token from ingested span data after decompression but before filtering and throttling. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.grossSpanBytesReceivedByToken @@ -40,8 +40,8 @@ sf.org.apm.grossSpansReceived: description: | The number of spans Splunk APM received before filtering or throttling. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.grossSpansReceived @@ -50,8 +50,8 @@ sf.org.apm.ingestLatency.duration.ns.min: description: | The minimum duration of the ingest latency in Splunk APM. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: gauge title: sf.org.apm.ingestLatency.duration.ns.min @@ -72,8 +72,8 @@ sf.org.apm.numAddSpansCalls: description: | The number of calls to the `/v2/trace` endpoint. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numAddSpansCalls @@ -82,8 +82,8 @@ sf.org.apm.numAddSpansCallsByToken: description: | The number of calls to the `/v2/trace` endpoint for a specific access token. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numAddSpansCallsByToken @@ -92,8 +92,8 @@ sf.org.apm.numContainers: description: | The number of containers actively sending data to Splunk APM. - * Dimension(s): `orgId` - * Data resolution: 1 minute + * Dimension(s): `orgId` + * Data resolution: 1 minute metric_type: gauge title: sf.org.apm.numContainers @@ -101,8 +101,8 @@ sf.org.apm.numHosts: brief: The number of hosts that are actively sending data to Splunk APM. description: | The number of hosts that are actively sending data to Splunk APM. - * Dimension(s): `orgId` - * Data resolution: 1 minute + * Dimension(s): `orgId` + * Data resolution: 1 minute metric_type: gauge title: sf.org.apm.numHosts @@ -113,8 +113,8 @@ sf.org.apm.numSpanBytesReceived: The number of bytes Splunk APM accepts from ingested span data after decompression after filtering and throttling. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpanBytesReceived @@ -125,8 +125,8 @@ sf.org.apm.numSpanBytesReceivedByToken: The number of bytes Splunk APM accepts for a specific access token for a span after decompression after filtering and throttling. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpanBytesReceivedByToken @@ -137,8 +137,8 @@ sf.org.apm.numSpansDroppedInvalid: invalid if there is no start time, trace ID, or service associated with it, or if there are too many spans in the trace. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpansDroppedInvalid @@ -150,8 +150,8 @@ sf.org.apm.numSpansDroppedInvalidByToken: access token. A span can be invalid if there is no start time, trace ID, or service associated with it, or if there are too many spans in the trace. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpansDroppedInvalidByToken @@ -160,8 +160,8 @@ sf.org.apm.numSpansDroppedOversize: description: | The number of spans Splunk APM receives that are too large to process. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpansDroppedOversize @@ -172,8 +172,8 @@ sf.org.apm.numSpansDroppedOversizeByToken: The number of spans Splunk APM receives that are too large to process for a specific access token. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpansDroppedOversizeByToken @@ -183,8 +183,8 @@ sf.org.apm.numSpansDroppedThrottle: The number of spans Splunk APM dropped after you exceeded the allowed ingest volume. Splunk APM drops spans it receives after the ingestion volume limit is reached. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpansDroppedThrottle @@ -196,8 +196,8 @@ sf.org.apm.numSpansDroppedThrottleByToken: beyond the allowed ingest volume. Splunk APM drops spans it receives after the ingestion volume limit is reached. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpansDroppedThrottleByToken @@ -206,8 +206,8 @@ sf.org.apm.numSpansReceived: description: | The number of spans Splunk APM accepts after filtering and throttling. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpansReceived @@ -218,8 +218,8 @@ sf.org.apm.numSpansReceivedByToken: The number of spans Splunk APM received for a specific access token after filtering and throttling. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpansReceivedByToken @@ -230,8 +230,8 @@ sf.org.apm.grossSpansReceivedByToken: The number of spans Splunk APM receives for a specific access token before filtering or throttling. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.grossSpansReceivedByToken @@ -240,8 +240,8 @@ sf.org.apm.subscription.containers: description: | The entitlement for the number of containers for your subscription plan. - * Dimension(s): `orgId` - * Data resolution: 2 minutes + * Dimension(s): `orgId` + * Data resolution: 2 minutes metric_type: gauge title: sf.org.apm.subscription.containers @@ -250,8 +250,8 @@ sf.org.apm.subscription.hosts: description: | The entitlement for the number of hosts for your subscription plan. - * Dimension(s): `orgId` - * Data resolution: 2 minutes + * Dimension(s): `orgId` + * Data resolution: 2 minutes metric_type: gauge title: sf.org.apm.subscription.hosts @@ -260,8 +260,8 @@ sf.org.apm.subscription.monitoringMetricSets: description: | The entitlement for the number of Monitoring MetricSets as part of your subscription plan. - * Dimension(s): `orgId` - * Data resolution: 2 minutes + * Dimension(s): `orgId` + * Data resolution: 2 minutes metric_type: gauge title: sf.org.apm.subscription.monitoringMetricSets @@ -270,8 +270,8 @@ sf.org.apm.subscription.spanBytes: description: | The entitlement for the number of bytes per minutes for your subscription plan. - * Dimension(s): `orgId` - * Data resolution: 2 minutes + * Dimension(s): `orgId` + * Data resolution: 2 minutes metric_type: gauge title: sf.org.apm.subscription.spanBytes @@ -280,8 +280,8 @@ sf.org.apm.subscription.traces: description: | The entitlement for the number of traces analyzed per minute (TAPM) as part of your subscription plan. - * Dimension(s): `orgId` - * Data resolution: 2 minutes + * Dimension(s): `orgId` + * Data resolution: 2 minutes metric_type: gauge title: sf.org.apm.subscription.traces @@ -290,8 +290,8 @@ sf.org.apm.subscription.troubleshootingMetricSets: description: | The entitlement for the number of Troubleshooting MetricSets as part of your subscription plan. - * Dimension(s): `orgId` - * Data resolution: 2 minutes + * Dimension(s): `orgId` + * Data resolution: 2 minutes metric_type: gauge title: sf.org.apm.subscription.troubleshootingMetricSets @@ -300,8 +300,8 @@ sf.org.apm.numTracesReceived: description: | The number of traces Splunk APM receives and processes. - * Dimension(s): `orgId` - * Data resolution: 1 minute + * Dimension(s): `orgId` + * Data resolution: 1 minute metric_type: counter title: sf.org.apm.numTracesReceived @@ -310,8 +310,8 @@ sf.org.apm.numTroubleshootingMetricSets10s: description: | The cardinality of Troubleshooting MetricSets for each 10-second window. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: gauge title: sf.org.apm.numTroubleshootingMetricSets10s @@ -320,8 +320,8 @@ sf.org.apm.numTroubleshootingMetricSets: description: | The cardinality of Troubleshooting MetricSets for each 1-minute time window. - * Dimension(s): `orgId` - * Data resolution: 1 minute + * Dimension(s): `orgId` + * Data resolution: 1 minute metric_type: counter title: sf.org.apm.numTroubleshootingMetricSets @@ -332,8 +332,8 @@ sf.org.apm.numContentBytesReceived: The volume of bytes Splunk APM accepts off the wire after filtering and throttling. This content could be compressed. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numContentBytesReceived @@ -344,8 +344,8 @@ sf.org.apm.grossContentBytesReceivedByToken: The volume of bytes Splunk APM receives off the wire for a specific access token before filtering and throttling. This content could be compressed. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.grossContentBytesReceivedByToken @@ -356,8 +356,8 @@ sf.org.apm.numContentBytesReceivedByToken: The volume of bytes Splunk APM accepts off the wire for a specific access token after filtering and throttling. This content could be compressed. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.apm.numContentBytesReceivedByToken @@ -374,8 +374,8 @@ sf.org.datapointsTotalCountByToken: description: | Total datapoints by token - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 seconds + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.datapointsTotalCountByToken @@ -384,8 +384,8 @@ sf.org.datainventory.datapointsAdded: description: | Number of data points retrieved from the AWS integration - * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` - * Data resolution: 10 seconds + * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` + * Data resolution: 10 seconds metric_type: count title: sf.org.datainventory.datapointsAdded @@ -394,8 +394,8 @@ sf.org.datainventory.latestTimestamp: description: | Timestamp of the last data point retrieved from an integration - * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` - * Data resolution: 10 seconds + * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` + * Data resolution: 10 seconds metric_type: gauge title: sf.org.datainventory.latestTimestamp @@ -404,8 +404,8 @@ sf.org.datainventory.mtses: description: | Number of Metric Time Series retrieved from an AWS integration. It’s only generated when AWS metrics are polled, and is not available with Metric Streams - * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` - * Data resolution: 10 seconds + * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` + * Data resolution: 10 seconds metric_type: gauge title: sf.org.datainventory.mtses @@ -414,8 +414,8 @@ sf.org.datainventory.resources: description: | Number of AWS resources polled by an AWS integration. It's only generated when AWS metrics are polled, and is not available with Metric Streams - * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` - * Data resolution: 10 seconds + * Dimension(s): `type: AWS`, `service`, `region`, `integrationId` + * Data resolution: 10 seconds metric_type: gauge title: sf.org.datainventory.resources @@ -509,8 +509,8 @@ sf.org.log.grossContentBytesReceived: description: | The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossContentBytesReceived @@ -519,8 +519,8 @@ sf.org.log.grossContentBytesReceivedByToken: description: | The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossContentBytesReceivedByToken @@ -529,8 +529,8 @@ sf.org.log.grossMessageBytesReceived: description: | The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossMessageBytesReceived @@ -539,8 +539,8 @@ sf.org.log.grossMessageBytesReceivedByToken: description: | The number of bytes received by Splunk Log Observer for a specific access token from ingested logs after decompression but before filtering and throttling are complete. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossMessageBytesReceivedByToken @@ -549,8 +549,8 @@ sf.org.log.grossMessagesReceived: description: | The total number of log messages Splunk Log Observer receives before filtering and throttling. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossMessagesReceived @@ -559,8 +559,8 @@ sf.org.log.grossMessagesReceivedByToken: description: | The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.grossMessagesReceivedByToken @@ -569,8 +569,8 @@ sf.org.log.numContentBytesReceived: description: | The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numContentBytesReceived @@ -579,8 +579,8 @@ sf.org.log.numContentBytesReceivedByToken: description: | The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numContentBytesReceivedByToken @@ -589,8 +589,8 @@ sf.org.log.numLogsDroppedIndexThrottle: description: | The number of logs Splunk Log Observer drops after the organization's allowed logs index limit threshold is met. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numLogsDroppedIndexThrottle @@ -599,8 +599,8 @@ sf.org.log.numMessageBytesReceived: description: | The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessageBytesReceived @@ -609,8 +609,8 @@ sf.org.log.numMessageBytesReceivedByToken: description: | The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessageBytesReceivedByToken @@ -619,8 +619,8 @@ sf.org.log.numMessagesDroppedThrottle: description: | The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesDroppedThrottle @@ -629,8 +629,8 @@ sf.org.log.numMessagesDroppedOversize: description: | The number of log messages Splunk Log Observer receives that are too large to process. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesDroppedOversize @@ -639,8 +639,8 @@ sf.org.log.numMessagesDroppedOversizeByToken: description: | The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesDroppedOversizeByToken @@ -649,8 +649,8 @@ sf.org.log.numMessagesDroppedThrottleByToken: description: | The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesDroppedThrottleByToken @@ -659,8 +659,8 @@ sf.org.log.numMessagesReceived: description: | The total number of log messages Splunk Log Observer accepts after filtering and throttling. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesReceived @@ -669,8 +669,8 @@ sf.org.log.numMessagesReceivedByToken: description: | The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. - * Dimension(s): `orgId` - * Data resolution: 10 second + * Dimension(s): `orgId` + * Data resolution: 10 second metric_type: counter title: sf.org.log.numMessagesReceivedByToken @@ -679,8 +679,8 @@ sf.org.log.numMessageBytesIndexed: description: | Bytes of data stored in the Log Observer index after applying pipeline management rules. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessageBytesIndexed @@ -690,8 +690,8 @@ sf.org.num.alertmuting: Total number of alert muting rules; includes rules currently in effect and rules not currently in effect (e.g. scheduled muting rules). - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.alertmuting @@ -699,9 +699,9 @@ sf.org.num.awsServiceAuthErrorCount: brief: Authentication errors thrown by AWS services 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) - * Data resolution: 1 second + + * 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 @@ -710,9 +710,9 @@ sf.org.num.awsServiceCallCount: description: | Total number of calls made to the Amazon API. - * Dimension(s): `orgId`, `namespace` (AWS service, such as `AWS/Cloudwatch`), `method` - (the API being called, such as `getMetricStatistics`) - * Data resolution: 5 seconds + * Dimension(s): `orgId`, `namespace` (AWS service, such as `AWS/Cloudwatch`), `method` + (the API being called, such as `getMetricStatistics`) + * Data resolution: 5 seconds metric_type: gauge title: sf.org.num.awsServiceCallCount @@ -721,10 +721,10 @@ sf.org.num.awsServiceCallCountExceptions: description: | Number of calls made to the Amazon API that threw exceptions. - * Dimension(s): `orgId`, `namespace` (AWS service, such as AWS/Cloudwatch), `method` - (the API being called, such as `getMetricStatistics`), `location` (where the exception - occurred, either `client` or `server`) - * Data resolution: 5 seconds + * Dimension(s): `orgId`, `namespace` (AWS service, such as AWS/Cloudwatch), `method` + (the API being called, such as `getMetricStatistics`), `location` (where the exception + occurred, either `client` or `server`) + * Data resolution: 5 seconds metric_type: gauge title: sf.org.num.awsServiceCallCountExceptions @@ -734,9 +734,9 @@ sf.org.num.awsServiceCallThrottles: Number of calls made to the Amazon API that are being throttled by AWS because you have exceeded your AWS API Call limits. - * Dimension(s): `orgId`, `namespace` (AWS service, such as AWS/Cloudwatch), `method` - (the API being called, such as `getMetricStatistics`) - * Data resolution: 5 seconds + * Dimension(s): `orgId`, `namespace` (AWS service, such as AWS/Cloudwatch), `method` + (the API being called, such as `getMetricStatistics`) + * Data resolution: 5 seconds metric_type: gauge title: sf.org.num.awsServiceCallThrottles @@ -747,22 +747,21 @@ sf.org.num.azureMonitorClientCallCount (DEPRECATED): PLEASE USE `sf.org.num.azureServiceClientCallCount` INSTEAD Total number of calls made to the Azure Monitor API. - * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric - syncing and `metric_metadata_sync` for property syncing) - * Data resolution: 5 seconds + * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric + syncing and `metric_metadata_sync` for property syncing) + * Data resolution: 5 seconds metric_type: counter title: sf.org.num.azureMonitorClientCallCount sf.org.num.azureMonitorClientCallCountErrors (DEPRECATED): brief: Number of calls to Azure Monitor API method that threw errors description: | - THIS METRIC IS DEPRECATED AND WILL BE REMOVED. - PLEASE USE `sf.org.num.azureServiceClientCallCountErrors` INSTEAD + Note: This metric is deprecated. Use `sf.org.num.azureServiceClientCallCountErrors` instead. Number of calls to Azure Monitor API method that threw errors. - * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric - syncing and `metric_metadata_sync` for property syncing) - * Data resolution: 1 second + * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric + syncing and `metric_metadata_sync` for property syncing) + * Data resolution: 1 second metric_type: counter title: sf.org.num.azureMonitorClientCallCountErrors @@ -773,9 +772,9 @@ sf.org.num.azureMonitorClientCallCountThrottles (DEPRECATED): PLEASE USE `sf.org.num.azureServiceClientCallCountThrottles` INSTEAD Number of calls to Azure Monitor method that were throttled. - * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric - syncing and `metric_metadata_sync` for property syncing) - * Data resolution: 1 second + * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric + syncing and `metric_metadata_sync` for property syncing) + * Data resolution: 1 second metric_type: counter title: sf.org.num.azureMonitorClientCallCountThrottles @@ -784,8 +783,8 @@ sf.org.num.azureServiceClientCallCount: description: | Total number of calls made to the Azure API. - * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) - * Data resolution: 5 seconds + * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) + * Data resolution: 5 seconds metric_type: counter title: sf.org.num.azureServiceClientCallCount @@ -794,8 +793,8 @@ sf.org.num.azureServiceClientCallCountErrors: description: | Number of calls to Azure API that threw errors. - * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) - * Data resolution: 1 second + * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) + * Data resolution: 1 second metric_type: counter title: sf.org.num.azureServiceClientCallCountErrors @@ -804,8 +803,8 @@ sf.org.num.azureServiceClientCallCountThrottles: description: | Number of calls to Azure API that were throttled. - * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) - * Data resolution: 1 second + * Dimension(s): `orgId`, `integrationId`, `subscriptionId`, `api` (`AzureMonitor` or `AzureResourceManager`), `method` (only for `api`=`AzureMonitor`, the API being called, such as `getTimeseries`), `resource` (only for `api`=`AzureResourceMonitor`, resource asked for, such as `microsoft.compute/virtualmachines`) + * Data resolution: 1 second metric_type: counter title: sf.org.num.azureServiceClientCallCountThrottles @@ -815,8 +814,8 @@ sf.org.num.chart: Total number of charts; includes any charts created using the Infrastructure Monitoring API but not associated with a dashboard. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.chart @@ -827,8 +826,8 @@ sf.org.num.credentials: in Infrastructure Monitoring, for the purpose of retrieving metrics (example: AWS Cloudwatch) or sending alerts (example: PagerDuty). - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.credentials @@ -837,8 +836,8 @@ sf.org.num.crosslink: description: | Total number of crosslinks. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.crosslink @@ -848,8 +847,8 @@ sf.org.num.dashboard: Total number of dashboards; includes all user, custom, and built-in dashboards - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.dashboard @@ -858,8 +857,8 @@ sf.org.num.detector: description: | Total number of detectors; includes detectors that are muted. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.detector @@ -868,8 +867,8 @@ sf.org.numDetectorsAborted: description: | Number of detector jobs stopped because they reached a resource limit (usually MTS limit). - * Dimension(s): `orgId` - * Data resolution: 5 seconds + * Dimension(s): `orgId` + * Data resolution: 5 seconds metric_type: counter title: sf.org.numDetectorsAborted @@ -884,8 +883,8 @@ sf.org.num.dimension: description: | Number of unique dimensions across all time series. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.dimension @@ -896,8 +895,8 @@ sf.org.num.eventtimeseries: Number of event time series (ETS) available to be visualized in charts and detectors. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.eventtimeseries @@ -906,44 +905,41 @@ sf.org.num.eventtype: description: | Number of unique event types across all ETS. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.eventtype sf.org.num.gcpStackdriverClientCallCount (DEPRECATED): brief: Number of calls to each Stackdriver client method description: | - THIS METRIC IS DEPRECATED AND WILL BE REMOVED. - PLEASE USE `sf.org.num.gcpServiceClientCallCount` INSTEAD + Note: This metric is deprecated. Use `sf.org.num.gcpServiceClientCallCount` instead. Number of calls to each Stackdriver client method. - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second metric_type: counter title: sf.org.num.gcpStackdriverClientCallCount sf.org.num.gcpStackdriverClientCallCountErrors (DEPRECATED): brief: Number of calls to each Stackdriver client method that threw errors description: | - THIS METRIC IS DEPRECATED AND WILL BE REMOVED. - PLEASE USE `sf.org.num.gcpServiceClientCallCountErrors` INSTEAD + Note: This metric is deprecated. Use `sf.org.num.gcpServiceClientCallCountErrors` instead. Number of calls to each Stackdriver client method that threw errors. - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second metric_type: counter title: sf.org.num.gcpStackdriverClientCallCountErrors sf.org.num.gcpStackdriverClientCallCountThrottles (DEPRECATED): brief: Number of calls to each Stackdriver client method that were throttled description: | - THIS METRIC IS DEPRECATED AND WILL BE REMOVED. - PLEASE USE `sf.org.num.gcpServiceClientCallCountThrottles` INSTEAD + Note: This metric is deprecated. Use `sf.org.num.gcpServiceClientCallCountThrottles` instead. Number of calls to each Stackdriver client method that were throttled. - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second metric_type: counter title: sf.org.num.gcpStackdriverClientCallCountThrottles @@ -952,8 +948,8 @@ sf.org.num.gcpServiceClientCallCount: description: | Number of calls to each GCP API client method. - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second metric_type: counter title: sf.org.num.gcpSeviceClientCallCount @@ -962,8 +958,8 @@ sf.org.num.gcpServiceClientCallCountErrors: description: | Number of calls to each GCP API client method that threw errors. - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second metric_type: counter title: sf.org.num.gcpServiceClientCallCountErrors @@ -972,8 +968,8 @@ sf.org.num.gcpServiceClientCallCountThrottles: description: | Number of calls to each GCP API client method that were throttled. - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second + * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) + * Data resolution: 1 second metric_type: counter title: sf.org.num.gcpServiceClientCallCountThrottles @@ -982,8 +978,8 @@ sf.org.num.metric: description: | Number of unique metrics across all MTS. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.metric @@ -993,8 +989,8 @@ sf.org.num.metrictimeseries: Number of metric time series (MTS) available to be visualized in charts and detectors. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.metrictimeseries @@ -1015,8 +1011,8 @@ sf.org.num.namedtoken: description: | Number of organization access tokens, including disabled tokens. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.namedtoken @@ -1025,8 +1021,8 @@ sf.org.num.navigator: description: | Number of options available in the sidebar in the Infrastructure Navigator. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.navigator @@ -1048,8 +1044,8 @@ sf.org.num.orguser: Total number of members and admins associated with an organization; includes invited users who have not yet logged in. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.orguser @@ -1059,8 +1055,8 @@ sf.org.num.page: Total number of dashboard groups; includes user, custom, and built-in dashboard groups. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.page @@ -1070,8 +1066,8 @@ sf.org.num.property: Number of properties; includes only properties you have created, not dimensions. For the latter, use ``sf.org.num.dimension``. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.property @@ -1079,8 +1075,8 @@ sf.org.num.role: brief: Number of roles in your system description: | Number of roles in your system. - * Dimension(s): `orgId` - * Data resolution: 63 minutes + * Dimension(s): `orgId` + * Data resolution: 63 minutes metric_type: gauge title: sf.org.num.role @@ -1107,8 +1103,8 @@ sf.org.num.tag: description: | Number of tags available for use. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.tag @@ -1117,8 +1113,8 @@ sf.org.num.team: description: | Number of teams in the organization. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.team @@ -1129,8 +1125,8 @@ sf.org.num.teammember: total number of users. For example, if team A has 30 members and team B has 20 members, the value is 50 even if there are only 30 members in the org. - * Dimension(s): `orgId` - * Data resolution: 15 minutes + * Dimension(s): `orgId` + * Data resolution: 15 minutes metric_type: gauge title: sf.org.num.teammember @@ -1153,8 +1149,8 @@ sf.org.numAddDatapointCalls: description: | Number of calls to send data points to Infrastructure Monitoring. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numAddDatapointCalls @@ -1165,8 +1161,8 @@ sf.org.numAddDatapointCallsByToken: The sum of all the values might be less than the value of `sf.org.numAddDatapointCalls`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numAddDatapointCallsByToken @@ -1175,8 +1171,8 @@ sf.org.numAddEventsCalls: description: | Number of calls to send custom events to Infrastructure Monitoring. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numAddEventsCalls @@ -1187,8 +1183,8 @@ sf.org.numAddEventsCallsByToken: The sum of all the values might be less than the value of `sf.org.numAddEventsCalls`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numAddEventsCallsByToken @@ -1197,8 +1193,8 @@ sf.org.numApmApiCalls: description: | Number of calls made to APM’s public APIs. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numApmApiCalls @@ -1207,8 +1203,8 @@ sf.org.numApmBundledMetrics: description: | APM Bundled Metrics limit for your org. - * Dimension(s): `orgId` - * Data resolution: 10 minutes + * Dimension(s): `orgId` + * Data resolution: 10 minutes metric_type: gauge title: sf.org.numApmBundledMetrics @@ -1217,8 +1213,8 @@ sf.org.numApmBundledMetricsByToken: description: | APM Bundled Metrics limit for your org for a specific token. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 minutes + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 minutes metric_type: gauge title: sf.org.numApmBundledMetricsByToken @@ -1232,8 +1228,8 @@ sf.org.numBackfillCalls: "cumulative_counter", or "gauge". To learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type). - * Dimension(s): `category, orgId` - * Data resolution: 1 second + * Dimension(s): `category, orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numBackfillCalls @@ -1249,28 +1245,18 @@ sf.org.numBackfillCallsByToken: The sum of all the values might be less than the value of `sf.org.numBackfillCalls`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `category`, `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `category`, `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numBackfillCallsByToken - -sf.org.numComputationsStarted: - brief: Rate at which you're starting new jobs - description: | - Number of computations started, use it to know the rate at which you're starting new jobs. - - * Dimension(s): `orgId` - * Data resolution: 10 seconds - metric_type: counter - title: sf.org.numComputationsStarted sf.org.numBadDimensionMetricTimeSeriesCreateCalls: brief: Number of bad calls to create MTS due to an error with dimensions description: | Number of calls to create MTS that have failed due to an error with dimensions. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numBadDimensionMetricTimeSeriesCreateCalls @@ -1279,8 +1265,8 @@ sf.org.numBadDimensionMetricTimeSeriesCreateCallsByToken: description: | Number of calls to create MTS that have failed due to an error with dimensions, per token. - * Dimension(s): `orgId` - * Data resolution: 35 seconds + * Dimension(s): `orgId` + * Data resolution: 35 seconds metric_type: counter title: sf.org.numBadDimensionMetricTimeSeriesCreateCallsByToken @@ -1289,8 +1275,8 @@ sf.org.numBadMetricMetricTimeSeriesCreateCalls: description: | Number of calls to create MTS that have failed due to an error with metrics. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numBadMetricMetricTimeSeriesCreateCalls @@ -1299,8 +1285,8 @@ sf.org.numBadMetricMetricTimeSeriesCreateCallsByToken: description: | Number of calls to create MTS that have failed due to an error with metrics, per token. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 35 seconds + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 35 seconds metric_type: counter title: sf.org.numBadMetricMetricTimeSeriesCreateCallsByToken @@ -1309,20 +1295,60 @@ sf.org.numCustomMetrics: description: | Number of custom metrics monitored by Infrastructure Monitoring. - * Dimension(s): `orgId` - * Data resolution: 10 minutes + * Dimension(s): `orgId` + * Data resolution: 10 minutes metric_type: counter title: sf.org.numCustomMetrics +sf.org.numComputationsStarted: + brief: Rate at which you're starting new SignalFlow jobs + description: | + Number of SignalFlow computations, which mostly consist of chart views and detectors, started. Use this metric to know the rate at which you're starting new SignalFlow jobs. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numComputationsStarted + +sf.org.numComputationsStartedByToken: + brief: Rate at which you're starting new SignalFlow jobs, per token + description: | + One value per token. Number of SignalFlow computations, which mostly consist of chart views and detectors, started. Use this metric to know the rate at which you're starting new SignalFlow jobs. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: 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]. + + * 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]. + + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numComputationsThrottledByToken + sf.org.numCustomMetricsByToken: brief: Per token number of custom metrics monitored description: | - One value per token; number of custom metrics monitored by Infrastructure Monitoring. + One value per token; number of custom metrics monitored by Splunk Observability Cloud. The sum of all the values might be less than the value of `sf.org.numCustomMetrics`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 10 minutes + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 minutes metric_type: counter title: sf.org.numCustomMetricsByToken @@ -1336,8 +1362,8 @@ sf.org.numDatapointsBackfilled: 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): `category, orgId` - * Data resolution: 1 second + * Dimension(s): `category`, `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numDatapointsBackfilled @@ -1352,8 +1378,8 @@ sf.org.numDatapointsBackfilledByToken: The sum of all the values might be less than the value of `sf.org.numDatapointsBackfilled`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `category, orgId, tokenId` - * Data resolution: 1 second + * Dimension(s): `category`, `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numDatapointsBackfilledByToken @@ -1362,8 +1388,8 @@ sf.org.numDatapointsDroppedBatchSize: description: | Number of data points dropped because a single request contained more than 100,000 data points. In this scenario, Observability Cloud drops data points because it perceives sending more than 100,000 data points in a single request as excessive. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numDatapointsDroppedBatchSize @@ -1372,8 +1398,8 @@ sf.org.numDatapointsDroppedBatchSizeByToken: description: | Number of data points dropped because a single request contained more than 100,000 data points, per token. In this scenario, Observability Cloud drops data points because it perceives sending more than 100,000 data points in a single request as excessive. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 40 seconds + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 40 seconds metric_type: counter title: sf.org.numDatapointsDroppedBatchSizeByToken @@ -1384,8 +1410,8 @@ sf.org.numDatapointsDroppedExceededQuota: Total number of new data points you sent to Infrastructure Monitoring but that Infrastructure Monitoring didn't accept, because your organization exceeded its subscription limit. To learn more, see [Exceeding your system limits](https://docs.splunk.com/Observability/admin/subscription-usage/dpm-usage.html#exceeding-your-system-limits). - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numDatapointsDroppedExceededQuota @@ -1399,8 +1425,8 @@ sf.org.numDatapointsDroppedExceededQuotaByToken: The sum of all the values might be less than the value of `sf.org.numDatapointsDroppedExceededQuota`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numDatapointsDroppedExceededQuotaByToken @@ -1409,8 +1435,8 @@ sf.org.numDatapointsDroppedInvalid: description: | 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. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numDatapointsDroppedInvalid @@ -1418,8 +1444,8 @@ sf.org.numDatapointsDroppedInvalidByToken: brief: Number of data points dropped because they didn't follow documented guidelines for data points. description: | Number of data points for a specific access token that are 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. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 seconds + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numDatapointsDroppedInvalidByToken @@ -1428,8 +1454,8 @@ sf.org.numDatapointsDroppedInTimeout: description: | Number of data points Observability Cloud didn't attempt to create because your account was throttled or limited in the previous few seconds and creation was very unlikely to succeed. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numDatapointsDroppedInTimeout @@ -1449,8 +1475,8 @@ sf.org.numDatapointsDroppedThrottle: data points for both existing and new MTS. If Infrastructure Monitoring is throttling your organization, it isn't keeping any of your data. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numDatapointsDroppedThrottle @@ -1466,8 +1492,8 @@ sf.org.numDatapointsDroppedThrottleByToken: The sum of all the values might be less than the value of `sf.org.numDatapointsDroppedThrottle`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numDatapointsDroppedThrottleByToken @@ -1491,7 +1517,7 @@ sf.org.numDatapointsReceivedByToken: You can have up to three MTS for this metric. To learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type). The sum of all the values might be less than the value of `sf.org.numDatapointsReceived`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Data resolution: 1 second + * Data resolution: 1 second metric_type: counter title: sf.org.numDatapointsReceivedByToken @@ -1500,8 +1526,8 @@ sf.org.numDimensionObjectsCreated: description: | Total number of dimensions created. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: gauge title: sf.org.numDimensionObjectsCreated @@ -1510,8 +1536,8 @@ sf.org.numDimensionObjectsCreatedByToken: description: | Total number of dimensions created by token. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 40 seconds + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 40 seconds metric_type: gauge title: sf.org.numDimensionObjectsCreatedByToken @@ -1519,9 +1545,9 @@ sf.org.numEventSearches: brief: Number of event searches description: | Number of event searches. - - * Dimension(s): `orgId` - * Data resolution: 10 seconds + + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numEventSearches @@ -1529,9 +1555,9 @@ sf.org.numEventSearchesThrottled: brief: Number of event searches that were throttled description: | Number of event searches that were throttled. - - * Dimension(s): `orgId` - * Data resolution: 10 seconds + + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numEventSearchesThrottled @@ -1540,8 +1566,8 @@ sf.org.numEventTimeSeriesCreated: description: | Total number of event time series (ETS) created. For MTS values, see `sf.org.numMetricTimeSeriesCreated`. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numEventTimeSeriesCreated @@ -1553,8 +1579,8 @@ sf.org.numEventTimeSeriesCreatedByToken: The sum of all the values might be less than the value of `sf.org.numEventTimeSeriesCreated`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numEventTimeSeriesCreatedByToken @@ -1564,8 +1590,8 @@ sf.org.numEventsDroppedThrottle: Number of custom events you sent to Infrastructure Monitoring but that Infrastructure Monitoring didn't accept, because your organization exceeded its per-minute limit. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numEventsDroppedThrottle @@ -1578,8 +1604,8 @@ sf.org.numEventsDroppedThrottleByToken: The sum of all the values might be less than the value of `sf.org.numEventsDroppedThrottle`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numEventsDroppedThrottleByToken @@ -1601,8 +1627,8 @@ sf.org.numHighResolutionMetrics: description: | Number of high resolution metrics monitored by Infrastructure Monitoring - * Dimension(s): `orgId` - * Data resolution: 10 minutes + * Dimension(s): `orgId` + * Data resolution: 10 minutes metric_type: counter title: sf.org.numHighResolutionMetrics @@ -1614,8 +1640,8 @@ sf.org.numHighResolutionMetricsByToken: The sum of all the values might be less than the value of `sf.org.numHighResolutionMetrics`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 10 minutes + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 10 minutes metric_type: counter title: sf.org.numHighResolutionMetricsByToken @@ -1624,8 +1650,8 @@ sf.org.numHostMetaDataEventsDroppedThrottle: description: | Number of host metadata events dropped because of throttling. - * Dimension(s): `orgId` - * Data resolution: 40 seconds + * Dimension(s): `orgId` + * Data resolution: 40 seconds metric_type: counter title: sf.org.numHostMetaDataEventsDroppedThrottle @@ -1634,8 +1660,8 @@ sf.org.numHostMetaDataEventsDroppedThrottleByToken: description: | Number of host metadata events dropped because of throttling, per token. - * Dimension(s): `orgId, tokenId` - * Data resolution: 40 seconds + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 40 seconds metric_type: counter title: sf.org.numHostMetaDataEventsDroppedThrottleByToken @@ -1670,8 +1696,8 @@ sf.org.numLimitedEventTimeSeriesCreateCalls: Number of event time series (ETS) that Infrastructure Monitoring was unable to create because you exceeded the maximum number of ETS allowed. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numLimitedEventTimeSeriesCreateCalls @@ -1684,8 +1710,8 @@ sf.org.numLimitedEventTimeSeriesCreateCallsByToken: The sum of all the values might be less than the value of `sf.org.numLimitedEventTimeSeriesCreateCalls`. To learn more, [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `category`, `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `category`, `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numLimitedEventTimeSeriesCreateCallsByToken @@ -1710,8 +1736,8 @@ sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryType: 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: 10 seconds + * Dimension(s): `categoryType`, `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryType @@ -1726,8 +1752,8 @@ sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken: named `category` with a value of "counter", "cumulative_counter", or "gauge". To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `categoryType`, `orgId`, `tokenId` - * Data resolution: 10 seconds + * Dimension(s): `categoryType`, `orgId`, `tokenId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken @@ -1757,7 +1783,7 @@ sf.org.numLogsReceivedByToken: description: | Number of logs received by token. - * Dimension(s): `orgId, tokenId` + * Dimension(s): `orgId`, `tokenId` * Data resolution: 10 seconds metric_type: counter title: sf.org.numLogsReceivedByToken @@ -1806,8 +1832,8 @@ sf.org.numMetricTimeSeriesCreated: 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): `category`, `orgId` - * Data resolution: 5 seconds + * Dimension(s): `category`, `orgId` + * Data resolution: 5 seconds metric_type: counter title: sf.org.numMetricTimeSeriesCreated @@ -1822,8 +1848,8 @@ sf.org.numMetricTimeSeriesCreatedByToken: The sum of all the values might be less than the value of `sf.org.numMetricTimeSeriesCreated`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `category`, `orgId`, `tokenId` - * Data resolution: 5 seconds + * Dimension(s): `category`, `orgId`, `tokenId` + * Data resolution: 5 seconds metric_type: counter title: sf.org.numMetricTimeSeriesCreatedByToken @@ -1832,8 +1858,8 @@ sf.org.numMetricObjectsCreatedByToken: description: | Number of metric objects created by token. - * Dimension(s): `tokenId`, `orgId` - * Data resolution: 40 seconds + * Dimension(s): `tokenId`, `orgId` + * Data resolution: 40 seconds metric_type: gauge title: sf.org.numMetricObjectsCreatedByToken @@ -1854,7 +1880,7 @@ sf.org.numNewDimensionsByName: created) are included, in addition to dimension name `sf_metric`, which is always included. - * Data resolution: 5 minutes + * Data resolution: 5 minutes metric_type: counter title: sf.org.numNewDimensionsByName @@ -1863,8 +1889,8 @@ sf.org.numProcessDataEventsDroppedThrottleByToken: description: | Per token, number of data ingest process events dropped due to throttling, because you exceeded your system limits. - * Dimension(s): `orgId, tokenIn` - * Data resolution: 40 seconds + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 40 seconds metric_type: counter title: sf.org.numProcessDataEventsDroppedThrottleByToken @@ -1874,8 +1900,8 @@ sf.org.numPropertyLimitedMetricTimeSeriesCreateCalls: Number of metric time series (MTS) Infrastructure Monitoring was unable to create because you reached your maximum number of unique dimension names. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numPropertyLimitedMetricTimeSeriesCreateCalls @@ -1888,8 +1914,8 @@ sf.org.numPropertyLimitedMetricTimeSeriesCreateCallsByToken: The sum of all the values might be less than the value of `sf.org.numPropertyLimitedMetricTimeSeriesCreateCalls`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numPropertyLimitedMetricTimeSeriesCreateCallsByToken @@ -1901,8 +1927,8 @@ sf.org.numResourceMetrics: The `resourceType` dimension indicates whether the value represents hosts or containers. - * Dimension(s): `orgId`, `resourceType` - * Data resolution: 10 minutes + * Dimension(s): `orgId`, `resourceType` + * Data resolution: 10 minutes metric_type: gauge title: sf.org.numResourceMetrics @@ -1913,8 +1939,8 @@ sf.org.numResourceMetricsbyToken: The `resourceType` dimension indicates whether the value represents hosts or containers. - * Dimension(s): `orgId`, `resourceType`, `tokenId` - * Data resolution: 10 minutes + * Dimension(s): `orgId`, `resourceType`, `tokenId` + * Data resolution: 10 minutes metric_type: gauge title: sf.org.numResourceMetricsbyToken @@ -1924,8 +1950,8 @@ sf.org.numResourcesMonitored: Number of hosts or containers that Infrastructure Monitoring is currently monitoring. The `resourceType` dimension indicates whether the value represents hosts or containers. - * Dimension(s): `orgId`, `resourceType` - * Data resolution: 10 minutes + * Dimension(s): `orgId`, `resourceType` + * Data resolution: 10 minutes metric_type: counter title: sf.org.numResourcesMonitored @@ -1938,8 +1964,8 @@ sf.org.numResourcesMonitoredByToken: The sum of all the values might be less than the value of `sf.org.numResourcesMonitored`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId`, `resourceType`, tokenId` - * Data resolution: 10 minutes + * Dimension(s): `orgId`, `resourceType`, tokenId` + * Data resolution: 10 minutes metric_type: counter title: sf.org.numResourcesMonitoredByToken @@ -1948,8 +1974,8 @@ sf.org.numRestCalls: description: | Number of REST calls made to the Infrastructure Monitoring API. - * Dimension(s): `orgId` - * Data resolution: 1 second" + * Dimension(s): `orgId` + * Data resolution: 1 second" metric_type: counter title: sf.org.numRestCalls @@ -1959,8 +1985,8 @@ sf.org.numRestCallsThrottled: Number of REST calls you made to the Infrastructure Monitoring API that were not accepted by Infrastructure Monitoring, because your organization significantly exceeded its per-minute limit. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numRestCallsThrottled @@ -1974,8 +2000,8 @@ sf.org.numRestCallsThrottledByToken: The sum of all the values might be less than the value of `sf.org.numRestCallsThrottled`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numRestCallsThrottledByToken @@ -1986,8 +2012,8 @@ sf.org.numThrottledEventTimeSeriesCreateCalls: Total number of event time series (ETS) that Infrastructure Monitoring was unable to create, because you significantly exceeded your per-minute event creation limit. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numThrottledEventTimeSeriesCreateCalls @@ -2001,8 +2027,8 @@ sf.org.numThrottledEventTimeSeriesCreateCallsByToken: The sum of all the values might be less than the value of `sf.org.numThrottledEventTimeSeriesCreateCalls`. To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numThrottledEventTimeSeriesCreateCallsByToken @@ -2013,8 +2039,8 @@ sf.org.numThrottledMetricTimeSeriesCreateCalls: Number of metric time series (MTS) that Infrastructure Monitoring was unable to create because you significantly exceeded your per-minute or per-hour MTS creation limit. - * Dimension(s): `orgId` - * Data resolution: 1 second + * Dimension(s): `orgId` + * Data resolution: 1 second metric_type: counter title: sf.org.numThrottledMetricTimeSeriesCreateCalls @@ -2028,8 +2054,8 @@ sf.org.numThrottledMetricTimeSeriesCreateCallsByToken: The sum of all the values might be less than the value of `sf.org.numThrottledMetricTimeSeriesCreateCalls`. To learn more, see [Metrics for values by token](#metrics for values by token). - * Dimension(s): `orgId, tokenId` - * Data resolution: 1 second + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 1 second metric_type: counter title: sf.org.numThrottledMetricTimeSeriesCreateCallsByToken @@ -2037,7 +2063,7 @@ sf.org.numUniqueNamesInNewDimensions: brief: Number of unique dimension names that were created description: | The number of unique dimension names (keys) created in all new dimensions - * Data resolution: 5 minutes + * Data resolution: 5 minutes metric_type: counter title: sf.org.numUniqueNamesInNewDimensions @@ -2048,7 +2074,7 @@ sf.org.subscription.activeTimeSeries: The number of active MTS is the total number of MTS that have received at least one data point within a moving window of the last 25 hours. - * Data resolution: 15 minutes + * Data resolution: 15 minutes metric_type: gauge title: sf.org.subscription.activeTimeSeries @@ -2058,7 +2084,7 @@ sf.org.subscription.datapointsPerMinute: Maximum number of data points per minute (DPM) that Infrastructure Monitoring will process and store. - * Data resolution: 15 minutes + * Data resolution: 15 minutes metric_type: gauge title: sf.org.subscription.datapointsPerMinute @@ -2068,7 +2094,7 @@ sf.org.subscription.containers: Number of containers included in the subscription. - * Data resolution: 10 seconds + * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.containers @@ -2077,7 +2103,7 @@ sf.org.subscription.customMetrics: description: | Number of custom metric time series (MTS) included in the subscription. - * Data resolution: 10 seconds + * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.customMetrics @@ -2086,7 +2112,7 @@ sf.org.subscription.highResolutionMetrics: description: | Number of high resolution metric time series (MTS) included in the subscription. - * Data resolution: 10 seconds + * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.highResolutionMetrics @@ -2095,7 +2121,7 @@ sf.org.subscription.hosts: description: | Number of hosts included in the subscription. - * Data resolution: 10 seconds + * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.hosts @@ -2104,7 +2130,7 @@ sf.org.subscription.function: description: | Number of serverless functions included in the subscription. - * Data resolution: 10 seconds + * Data resolution: 10 seconds metric_type: gauge title: sf.org.subscription.function @@ -2120,9 +2146,9 @@ sf.org.rum.numSpansReceived: description: | Number of spans received. - * Dimension: orgId - * Data resolution: 10 seconds - metric_type: Counter + * Dimension: `orgId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numSpansReceived sf.org.rum.numSpansReceivedByToken: @@ -2132,9 +2158,9 @@ sf.org.rum.numSpansReceivedByToken: The number of spans Splunk RUM received for a specific access token after filtering and throttling. - * Dimension: orgId, tokenId + * Dimension: `orgId`, `tokenId` * Data resolution: 10 seconds - metric_type: Counter + metric_type: counter title: sf.org.rum.numSpansReceivedByToken @@ -2143,9 +2169,9 @@ sf.org.rum.numAddSpansCalls: description: | The number of calls to the `/v1/rum?auth={AUTH_TOKEN}` endpoint. - * Dimension: orgId - * Data resolution: 10 seconds - metric_type: Counter + * Dimension: `orgId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numAddSpansCalls sf.org.rum.numAddSpansCallsByToken: @@ -2153,9 +2179,9 @@ sf.org.rum.numAddSpansCallsByToken: description: | The number of calls to the `/v1/rum?auth={AUTH_TOKEN}` endpoint for a specific access token. - * Dimension: orgId, tokenId - * Data resolution: 10 seconds - metric_type: Counter + * Dimension: `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numAddSpansCalls sf.org.rum.numSpansDroppedInvalid: @@ -2163,9 +2189,9 @@ sf.org.rum.numSpansDroppedInvalid: description: | Number of spans dropped because they were invalid. Some of the reasons that spans are invalid are: spans are too large, missing required tags and invalid Trace IDs. Look through the reason column in the data table to see details for specific spans. - * Dimension: orgId, reason, - * Data resolution: 10 seconds - metric_type: Counter + * Dimension: `orgId`, `reason` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numSpansDroppedInvalid sf.org.rum.numSpansDroppedInvalidByToken: @@ -2175,10 +2201,10 @@ sf.org.rum.numSpansDroppedInvalidByToken: The number of invalid spans Splunk RUM receives for a specific access token. Some of the reasons that spans are invalid are: spans are too large, missing required tags and invalid Trace IDs. Look through the reason column in the data table to see details for specific spans. - * Dimensions: orgId, tokenId, reason - * Data resolution: 10 seconds + * Dimensions: `orgId`, `tokenId`, `reason` + * Data resolution: 10 seconds - metric_type: Counter + metric_type: counter title: sf.org.rum.numSpansDroppedInvalidByToken sf.org.rum.numSpansDroppedThrottle: @@ -2186,9 +2212,9 @@ sf.org.rum.numSpansDroppedThrottle: description: | The number of spans Splunk RUM dropped after you exceeded the allowed ingest volume. - * Dimension: orgId - * Data resolution: 10 seconds - metric_type: Counter + * Dimension: `orgId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numSpansDroppedThrottle sf.org.rum.numSpansDroppedThrottleByToken: @@ -2196,9 +2222,9 @@ sf.org.rum.numSpansDroppedThrottleByToken: description: | The number of spans Splunk RUM dropped after you exceeded the allowed ingest volume for a specific access token. - * Dimension: orgId, tokenId - * Data resolution: 10 seconds - metric_type: Counter + * Dimension: `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numSpansDroppedThrottleByToken @@ -2207,9 +2233,9 @@ sf.org.rum.numSpanBytesReceived: description: | The bytes of all the spans accepted and counted by the metric numSpansReceived. - * Dimensions: orgId - * Data resolution: 10 seconds - metric_type: Counter + * Dimensions: `orgId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numSpanBytesReceived sf.org.rum.numSpanBytesReceivedByToken: @@ -2217,9 +2243,9 @@ sf.org.rum.numSpanBytesReceivedByToken: description: | The bytes of all the spans accepted and counted by the metric numSpansReceived by token. - * Dimensions: orgId, tokenId - * Data resolution: 10 seconds - metric_type: Counter + * Dimensions: `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numSpanBytesReceivedByToken @@ -2228,9 +2254,9 @@ sf.org.rum.grossSpanBytesReceivedByToken: description: | The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. - * Dimensions: orgId, tokenId - * Data resolution: 10 seconds - metric_type: Counter + * Dimensions: `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.grossSpanBytesReceivedByToken sf.org.rum.numContentBytesReceived: @@ -2238,9 +2264,9 @@ sf.org.rum.numContentBytesReceived: description: | The volume of bytes Splunk RUM receives after filtering and throttling. - * Dimensions: orgId - * Data resolution: 10 seconds - metric_type: Counter + * Dimensions: `orgId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.numContentBytesReceived sf.org.rum.grossContentBytesReceivedByToken: @@ -2248,9 +2274,9 @@ sf.org.rum.grossContentBytesReceivedByToken: description: | The possibly compressed wire size of the payloads before the payloads are decompressed and decoded by token. - * Dimensions: orgId, tokenId - * Data resolution: 10 seconds - metric_type: Counter + * Dimensions: `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter title: sf.org.rum.grossContentBytesReceivedByToken @@ -2259,8 +2285,8 @@ sf.org.rum.grossContentBytesReceived: description: | The possibly compressed wire size of the payloads before the payloads are decompressed and decoded. - * Dimensions: orgId - * Data resolution: 10 seconds + * Dimensions: `orgId` + * Data resolution: 10 seconds - metric_type: Counter + metric_type: counter title: sf.org.rum.grossContentBytesReceived From 69c119c6dcf1d9485785a3a9dda22650cf7dc722 Mon Sep 17 00:00:00 2001 From: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> Date: Tue, 22 Aug 2023 15:14:54 -0400 Subject: [PATCH 41/48] Merge changes in main to release (#1002) (#1031) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review --------- Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Co-authored-by: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Co-authored-by: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com> From 4bb258c00c7472369ce32595035c9d769eea5dcf Mon Sep 17 00:00:00 2001 From: trangl Date: Tue, 22 Aug 2023 15:43:31 -0400 Subject: [PATCH 42/48] Fix link formatting --- signalfx-org-metrics/metrics.yaml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index beaae29a..42d6cac3 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -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 @@ -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 From ecfc1181cb1b7df79fb7cf9d60014f0d41a721a3 Mon Sep 17 00:00:00 2001 From: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> Date: Tue, 22 Aug 2023 15:51:05 -0400 Subject: [PATCH 43/48] Fix link formatting (#1032) (#1033) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review * Merge changes in main to release (#1002) (#1031) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review --------- * Fix link formatting --------- Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Co-authored-by: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Co-authored-by: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com> From 4845ee1edc9b9434c4ab6750dbcad48ec0184fff Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Tue, 5 Sep 2023 15:26:08 +0200 Subject: [PATCH 44/48] [OD5656]: Remove Azure/GCP deprecated metrics (#1034) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. * OD5656-deprecated-remove * Fix * Fix? * Update metrics.yaml --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> --- signalfx-org-metrics/metrics.yaml | 122 ++++++++---------------------- 1 file changed, 31 insertions(+), 91 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 42d6cac3..fe792590 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -739,44 +739,6 @@ sf.org.num.awsServiceCallThrottles: * Data resolution: 5 seconds metric_type: gauge title: sf.org.num.awsServiceCallThrottles - -sf.org.num.azureMonitorClientCallCount (DEPRECATED): - brief: Number of calls made to the Azure Monitor API - description: | - THIS METRIC IS DEPRECATED AND WILL BE REMOVED. - PLEASE USE `sf.org.num.azureServiceClientCallCount` INSTEAD - Total number of calls made to the Azure Monitor API. - - * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric - syncing and `metric_metadata_sync` for property syncing) - * Data resolution: 5 seconds - metric_type: counter - title: sf.org.num.azureMonitorClientCallCount - -sf.org.num.azureMonitorClientCallCountErrors (DEPRECATED): - brief: Number of calls to Azure Monitor API method that threw errors - description: | - Note: This metric is deprecated. Use `sf.org.num.azureServiceClientCallCountErrors` instead. - Number of calls to Azure Monitor API method that threw errors. - - * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric - syncing and `metric_metadata_sync` for property syncing) - * Data resolution: 1 second - metric_type: counter - title: sf.org.num.azureMonitorClientCallCountErrors - -sf.org.num.azureMonitorClientCallCountThrottles (DEPRECATED): - brief: Number of calls to Azure Monitor method that were throttled - description: | - THIS METRIC IS DEPRECATED AND WILL BE REMOVED. - PLEASE USE `sf.org.num.azureServiceClientCallCountThrottles` INSTEAD - Number of calls to Azure Monitor method that were throttled. - - * Dimension(s): `orgId`, `subscription_id`, `type` (`metric_data_sync` for metric - syncing and `metric_metadata_sync` for property syncing) - * Data resolution: 1 second - metric_type: counter - title: sf.org.num.azureMonitorClientCallCountThrottles sf.org.num.azureServiceClientCallCount: brief: Number of calls made to the Azure API @@ -910,39 +872,6 @@ sf.org.num.eventtype: metric_type: gauge title: sf.org.num.eventtype -sf.org.num.gcpStackdriverClientCallCount (DEPRECATED): - brief: Number of calls to each Stackdriver client method - description: | - Note: This metric is deprecated. Use `sf.org.num.gcpServiceClientCallCount` instead. - Number of calls to each Stackdriver client method. - - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second - metric_type: counter - title: sf.org.num.gcpStackdriverClientCallCount - -sf.org.num.gcpStackdriverClientCallCountErrors (DEPRECATED): - brief: Number of calls to each Stackdriver client method that threw errors - description: | - Note: This metric is deprecated. Use `sf.org.num.gcpServiceClientCallCountErrors` instead. - Number of calls to each Stackdriver client method that threw errors. - - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second - metric_type: counter - title: sf.org.num.gcpStackdriverClientCallCountErrors - -sf.org.num.gcpStackdriverClientCallCountThrottles (DEPRECATED): - brief: Number of calls to each Stackdriver client method that were throttled - description: | - Note: This metric is deprecated. Use `sf.org.num.gcpServiceClientCallCountThrottles` instead. - Number of calls to each Stackdriver client method that were throttled. - - * Dimension(s): `orgId`, `project_id`, `method` (the API being called, such as `getTimeSeries`) - * Data resolution: 1 second - metric_type: counter - title: sf.org.num.gcpStackdriverClientCallCountThrottles - sf.org.num.gcpServiceClientCallCount: brief: Number of calls to each GCP API client method description: | @@ -1249,6 +1178,16 @@ sf.org.numBackfillCallsByToken: * Data resolution: 1 second metric_type: counter title: sf.org.numBackfillCallsByToken + +sf.org.numComputationsStarted: + brief: Rate at which you're starting new jobs + description: | + Number of computations started, use it to know the rate at which you're starting new jobs. + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.numComputationsStarted sf.org.numBadDimensionMetricTimeSeriesCreateCalls: brief: Number of bad calls to create MTS due to an error with dimensions @@ -1396,9 +1335,9 @@ sf.org.numDatapointsDroppedBatchSizeByToken: brief: Number of data points dropped because a single request contained more than 100,000 data points, by token. description: | Number of data points dropped because a single request contained more than 100,000 data points, per token. In this scenario, Observability Cloud drops data points because it perceives sending more than 100,000 data points in a single request as excessive. + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 40 seconds - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 40 seconds metric_type: counter title: sf.org.numDatapointsDroppedBatchSizeByToken @@ -1524,9 +1463,9 @@ sf.org.numDimensionObjectsCreated: brief: Number of dimensions created description: | Total number of dimensions created. - - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: gauge title: sf.org.numDimensionObjectsCreated @@ -1534,9 +1473,9 @@ sf.org.numDimensionObjectsCreatedByToken: brief: Number of dimensions created by token description: | Total number of dimensions created by token. - * Dimension(s): `orgId`, `tokenId` * Data resolution: 40 seconds + metric_type: gauge title: sf.org.numDimensionObjectsCreatedByToken @@ -1544,9 +1483,9 @@ sf.org.numEventSearches: brief: Number of event searches description: | Number of event searches. - * Dimension(s): `orgId` * Data resolution: 10 seconds + metric_type: counter title: sf.org.numEventSearches @@ -1554,9 +1493,9 @@ sf.org.numEventSearchesThrottled: brief: Number of event searches that were throttled description: | Number of event searches that were throttled. - * Dimension(s): `orgId` * Data resolution: 10 seconds + metric_type: counter title: sf.org.numEventSearchesThrottled @@ -1648,9 +1587,9 @@ sf.org.numHostMetaDataEventsDroppedThrottle: brief: Number of host metadata events dropped due to throttling description: | Number of host metadata events dropped because of throttling. + * Dimension(s): `orgId` + * Data resolution: 40 seconds - * Dimension(s): `orgId` - * Data resolution: 40 seconds metric_type: counter title: sf.org.numHostMetaDataEventsDroppedThrottle @@ -1658,9 +1597,9 @@ sf.org.numHostMetaDataEventsDroppedThrottleByToken: brief: Number of host metadata events dropped due to throttling by token description: | Number of host metadata events dropped because of throttling, per token. - * Dimension(s): `orgId`, `tokenId` * Data resolution: 40 seconds + metric_type: counter title: sf.org.numHostMetaDataEventsDroppedThrottleByToken @@ -1781,9 +1720,9 @@ sf.org.numLogsReceivedByToken: brief: Number of logs received by token description: | Number of logs received by token. - - * Dimension(s): `orgId`, `tokenId` + * Dimension(s): `orgId, tokenId` * Data resolution: 10 seconds + metric_type: counter title: sf.org.numLogsReceivedByToken @@ -1856,9 +1795,9 @@ sf.org.numMetricObjectsCreatedByToken: brief: Number of metric objects created by token description: | Number of metric objects created by token. - * Dimension(s): `tokenId`, `orgId` * Data resolution: 40 seconds + metric_type: gauge title: sf.org.numMetricObjectsCreatedByToken @@ -1866,8 +1805,8 @@ sf.org.numNewDimensions: brief: Number of new dimensions that were created description: | The number of new dimensions (key:value pairs) created. - * Data resolution: 5 minutes + metric_type: counter title: sf.org.numNewDimensions @@ -1878,8 +1817,8 @@ sf.org.numNewDimensionsByName: (key from key:value pair). Only the top 100 dimension names (by number of dimensions created) are included, in addition to dimension name `sf_metric`, which is always included. - * Data resolution: 5 minutes + metric_type: counter title: sf.org.numNewDimensionsByName @@ -1887,9 +1826,9 @@ sf.org.numProcessDataEventsDroppedThrottleByToken: brief: Number of data ingest process events dropped due to throttling by token description: | Per token, number of data ingest process events dropped due to throttling, because you exceeded your system limits. + * Dimension(s): `orgId, tokenIn` + * Data resolution: 40 seconds - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 40 seconds metric_type: counter title: sf.org.numProcessDataEventsDroppedThrottleByToken @@ -1938,8 +1877,9 @@ sf.org.numResourceMetricsbyToken: The `resourceType` dimension indicates whether the value represents hosts or containers. - * Dimension(s): `orgId`, `resourceType`, `tokenId` - * Data resolution: 10 minutes + * Dimension(s): `orgId`, `resourceType`, `tokenId` + * Data resolution: 10 minutes + metric_type: gauge title: sf.org.numResourceMetricsbyToken From 871124a9ffb488e4a92e696ed3f848babce46422 Mon Sep 17 00:00:00 2001 From: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Date: Fri, 8 Sep 2023 16:57:46 -0500 Subject: [PATCH 45/48] Remove duplicate metric (#1035) sf.org.numComputationsStarted had two entries. Fixes the table by removing the first entry. --- signalfx-org-metrics/metrics.yaml | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index fe792590..7a029f2f 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1178,16 +1178,6 @@ sf.org.numBackfillCallsByToken: * Data resolution: 1 second metric_type: counter title: sf.org.numBackfillCallsByToken - -sf.org.numComputationsStarted: - brief: Rate at which you're starting new jobs - description: | - Number of computations started, use it to know the rate at which you're starting new jobs. - - * Dimension(s): `orgId` - * Data resolution: 10 seconds - metric_type: counter - title: sf.org.numComputationsStarted sf.org.numBadDimensionMetricTimeSeriesCreateCalls: brief: Number of bad calls to create MTS due to an error with dimensions From b6fed5ab7c92a6cce712708f72fe9fbdecf59425 Mon Sep 17 00:00:00 2001 From: trangl Date: Mon, 18 Sep 2023 15:00:03 -0400 Subject: [PATCH 46/48] Fix indentations for formatting --- signalfx-org-metrics/metrics.yaml | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index 7a029f2f..e99f0ca8 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1453,8 +1453,8 @@ sf.org.numDimensionObjectsCreated: brief: Number of dimensions created description: | Total number of dimensions created. - * Dimension(s): `orgId` - * Data resolution: 10 seconds + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: gauge title: sf.org.numDimensionObjectsCreated @@ -1577,8 +1577,8 @@ sf.org.numHostMetaDataEventsDroppedThrottle: brief: Number of host metadata events dropped due to throttling description: | Number of host metadata events dropped because of throttling. - * Dimension(s): `orgId` - * Data resolution: 40 seconds + * Dimension(s): `orgId` + * Data resolution: 40 seconds metric_type: counter title: sf.org.numHostMetaDataEventsDroppedThrottle @@ -1648,8 +1648,8 @@ sf.org.numLimitedMetricTimeSeriesCreateCalls: description: | Number of metric time series (MTS) not created because your account reached a category limit (or subscription limit). - * Dimension(s): `category`, `orgId` - * Data resolution: 10 seconds + * Dimension(s): `category`, `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numLimitedMetricTimeSeriesCreateCalls @@ -2179,14 +2179,14 @@ sf.org.rum.numSpanBytesReceivedByToken: sf.org.rum.grossSpanBytesReceivedByToken: - brief: The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. - description: | - The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. - - * Dimensions: `orgId`, `tokenId` - * Data resolution: 10 seconds - metric_type: counter - title: sf.org.rum.grossSpanBytesReceivedByToken + brief: The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. + description: | + The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. + + * Dimensions: `orgId`, `tokenId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.rum.grossSpanBytesReceivedByToken sf.org.rum.numContentBytesReceived: brief: The volume of bytes Splunk RUM receives after filtering and throttling. From f0073bab544d2221a63e270088f43434301cd4b4 Mon Sep 17 00:00:00 2001 From: trangl Date: Mon, 18 Sep 2023 15:04:30 -0400 Subject: [PATCH 47/48] Fix typos --- signalfx-org-metrics/metrics.yaml | 34 +++++++++++++++---------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index e99f0ca8..7915a629 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -510,7 +510,7 @@ sf.org.log.grossContentBytesReceived: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire before filtering and throttling. This content can be compressed. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.grossContentBytesReceived @@ -520,7 +520,7 @@ sf.org.log.grossContentBytesReceivedByToken: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.grossContentBytesReceivedByToken @@ -530,7 +530,7 @@ sf.org.log.grossMessageBytesReceived: The number of bytes Splunk Log Observer receives from ingested logs after decompression but before filtering and throttling are complete. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.grossMessageBytesReceived @@ -540,7 +540,7 @@ sf.org.log.grossMessageBytesReceivedByToken: The number of bytes received by Splunk Log Observer for a specific access token from ingested logs after decompression but before filtering and throttling are complete. * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.grossMessageBytesReceivedByToken @@ -550,7 +550,7 @@ sf.org.log.grossMessagesReceived: The total number of log messages Splunk Log Observer receives before filtering and throttling. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.grossMessagesReceived @@ -560,7 +560,7 @@ sf.org.log.grossMessagesReceivedByToken: The total number of log messages Splunk Log Observer receives for a specific access token before filtering and throttling. * Dimension(s): `orgId`, `tokenId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.grossMessagesReceivedByToken @@ -570,7 +570,7 @@ sf.org.log.numContentBytesReceived: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire after filtering and throttling. This content can be compressed. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numContentBytesReceived @@ -580,7 +580,7 @@ sf.org.log.numContentBytesReceivedByToken: The volume of bytes Splunk Log Observer receives from ingesting logs off the wire for a specific access token after filtering and throttling. This content can be compressed. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numContentBytesReceivedByToken @@ -590,7 +590,7 @@ sf.org.log.numLogsDroppedIndexThrottle: The number of logs Splunk Log Observer drops after the organization's allowed logs index limit threshold is met. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numLogsDroppedIndexThrottle @@ -600,7 +600,7 @@ sf.org.log.numMessageBytesReceived: The number of bytes Splunk Log Observer receives from ingested logs after decompression, filtering, and throttling are complete. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessageBytesReceived @@ -610,7 +610,7 @@ sf.org.log.numMessageBytesReceivedByToken: The number of bytes Splunk Log Observer receives for a specific access token from ingested logs after decompression, filtering, and throttling are complete. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessageBytesReceivedByToken @@ -620,7 +620,7 @@ sf.org.log.numMessagesDroppedThrottle: The number of log messages Splunk Log Observer drops after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessagesDroppedThrottle @@ -630,7 +630,7 @@ sf.org.log.numMessagesDroppedOversize: The number of log messages Splunk Log Observer receives that are too large to process. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessagesDroppedOversize @@ -640,7 +640,7 @@ sf.org.log.numMessagesDroppedOversizeByToken: The number of log messages Splunk Log Observer receives that are too large to process for a specific access token. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessagesDroppedOversizeByToken @@ -650,7 +650,7 @@ sf.org.log.numMessagesDroppedThrottleByToken: The number of log messages Splunk Log Observer drops for a specific access token after the allowed ingest volume is exceeded. Splunk Log Observer drops messages it receives after the ingestion volume is reached. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessagesDroppedThrottleByToken @@ -660,7 +660,7 @@ sf.org.log.numMessagesReceived: The total number of log messages Splunk Log Observer accepts after filtering and throttling. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessagesReceived @@ -670,7 +670,7 @@ sf.org.log.numMessagesReceivedByToken: The total number of log messages Splunk Log Observer accepts for a specific access token after filtering and throttling. * Dimension(s): `orgId` - * Data resolution: 10 second + * Data resolution: 10 seconds metric_type: counter title: sf.org.log.numMessagesReceivedByToken From 7448df4548dee1601ec2e67d8440aeceb6e2d9e6 Mon Sep 17 00:00:00 2001 From: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> Date: Mon, 18 Sep 2023 15:07:29 -0400 Subject: [PATCH 48/48] Release (#1037) * Fix link formatting (#1032) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review * Merge changes in main to release (#1002) (#1031) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review --------- Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Co-authored-by: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Co-authored-by: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com> * Fix link formatting --------- Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Co-authored-by: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Co-authored-by: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com> * Update release (#1036) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: trangl-splunk <80287142+trangl-splunk@users.noreply.github.com> * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review * Merge changes in main to release (#1002) (#1031) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review --------- Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Co-authored-by: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Co-authored-by: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com> * Fix link formatting * Fix link formatting (#1032) (#1033) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review * Merge changes in main to release (#1002) (#1031) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * DOCS-1552: Update documentation of IMM Metrics (#971) * Update metrics.yaml * Add two metrics to metrics.yaml * Update sf.org.numResourceMetrics * Update descriptions of new metrics * Update sf.org.subscription.function description * Add subscription details to new metrics * Update from Joe suggestions * Changes to metrics.yaml * Update docs for v5.23.0 (#974) SignalFx Smart Agent release v5.23.0 contained multiple documentation changes. This commit updates integration docs to match changes. * Mfoulds doc4443 (#976) * added space before brief * Update metrics.yaml (#975) * added spaces to line 374 to fix build error(?) * DOCS-4504: Fix YAML file (#978) Fix formatting problems in signalfx-org-metrics/metrics.yaml * Update metrics.yaml (#980) * fixed typos (#982) * merge jmalin-docs-4360-no-MTS-definition changes from master to release (#973) (#985) * DOCS-3971 Switch descriptions for metrics (#966) * DOCS-3971: Switch descriptions for metrics Doc feedback given in this JIRA ticket: https://signalfuse.atlassian.net/browse/DOCS-3971 * Added period * updated data resolution fields for swapped metrics * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken (#967) * Add entry for numLimitedMetricTimeSeriesCreateCallsByCategoryTypeByToken * Use MD not RST syntax * DOCS-2113: Document subscription metrics (#968) * Add host-based limit metrics to metrics.yaml * Update metrics.yaml * Revert "DOCS-2113: Document subscription metrics (#968)" (#969) This reverts commit bee12adf906483f35795288da69ccd09c483425b. * Update metrics.yaml (#970) * Jmalin docs4360 no mts definition (#972) * DOC-4360: Add MTS definitions Add definitions of active and inactive MTS. * DOCS-4360: Edit and cleanup * [DOCS-2512] Org metrics redux (#991) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * DRAFT [DOCS-4678] - Org metrics batch A (#992) * [DOCS-4678] - Org metrics batch A See jira. * More updates, WIP * Final updates to Batch A * update docs with splunk.com links (#996) * update docs with splunk.com links * lowercase observability * remove CircleCI, use github actions (#995) * Code review changes from #995 (#997) * code review * Update .github/workflows/test.yml * rename to build-and-test * add sf.org.numDatapointsDroppedInvalidByToken metric (#983) * add sf.org.numDatapointsDroppedInvalidByToken metric * ByToken metric updates * Revert "add sf.org.numDatapointsDroppedInvalidByToken metric (#983)" (#998) This reverts commit 8330ce38f9ce0b4c39b22f6765ebdbf5c12bf72f. * DOCS-4464: add RUM org metrics (#993) * RUM metrics draft * additions * fixes * chages * fix endpoint * reason decripion * revisions * small fix * Remove typo * remove blank spaces * revisions * add sf.org.numDatapointsDroppedInvalidByToken (#999) * Revert "add sf.org.numDatapointsDroppedInvalidByToken (#999)" (#1003) This reverts commit 9102b6dc421eb09ebc373d2f64c33599f72e802d. * DOC-4606 feedback missing metric (#1004) * add sf.org.numDatapointsDroppedInvalidByToken * add metric with proper indentation * add metric sf.org.log.numMessagesReceivedByToken (#1001) * Removing old metrics (#1006) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Org metrics update (#1008) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * [DOCS-4776]: AWS org metrics (#994) * DOCS-4776 New org metrics for AWS * WIP, added info * Final definitions * Org Metrics updates. (#1012) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) --------- * Merging changes in master (#1014) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) --------- * [DOCS-4679]: Adding more Org metrics (#1009) * [DOCS-4679]: Adding more Org metrics * Added bad calls * Final metrics from batch * Add new Azure metrics and deprecate old ones (#1015) * add sf.org.log.numLogsDroppedIndexThrottle (#1016) * OD4680 More Org metrics (#1022) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml --------- * Org metrics update - batch D (#1024) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch --------- * Removing Reserved note in Org metrics (#1026) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. --------- * Update metrics.yaml (#1027) * OD3972-dpm-faqs (#1028) See jira for more details. * update java lib (#1018) * Add missing org metrics per feedback (#1029) * Formatting * Change to fix build failure * Clarify SignalFlow jobs * Eng review --------- * Fix link formatting --------- Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Co-authored-by: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Co-authored-by: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com> * [OD5656]: Remove Azure/GCP deprecated metrics (#1034) * DOCS-2512: Org metrics updates (#989) * DOCS-2512: Org metrics updates * Added minimum to def * Added two more metrics * sf.org.datapointsTotalCountByToken * Typo * sf.org.grossDpmContentBytesReceived * Arranged alphabetically * sf.org.log.grossContentBytesReceived WIP * Finalizing batch, reordering lohs * Updates * Revert "DOCS-2512: Org metrics updates (#989)" (#990) This reverts commit 239a202ef7a9a33a5d0c5df7466f785bdaea3f5e. * Removed old metrics (#1005) See https://signalfuse.atlassian.net/browse/DOCS-5040. * Updating Org metrics (#1007) * Putting updated metrics back See DOCS-5040. * Removed dimension * Add new GCP metrics and deprecate old ones (#1010) sf.org.num.gcpStackdriverClientCallCount* are being deprecated and will be removed. Those are being replaced with sf.org.num.gcpServiceClientCallCount* metrics that present more accurate data. * DOCS-5114-removing-metrics (#1011) * DOCS-5114-fix (#1013) * Update metrics - 4680 - batch C.yaml (#1021) * Update metrics - 4680 - batch C.yaml * Update metrics.yaml WIP * Update metrics.yaml * Update metrics - batch D.yaml (#1023) * Update metrics - batch D.yaml * Update metrics.yaml * Final metrics from batch * OD5392-removed-reserved (#1025) Removed "reserved" note. * OD5656-deprecated-remove * Fix * Fix? * Update metrics.yaml --------- Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> * Remove duplicate metric (#1035) sf.org.numComputationsStarted had two entries. Fixes the table by removing the first entry. * Fix indentations for formatting * Fix typos --------- Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Co-authored-by: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Co-authored-by: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com> --------- Co-authored-by: mbechtold-splunk <107698185+mbechtold-splunk@users.noreply.github.com> Co-authored-by: bhillmer <86490494+bhillmer@users.noreply.github.com> Co-authored-by: Joe Malin Co-authored-by: Curtis Robert <92119472+crobert-1@users.noreply.github.com> Co-authored-by: mfoulds-splunk <111084375+mfoulds-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Co-authored-by: Antoine Toulme Co-authored-by: gschatz-splunk <69330797+gschatz-splunk@users.noreply.github.com> Co-authored-by: Tracey <57269043+tcarter-splunk@users.noreply.github.com> Co-authored-by: akonarska <86464734+akonarska@users.noreply.github.com> Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com>