Skip to content

Add InfluxDB as storage backend to OTel docker service #3

@nicococo

Description

@nicococo

[Service] Add InfluxDB as Storage Backend to OTel

Description

OpenTelemetry (OTel) currently supports several storage backends for metrics and traces. Rn MLOX only uses the limited file backend in our service stack. InfluxDB is a popular time-series database that would provide users with a powerful, scalable, and flexible option for storing observability data.

This issue proposes adding a new OTel Service that support InfluxDB as a storage backend. The implementation should ensure that metrics, traces, logs are correctly exported and stored in InfluxDB. Functionality to receive the stored data should be provided and the UI adapted correspondingly.

Tasks

  • Research the current OTel Collector configuration.
  • Add new service for OTel/InfluxDB: Config files, service class and data access routines, as well as setup and settings UI.
  • Implement and test the OTel Collector pipeline for exporting metrics, logs, traces to InfluxDB.
  • Update documentation to include setup instructions and configuration examples for InfluxDB.
  • Add automated tests to verify correct data export and storage in InfluxDB.

Difficulty

This is a challenging but well-scoped issue, ideal for contributors who want to work on service integrations and observability. It requires knowledge of OpenTelemetry, time-series databases, and service configuration.

Additional Notes

  • Reference: InfluxDB OpenTelemetry Receiver
  • Please ensure compatibility with existing OTel backends and provide migration notes if necessary.
  • Feel free to ask questions or request guidance in the comments!

Good first issue for contributors interested in observability, service integrations, and backend development.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededtype:enhancementImprovements to existing features
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions