Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit aec9f48

Browse files
Added feedback to separate file
1 parent f1e6395 commit aec9f48

File tree

1 file changed

+1
-72
lines changed

1 file changed

+1
-72
lines changed

apm/span-tags/metricsets.rst

Lines changed: 1 addition & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ MMS are available for the APM components listed in the following table. Each MMS
3434

3535
.. _service-mms:
3636
.. _inferred-service-mms-dimensions:
37-
37+
.. _endpoint-mms:
3838

3939
.. list-table::
4040
:widths: 33 33 33
@@ -128,7 +128,6 @@ A histogram MTS uses the following syntax using SignalFlow:
128128
129129
histogram(metric=<metric_name>[,filter=<filter_dict>][,resolution=<resolution>)
130130
131-
132131
The following table displays example SignalFlow functions:
133132

134133
.. list-table::
@@ -151,76 +150,6 @@ The following table displays example SignalFlow functions:
151150

152151
.. note:: Because an aggregation is applied on histogram(), to display all of the metric sets separately, each dimension needs to be applied as a groupby.
153152

154-
Dimensions
155-
=====================
156-
Each MMS has a set of dimensions you can use to monitor and alert on service performance.
157-
158-
In addition to the following default MMS, you can create custom MMS to deep dive on your MMS. See :ref:`cmms`.
159-
160-
.. _service-mms:
161-
162-
Service dimensions
163-
---------------------------------
164-
165-
* ``sf_environment``
166-
* ``deployment.environment`` - This dimension is only available for histogram MMS.
167-
* ``sf_service``
168-
* ``service.name`` - This dimension is only available for histogram MMS.
169-
* ``sf_error``
170-
171-
.. _inferred-service-mms-dimensions:
172-
173-
Inferred service dimensions
174-
------------------------------
175-
176-
* ``sf_service``
177-
* ``service.name`` - This dimension is only available for histogram MMS.
178-
* ``sf_environment``
179-
* ``deployment.environment`` - This dimension is only available for histogram MMS.
180-
* ``sf_error``
181-
* ``sf.kind``
182-
* ``sf_operation``
183-
* ``sf_httpMethod``
184-
185-
.. _endpoint-mms:
186-
187-
Span dimensions
188-
----------------------------------------------
189-
190-
* ``sf_environment``
191-
* ``deployment.environment`` - This dimension is only available for histogram MMS.
192-
* ``sf_service``
193-
* ``service.name`` - This dimension is only available for histogram MMS.
194-
* ``sf_operation``
195-
* ``sf_kind``
196-
* ``sf_error``
197-
* ``sf_httpMethod``, where relevant
198-
199-
Trace dimensions
200-
---------------------------------
201-
202-
.. note:: Trace dimensions are not supported for custom MMS.
203-
204-
* ``sf_environment``
205-
* ``deployment.environment`` - This dimension is only available for histogram MMS.
206-
* ``sf_service``
207-
* ``service.name`` - This dimension is only available for histogram MMS.
208-
* ``sf_operation``
209-
* ``sf_httpMethod``
210-
* ``sf_error``
211-
212-
Workflow dimensions
213-
---------------------------------
214-
215-
Workflow metrics and dimensions are created by default when you create a Business Workflow.
216-
217-
.. note:: Workflow dimensions are not supported for custom MMS.
218-
219-
* ``sf_environment``
220-
* ``deployment.environment`` - This dimension is only available for histogram MMS.
221-
* ``sf_workflow``
222-
* ``sf_error``
223-
224153
Use MMS within Splunk APM
225154
----------------------------------------
226155

0 commit comments

Comments
 (0)