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
Some indexes for non-OpenTelemetry data have mappings for these attribute namespaces as well, so it's possible that any signal in Discover might have attribute fields.
Designs
Acceptance criteria
Display 3 sections
- {Signal} attributes (where Signal is Log, Span, etc.)
- Resource attributes
- Instrumentation scope attributes
The sections should have title, tooltip and a count (tooltip: TBD)
Accordion sections should be open by default
In each section should be a data table with 2 columns
- Attribute
- Value
Selected/Available/Empty
The attribute names should not display the whole namespace (resource.attributes.telemetry.sdk.language), but only the part of the field name belonging to the given attribute namespace: telemetry.sdk.language.
filtering controls should use the entire field name (T
Don't use pagination for the table
Reuse components from discover (filter controls, data table etc)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Summary
In OpenTelemetry, metadata are represented as Attributes. Elastic stores these attributes in document fields in these namespaces:
Some indexes for non-OpenTelemetry data have mappings for these attribute namespaces as well, so it's possible that any signal in Discover might have attribute fields.
Designs
Acceptance criteria
- {Signal} attributes (where Signal is Log, Span, etc.)
- Resource attributes
- Instrumentation scope attributes
- Attribute
- Value
The text was updated successfully, but these errors were encountered: