Spike: Figure out architecture to decouple metrics dashboard from environments

Topic to Evaluate

Environments and metrics dashboards are tightly coupled right now. Even if there is no deployment, you need to create a dummy environment before you can view the metrics dashboard. Additionally, the metrics dashboard URL contains the environment ID, which makes the URL longer than necessary.

We want to decouple metrics dashboards from environments, so that metrics dashboards can exist and display data independently of environments.

Created epic: &3859

Tasks to Evaluate

  • How do we handle predefined variables that are dependent on the environment: ci_environment_slug, kube_namespace, ci_environment_name.

    • Can we automatically add variable dropdowns for predefined variables like ci_environment_slug in dashboards that use these variables, since we already know all possible values?

  • Is there any impact on embedded dashboards?

  • Are there any other parts of the product that will get affected by this change?

  • Create issue for implementation with implementation proposal.

  • Set weight on implementation issue.

  • If weight is greater than 5, break issue into smaller issues.

Risks and Implementation Considerations

TBD

Team

Edited by Reuben Pereira