New component: eG Innovations Telemetry Exporter

[gsreg]

The purpose and use-cases of the new component

eginnovations exporter enables the ability to export telemetry data from an OpenTelemetry collector to the eG Innovations environment for further analysis, alerting and retention.

Example configuration for the component

WIP

receivers:
  otlp:
    protocols:
      grpc:
      http:

processors:
  batch:
    send_batch_max_size: 100
    send_batch_size: 10
    timeout: 10s

exporters:
    eginnovations:
        endpoint: https://www.eginnovations.com
        userId: "account_specific_generated_id"
        token: "0000000000000000"

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [eginnovations]

Telemetry data types supported

• trace
• metrics [WIP]
• logs [WIP]

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

No response

Sponsor (optional)

This component is being developed and contributed by eG Innovations and is looking for a volunteer sponsor.

Additional context

A version of the OpenTelemetry contrib collector containing the code for this exporter is available here: eginnovations-exporter.

[crobert-1]

Hello @gsreg, thanks for your proposal! Since this is a vendor-specific component a sponsor will be assigned to this component. It looks like @djaglowski is the next rotating sponsor.

[gsreg]

thanks.

[gsreg]

Hello @djaglowski sorry to ping you. Would you be able to be the sponsor for this component?

[djaglowski]

@gsreg I'm quite limited on capacity lately so I would like to get a resolution on #33299 (review) before sponsoring this. In my opinion our policy of auto-assigning sponsors is outdated and needs to be updated, but I'm waiting for more reviews on that PR. In the meantime, even under the proposed rule change your component would be accepted if you are a member of the project so please consider making some contributions and applying for membership.

[djaglowski]

The other maintainers generally seem to support the new rule in #33299 so at this point I will not consider it an obligation to take this on. Again, please consider contributing to the project and applying for membership or always feel free to find a voluntary sponsor.

[crobert-1]

Just to summarize @gsreg, once you become a community member a sponsor will be assigned for this component in case you don't find one in the meantime. The requirements for becoming a community member are here. 👍

[gsreg]

Hi, @crobert-1 & @djaglowski thanks for replying i'll try to follow latest guideline.

[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.

[github-actions]

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