Background

Loki includes now the option to generate logs using OTEL schema. Now that we have the capability to read logs that use both ViaQ or OTEL schemas. We need to be able to query using OTEL semantics, this includes adjustment on how the LogQL is generated from the filters that come from the UI components selections.

TODO:

UX for schema dropdown

Outcomes

• The logging plugin configuration has a new field called schema that can used to configure which schema to use for querying, the options are:
  • <empty> or <not defined>: Is the default option, if the value is not set it means it can be selected from the frontend side with a new dropdown
  • via-q: Use the current ViaQ semantics, hide the Schema dropdown
  • otel: Use the current OTEL semantics, hide the Schema dropdown
• The logging plugin has a dropdown to select the model to use. This dropdown is only visible if the schema is not defined
• When
  • ViaQ schema is selected or configured:
    • The plugin keeps is current behavior
  • When OTEL schema is selected or configured:
    • All the filters use the OTEL labels
    • The `| json` parsing is removed from the default query as is not needed for OTEL
    • The histogram removes the `| json` as is not needed for OTEL
    • The log entries in the table parse the main message log according to the OTEL semantics