azure-data-explorer-datasource should be categorized as logging

[yong-cha]

Azure data explorer datasource does not have category and falls under other category limiting ADX's usage for traces to logs. ADX should be categorized as logging.
https://github.com/grafana/grafana/blob/main/public/app/plugins/datasource/elasticsearch/plugin.json#L5

[kayodeprinceMS]

@yong-cha can you share more the user scenario to be supported here? The end goal is not simply to categorize ADX as logging but to be able to link from Trace datasources such (Jaeger, Tempo) to ADX logs automatically by configuring the Trace datasource settings to point to ADX.

[yong-cha]

We use ADX as our logging source and when we try to add traces to logs feature from Jaeger plugin, ADX does not show up as an traces to logs datasource because ADX is not tagged under logging category. As @kayodeprinceMS has mentioned, we would like to have ability to use ADX for traces to logs feature from tracing plugins such as Jaeger, Tempo.

[kayodeprinceMS]

Had a quick chat with @aangelisc on this, there is likely more work to enable this scenario in addition to ADX plugin having the Logging category label.

cc: @taleena for visibility

[aangelisc]

To add detail, the category does not determine if a datasource can be used with traces to logs functionality. This support has to be explicitly added in code and abstractQuery support also needs to be added.

[aangelisc]

@yong-cha have you taken a look at Grafana Correlations? This may be a solution for your use-case.

[taleena]

Closing this discussion. If there are more questions or desires for further investigation here, please open an issue (we're moving away from using discussions as much).