Update synthetics-usage.rst #1730
Open
Conversation
This file contains hidden or 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
Add a reference to the OOTB dashboard that customers can leverage to understand their Synthetics usage.
jcatera-splunk
added
the
stop-alert
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.
Add a reference to the OOTB dashboard that customers can leverage to understand their Synthetics usage.
Requirements
Describe the change
_Enter a description of the changes, why they're good for the Observability Cloud documentation, and so on.
If this contribution is time sensitive, tell us when you'd like this PR to be merged._
The doc today suggests that a customer can only understand their Synthetic usage by creating a custom chart with the provided metric. However, a while ago we added an OOTB dashboard that will begin to populate once a customer has Synthetic tests running. Pointing customers to the OOTB dashboard should lower the barrier to entry for onboarding and adopting. The customer will not know to look for this dashboard, especially if it is not mentioned in Docs.