You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: The current empty state of the Metrics explorer page is still focused around setting up the "old" custom metrics. We need to update it to reflect the new way of configuring metrics from span attributes.
Solution:
(1) If they’re already using performance
Show the explorer page
Remove the banner to set up custom metrics
In the query 3 dot menu - Update “Metric Settings” so it’s not disabled for the out-of-the-box metrics (e.g. span.duration), but leads to the “Configure Metrics” screen with the attribute pre-selected
Remove Modal with beta disclaimer (we would need to update it, it does not feel worth it at this point since there is a warning on the page already about the upcoming API changes)
The text was updated successfully, but these errors were encountered:
First of all, thank you for explaining the issue so thoroughly 🙏 🚀
Here is my feedback:
(1) If they’re already using performance
The Metrics button in the 3 dots menu seems too hidden. How can we make customers more aware of the metrics settings?
(3) First visit to the Metrics page
In my brand-new organization, I was surprised to be immediately presented with a modal upon visiting the metrics page. I don't know why we chose this option, but wouldn't improving the displayed banner behind it be sufficient? -
This question might be irrelevant now since it seems we plan to remove the feature, but I wanted to share this feedback for future reference
ale-cota
changed the title
Figure out new onboarding empty state
Onboarding Updates for Span-based Metrics
Jun 27, 2024
Problem: The current empty state of the Metrics explorer page is still focused around setting up the "old" custom metrics. We need to update it to reflect the new way of configuring metrics from span attributes.
Solution:
(1) If they’re already using performance
(2) If they’re not using performance
(3) First visit to the Metrics page
The text was updated successfully, but these errors were encountered: