[exporter/pulsar] Make pulsarexporter configuration more configurable

[dao-jun]

Component(s)

exporter/pulsar

Is your feature request related to a problem? Please describe.

Currently, in pulsar_exporter, configuration items only supports specify a single topic name for traces/metrics/logs.

And traces/metrics/logs exporter has default topic name(otlp_spans for traces, otlp_logs for logs and otlp_metrics for metrics), say, if users specify a topic for traces, but couldn't specify topic for logs and metrics. If users want to start a metrics exporter pipeline, it will be failed, because otlp_spans otlp_logs and otlp_metrics is not pulsar topic name pattern.

A topic name pattern must comply with a certain patter(pulsar://tenant/namespace/topic_name, example: pulsar://public/default/otlp_spans).

Also, pulsar_exporter only provide a single encoding configuration for logs,traces and metrics. Say, users want to use jaeger_proto for traces, but it couldn't apply to metrics and logs.

In this conditions, users have to config as below:

exporters:
  pulsar/trace:
    encoding: jaeger_json
    topic: pulsar://public/default/otlp_spans
    #ignore other items...

  pulsar/log:
    encoding: otlp_proto
    topic: pulsar://public/default/otlp_logs
    #ignore other items...

  pulsar/metric:
    encoding: otlp_proto
    topic: pulsar://public/default/otlp_metrics
    #ignore other items...

service:
  pipeline:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [pulsar/trace]

    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [pulsar/log]

    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [pulsar/metric]

This is relatively complex, so I hope to make pulsar_exporter more configurable.

Describe the solution you'd like

Provide extra configuration items:

trace:
  topic:
  encoding:
log:
  topic:
  encoding:
metric:
  topic:
  encoding:

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners for exporter/pulsar: @dmitryax @dao-jun. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• exporter/pulsar: @dmitryax @dao-jun

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.