[FEATURE]Metrics To Logs Dimension Corrections

[YANG-DB]

Is your feature request related to a problem?
When observing a specific OTEL metrics signal, I would like to dive in the specific traces / logs that have the similar dimensions (including the selected time window)

What solution would you like?
During reviewing of the metrics Analytics, the user would like to narrow down to a specific time window for which he can continue investing the behaviour of his system.

The user would need to further select specific dimensions (attributes) that exist on the metrics ( such as serviceName, userAgent, domain) and correlate these dimensions and time window with another type of signals:

The Metrics Semantic Conventions

The following dimensions are present in the Traces / Logs / Metrics signals as defined in the OTEL protocol:

• HTTP: For HTTP client and server metrics.
• RPC: For RPC client and server metrics.
• Database: For SQL and NoSQL client metrics.
• System: For standard system metrics.
• Process: For standard process metrics.
• Runtime Environment: For runtime environment metrics.
• FaaS: For Function as a Service metrics.
• Hardware: For hardware-related metrics.

Using these attributes will allow to correlate the metrics to their correspondents data points.

---

• Logs ( attempt to narrow down the logs index using these filters)

• Traces ( attempt to narrow down the traces index using these filters)

Do you have any additional context?

• https://github.com/opensearch-project/opensearch-catalog/tree/main/docs/schema
• https://opentelemetry.io/docs/specs/otel/metrics/semantic_conventions/
• https://github.com/open-telemetry/semantic-conventions

[YANG-DB]

some initial UX mockup for selecting metrics, selecting attributes and aggregate function and saving to dashboard