New component: RocketMQ Exporter

[CodePrometheus]

The purpose and use-cases of the new component

Similar use cases as other durable messaging system exporters like Kafka and Pulsar. This could help meet teams where they are that want to do custom telemetry processing but only have access to apache-rocketmq.

Example configuration for the component

exporters:
  rocketmq:
    nameserver:
      - 127.0.0.1:9876
    topic: otlp-spans
    group_name: otlp-group
    encoding: otlp_proto
    credentials:
      access_key: accessKey
      secret_key: secretKey
      security_token: token
    namespace: otlp-ns
    tls:
      use_tls: false

Telemetry data types supported

traces, metrics and logs

Code Owner(s)

@CodePrometheus

Sponsor (optional)

No response

Additional context

I'm looking for sponsors, if anyone is interested, please feel free to leave a message, thanks.

[VenuEmmadi]

Hi @CodePrometheus
Yes, adding an Apache RocketMQ exporter to OpenTelemetry is an excellent idea, especially for organizations or teams that already rely on RocketMQ for their message-driven architectures. This addition would provide a seamless way to integrate telemetry data, enabling users to leverage their existing infrastructure for observability purposes. I am interested in taking on this task and would like to contribute to its development.

[CodePrometheus]

Hi @CodePrometheus Yes, adding an Apache RocketMQ exporter to OpenTelemetry is an excellent idea, especially for organizations or teams that already rely on RocketMQ for their message-driven architectures. This addition would provide a seamless way to integrate telemetry data, enabling users to leverage their existing infrastructure for observability purposes. I am interested in taking on this task and would like to contribute to its development.

@VenuEmmadi hello venu, I submit this purpose intending to contribute myself, not to look for contributors, thanks :)

[VenuEmmadi]

@CodePrometheus, let me know if you need help—I’m ready to join you!

[TylerHelmuth]

@CodePrometheus thank you for the component proposal. The process now is to evangelize your idea and try to convince an approver or maintainer to sponsor the component in this repo.

In the meantime, we suggest working on and hosting the component within your own repo. This allows users to get value from the component while the approvers/maintainers decides if they want to take on the work for this repo.