Adding new Metrics Volume Management Doc #21935
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added related assets / unqueried metrics sections
Adding images for team filter, unqueried features
* Create volume_management page for Metris * Update volume_management * Update volume_management Added related assets / unqueried metrics sections * Create volume * Delete static/images/metrics/volume * Create Test * Add files via upload Adding images for team filter, unqueried features * Update volume_management * Documentation editorial review suggestions * Fix links * Apply suggestions from code review * Add Volume to left nav --------- Co-authored-by: Kathy L <[email protected]>
Preview links (active after the
|
Adding new Est CM usage graphs / ingestde sort column
Slowly iterating here
Updated structure
estherk15
approved these changes
Jul 31, 2024
Comment on lines
+26
to
+32
| - What is my overall account's realtime estimated Indexed Custom Metrics usage? | ||
| - What is my overall account's realtime estimated Ingested Custom Metrics usage? | ||
| - What are the Top 500 largest Metrics without Limits configured metric names by Ingested Custom Metrics volume? | ||
| - What are the Top 500 largest metric names by Indexed Custom Metrics volume? | ||
| - What are the Top 500 spiking cardinality metric names? | ||
| - Which team owns these Top 500 metric names and is responsible for optimizing? | ||
| - Which metrics are actually valuable (or not) to my organization? |
There was a problem hiding this comment.
Suggested change
| - What is my overall account's realtime estimated Indexed Custom Metrics usage? | |
| - What is my overall account's realtime estimated Ingested Custom Metrics usage? | |
| - What are the Top 500 largest Metrics without Limits configured metric names by Ingested Custom Metrics volume? | |
| - What are the Top 500 largest metric names by Indexed Custom Metrics volume? | |
| - What are the Top 500 spiking cardinality metric names? | |
| - Which team owns these Top 500 metric names and is responsible for optimizing? | |
| - Which metrics are actually valuable (or not) to my organization? | |
| - Your account's estimated Indexed Custom Metrics usage and Ingested Custom Metrics usage | |
| - The Top 500 largest Metrics without Limits™ configured metric names by Ingested Custom Metrics volume | |
| - The Top 500 largest metric names by Indexed Custom Metrics volume | |
| - The Top 500 spiking cardinality metric names | |
| - The team that owns and is responsible for optimizing metric names | |
| - The metrics that are or are not valuable to your organization |
There was a problem hiding this comment.
After reading the whole page, I'm not sure we need this section. Your headers are very clear in what a reader can expect to gain from the Metrics Volume, and adding this puts more friction for a user to scroll through. Let me know what you think
There was a problem hiding this comment.
Yeah agreed it adds a lot of overhead but we should assume that folks don't have patience to scroll vertically to read through the docs' headers -- an overview bulleted section of questions they can answer with this doc is present in other dd docs like logs' docs and other external docs too. Let's keep it
Comment on lines
+28
to
+30
| - What are the Top 500 largest Metrics without Limits configured metric names by Ingested Custom Metrics volume? | ||
| - What are the Top 500 largest metric names by Indexed Custom Metrics volume? | ||
| - What are the Top 500 spiking cardinality metric names? |
There was a problem hiding this comment.
Is there a way to group these into one sentence? A short list of bullet points is easier to digest.
Suggested change
| - What are the Top 500 largest Metrics without Limits configured metric names by Ingested Custom Metrics volume? | |
| - What are the Top 500 largest metric names by Indexed Custom Metrics volume? | |
| - What are the Top 500 spiking cardinality metric names? | |
| - The largest metrics grouped by Indexed and Ingested Custom Metrics | |
| - The Top 500 spiking cardinality metric names |
There was a problem hiding this comment.
Can we preserve it as 3 different questions? here's why:
- Was hopeful we can keep this summary section framed as questions that customers would ask. And wanted to follow the example external docs' (see gdoc for governance guide) where they call out each individual functionality to emphasize the huge value the tool brings. Even if people gloss over the summary section, they'll at least see numerically that the page offers a lot.
- Think it still makes sense to keep as separate bullets here because indexed vs ingested are separate SKUs.
- conceptually my top 500 largest metric names by indexed volume are likely a different group of metrics and require a different user action to access than the top 500 spiking metric names.
Co-authored-by: Esther Kim <[email protected]>
Co-authored-by: Esther Kim <[email protected]>
Co-authored-by: Esther Kim <[email protected]>
Co-authored-by: Esther Kim <[email protected]>
Co-authored-by: Esther Kim <[email protected]>
Co-authored-by: Esther Kim <[email protected]>
Co-authored-by: Esther Kim <[email protected]>
rtrieu
pushed a commit
that referenced
this pull request
Sep 3, 2024
* Create volume_management page for Metris * Update volume_management * Update volume_management Added related assets / unqueried metrics sections * Create volume * Delete static/images/metrics/volume * Create Test * Add files via upload Adding images for team filter, unqueried features * Update volume_management * Documentation editorial review (#22185) * Create volume_management page for Metris * Update volume_management * Update volume_management Added related assets / unqueried metrics sections * Create volume * Delete static/images/metrics/volume * Create Test * Add files via upload Adding images for team filter, unqueried features * Update volume_management * Documentation editorial review suggestions * Fix links * Apply suggestions from code review * Add Volume to left nav --------- Co-authored-by: Kathy L <[email protected]> * Re-review of the overview * Fix links for change alert monitor reference * Update volume.md Adding new Est CM usage graphs / ingestde sort column * Add files via upload * Update volume.md Slowly iterating here * Update volume.md Updated structure * Update volume.md * Update content/en/metrics/volume.md Co-authored-by: Esther Kim <[email protected]> * Update content/en/metrics/volume.md Co-authored-by: Esther Kim <[email protected]> * Update content/en/metrics/volume.md Co-authored-by: Esther Kim <[email protected]> * Update content/en/metrics/volume.md Co-authored-by: Esther Kim <[email protected]> * Update content/en/metrics/volume.md Co-authored-by: Esther Kim <[email protected]> * Update content/en/metrics/volume.md Co-authored-by: Esther Kim <[email protected]> * Update content/en/metrics/volume.md Co-authored-by: Esther Kim <[email protected]> --------- Co-authored-by: Heston Hoffman <[email protected]> Co-authored-by: Esther Kim <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
A new page describing the functionality of the metrics volume management page
Merge instructions
Additional notes