Support converting Grafana dashboards to Kibana

[Alphayeeeet]

Describe the feature:

As stated out above in the title. I would wish for a feature, which allows migrating existing Grafana dashboards into Kibana (or at least the background PromQL aggregations). I'm currently having a difficult time, trying to migrate our existing (mostly Community) Grafana dashboards to Kibana (which we want to use as our All-in-One platform in the future). If only an Import feature for the aggregations would be available, it would make this job so much easier.

Describe a specific use case for the feature:

When attempting to migrate from Grafana or Prometheus in general to Elastic, you would like to convert your existing dashboards. With support for converting the background PromQL Aggregations (while defining the metrics and labels as Elasticsearch fields), Migration could be so much easier.

For example I use the following as an Input...

sum by (tag_pluginKeyAtCreation) (rate(com_atlassian_confluence_metrics_Count{category00="cache",name="removeAll"}[5m]))

... I would like to get a corresponding Kibana aggregation in whatever visualization editor (doesn't matter if Legacy, TSVB, Lens, Vega or anything else).
This could be some sort of migration assistant which converts the query into an aggregation. Even better would be, if there was support for adding an import assistant for Grafana JSON-exports however. But this would be the superior solution, as only generating the aggregation would be enough (without the need to consider any design-templates of Grafana).

Feel happy to discuss under this issue.

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[jsanz]

@Alphayeeeet thank you for opening this issue.

This effort is totally on the team's radar, but, at this point, it is definitely blocked by #174497, and it will take quite a bit to get to a point where we can consider a migration mechanism.

[Alphayeeeet]

@jsanz Thank you for the response. As I could not find a previous issue, I wanted to open one to create room for discussion and track progress on this topic.

As long as a migration mechanism is considered to be implemented in the future, I am more than happy with that. I understand that implementing a complex functionality like this, can be quite time consuming.

[Alphayeeeet]

@jsanz Just for clarification: Could this be a feature for Elastic v9 or is it more likely to get released in a later major version?

Im asking, because in the issue mentioned by you above, there is mentioned, that the api changes are targetted for v9 release.

[jsanz]

It is very unlikely that we will tackle a task like this before 9.0, but I also think that this should not wait for 10.0 since it does not involve a breaking change.

cc. @teresaalvarezsoler @ThomThomson

[ThomThomson]

Yes this won't involve a breaking change! So it doesn't need to get into a major version, it could be released in a minor. That said, this is not on the top of our list.