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
Is your feature request related to a problem? Please describe.
Customer request to enable Grafana (or more its specifically DB backend) for the metric updates being introduced in v2.0. Currently, the Grafana based metric definitions have fallen behind the yaml based definitions used in CLI/standalone GUI, i.e. https://github.com/AMDResearch/omniperf/tree/2.x/src/omniperf_soc/analysis_configs
If customer tries to use Grafana with new v2.0 output, the reported metrics will be incorrect.
Describe the solution you'd like
Customer is asking we enable Grafana which would mean updating the MongoQL metric definitions for all metrics. This could potentially be time consuming and MongoQL limits the devs we could have working on this
Describe alternatives you've considered
In the past, I've wanted to build the DB backend into the CLI/standalone GUI backend which would essentially eliminate the need to keep maintaining (separate) MongoQL based definitions. A separate discussion needs to be had about if this would be a more timely solution, but it's something to consider.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Customer request to enable Grafana (or more its specifically DB backend) for the metric updates being introduced in v2.0. Currently, the Grafana based metric definitions have fallen behind the yaml based definitions used in CLI/standalone GUI, i.e.
https://github.com/AMDResearch/omniperf/tree/2.x/src/omniperf_soc/analysis_configs
If customer tries to use Grafana with new v2.0 output, the reported metrics will be incorrect.
Describe the solution you'd like
Customer is asking we enable Grafana which would mean updating the MongoQL metric definitions for all metrics. This could potentially be time consuming and MongoQL limits the devs we could have working on this
Describe alternatives you've considered
In the past, I've wanted to build the DB backend into the CLI/standalone GUI backend which would essentially eliminate the need to keep maintaining (separate) MongoQL based definitions. A separate discussion needs to be had about if this would be a more timely solution, but it's something to consider.
The text was updated successfully, but these errors were encountered: