From 75c71aa37985d661ce03c008280a53c67fdfdf36 Mon Sep 17 00:00:00 2001
From: bhillmer <86490494+bhillmer@users.noreply.github.com>
Date: Fri, 30 Aug 2024 11:18:47 -0600
Subject: [PATCH] add deprecation note to spansdroppedoversize (#1062)

---
 signalfx-org-metrics/metrics.yaml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml
index 35d8dec0..153bd688 100644
--- a/signalfx-org-metrics/metrics.yaml
+++ b/signalfx-org-metrics/metrics.yaml
@@ -2157,6 +2157,8 @@ sf.org.rum.numAddSpansCallsByToken:
 sf.org.rum.numSpansDroppedInvalid:
   brief: Number of spans dropped because they were invalid. 
   description: |
+    This metric is deprecated. See `sf.org.apm.numSpansDroppedInvalid` with the `spanTooLarge` dimension.
+    
     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`
@@ -2168,6 +2170,8 @@ sf.org.rum.numSpansDroppedInvalidByToken:
   brief: The number of invalid spans Splunk RUM receives for a specific access
     token.
   description: | 
+    This metric is deprecated. See `sf.org.apm.numSpansDroppedInvalid` with the `spanTooLarge` dimension.
+    
     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.