Merge pull request #21485 from newrelic/metric-grouping-issues

Metric grouping issues

Author: PallaviWrite

src/content/docs/new-relic-solutions/solve-common-issues/troubleshooting/metric-grouping-issues.mdx

@@ -74,7 +74,7 @@ If the problem persists, follow the procedures for your agent:
       </td>
 
       <td>
-        Review the information about [what causes metric grouping issues](#what).
+        Review the information about [what causes metric grouping issues](#cause).
       </td>
     </tr>
 
@@ -162,7 +162,7 @@ If the problem persists, follow the procedures for your agent:
 
 You can also edit and create metric normalization rules in the UI. For more details, see [Metric normalization](/docs/new-relic-solutions/new-relic-one/ui-data/metric-normalization-rules).
 
-## Cause
+## Cause [#cause]
 
 Metric grouping issues occur when the granularity of metric names (most often web transaction names) is too fine, resulting in hundreds or thousands of different web transaction names for just a small number of code paths. A few major code paths may generate many different full URL paths to unique documents, articles, or page, etc., and if the unique element of the URL path is included in the transaction name, each of these common paths will have its own unique name.
 
@@ -193,4 +193,4 @@ To monitor and improve your application performance, it's much more useful to kn
 
 This grouping gives you a much better idea of how much time was spent viewing articles, and allows you to easily spot any performance problems related to viewing articles. If these statistics were spread across hundreds or thousands of transactions, detecting trends, regressions, or performance improvements would be extremely difficult.
 
-Each APM agent has distinct ways of detecting controllers and frameworks. Most are automatic, but a few require you to enable or disable options in a [config file](/docs/agents/manage-apm-agents/configuration/configure-agent). You can also follow our recommendations to help [prevent metric grouping issues](#prevent) from occurring.
+Each APM agent has distinct ways of detecting controllers and frameworks. Most are automatic, but a few require you to enable or disable options in a [config file](/docs/agents/manage-apm-agents/configuration/configure-agent). You can also follow our recommendations to help prevent metric grouping issues from occurring.