New component: YDB Exporter

[gingersamurai]

The purpose and use-cases of the new component

YDB is an open-source Distributed SQL Database that combines high availability and scalability with strong consistency and ACID transactions.

Purpose

The purpose of this exporter is to extract telemetry to YDB.

• YDB is a distributed fault-tolerant database with support for vertical scaling out of the box, which is useful if a service has uneven load.
• YDB is already used as a jaeger storage plugin.

Use cases

• Analyse telemetry via YQL.
• Use Grafana YDB datasource to make dashboards.

Example configuration for the component

exporters:  
  ydb:
    connection:
      dsn: "grpc://localhost:2136/local"
      credentials: 
        anonymous: true
  
service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [ydb]
    metrics:
      receivers: [otlp]
      exporters: [ydb]
    logs:
      receivers: [otlp]
      exporters: [ydb]

Telemetry data types supported

• traces
• metrics
• logs

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)

No response

Additional context

No response

[bryan-aguilar]

Hi @gingersamurai,

Thank you for the new component proposal. If you have not already please make sure you review the new component guidelines.

If you have not found a volunteer sponsor yet then I encourage you to come to our weekly collector sig meetings. You can add an item to the agenda to discuss this new component proposal.

[bryan-aguilar]

As a note, since this is marked as a vendor specific component. Would it be possible to build in an OTLP receiver to YDB instead? I am not familiar with the system, so I recognize there may be a chance that this is not technically feasible. But accepting OTLP directly instead of relying on a collector exporter can be a really great direction also.

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