Task

1. Review Viaq and OTEL models
2. Produce a list of equivalent fields (JSON paths) between Viaq and OTEL with english documentation strings to describe them.

List should be in a form that is easily parsed for automation later e.g. JSON/YAML.

There's no specific format required.

References

OTEL

• Logs data model: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md
• Logs Resource mappings: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model-appendix.md#appendix-a-example-mappings
• General Semantic Conventions (Resources): https://github.com/open-telemetry/semantic-conventions/README.md
• Kubernetes logs | Vector documentation: https://vector.dev/docs/reference/configuration/sources/kubernetes_logs/

Viaq

• Viaq reference doc (generated)
• Definitions in code:

• Root log event
• Field types

• Samples of log output `logs-*.json`
  • Generate your own: `make logs-application logs-audit logs-infrastructure`

The logging opreator has 3 different styles for wrapping logs:

1. `{ message: "original log message", ... other viaq fields }` # For non-JSON logs, and some JSON logs if parsing is not enabled.
2. `{ structured: { original: { json: object } }, ... other viaq fields }` # For logs that are originally JSON, with parsing enabled.
3. `{ original and viaq fields mixed together }` # For k8s Audit and k8s Event logs, special cases.

Completion criteria

• Documented equivalent paths: ViaQ/OTEL/English description
• Notes on any difficulties or special treatment that might be needed translating between the two.