Overview

We would like to implement some usability enhancements for developers when using Custom Metrics.

Currently, it's difficult to identify the available metrics. Providing a more discoverable mechanism for the developer would be a nice improvement.

Additionally, when entering a query, there's no way for a user to save it. Thus, if developers have queries which they run more than once, we force them to enter it each time, which is time consuming and frustrating. Enabling a mechanism for the user to save their own queries to be access later would be a nice improvement.

Acceptance criteria:

1. The Monitoring area should be renamed to Observe on both the dev and admin perspectives
2. The Monitoring tab in the topology side panel should also be renamed

The following ACs are associated with the Metrics page in the Monitoring area:

1. As a developer, I want to easily identify all of the possible metrics available to me
   1. Note if the design matches what's available on the admin side, try to share the code
2. As a developer, when in the Monitoring->Metrics page, I want to be able to save a custom query so I can access it quickly later
3. As a developer, when in the Monitoring->Metrics page, I want to easily view any custom queries i've previously saved
4. As a developer, when in the Monitoring->Metrics page, I want to easily run one of my saved custom queries
5. As a developer, when in the Monitoring->Metrics page, I want to easily delete one of my saved custom queries
6. As a developer, when in the Monitoring->Metrics page, I want to easily edit one of my saved custom queries
7. As a dev, if i run a query and then navigate away from the page & return, the query should be persisted. The last run query should be persisted for the session.

Slack channel

#tmp-odc-observability

Epic Exploration

Miro board from epic exploration

Notes

These custom queries should be persisted.