Add relevant usage migration guide (#23891)

* Add relevant usage migration guide * Address feedback, including adding the new response examples * Fix JSON and make minor wording changes * Small format fixes * Apply suggestions from code review Co-authored-by: Sandra (neko) <165049174+neko-dd@users.noreply.github.com> * replace 'may' with 'might' * remove v2 and v1 from endpoint names to reduce confusion --------- Co-authored-by: Sandra (neko) <165049174+neko-dd@users.noreply.github.com>
DataDog · Jul 1, 2024 · 086b696 · 086b696
1 parent dc9316e
commit 086b696
Show file tree

Hide file tree

Showing 2 changed files with 510 additions and 0 deletions.
diff --git a/content/en/account_management/guide/_index.md b/content/en/account_management/guide/_index.md
@@ -9,6 +9,7 @@ cascade:
 ---
 
 {{< whatsnext desc="Usage metering API migration guides:" >}}
+    {{< nextlink href="account_management/guide/relevant-usage-migration" >}}Migrate Indexed Logs and RUM in the Hourly Usage and Summary Usage APIs{{< /nextlink >}}
     {{< nextlink href="account_management/guide/hourly-usage-migration" >}}Migrating from the v1 Hourly Usage APIs to v2{{< /nextlink >}}
     {{< nextlink href="account_management/guide/usage-attribution-migration" >}}Migrating from v1 to v2 of the Usage Attribution API{{< /nextlink >}}
     {{< nextlink href="account_management/guide/csv-headers-billing-migration" >}}Updates to Plan & Usage CSV Headers as of September 18, 2023{{< /nextlink >}}