[exporter/postgres]: Exporter to save OTEL data in postgresql

[destrex271]

Component(s)

No response

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

The problem is simply that it would be great to have a way to export otel data to ParadeDB which is based on PostgreSQL.
Referring to this issue: paradedb/paradedb#1632

Describe the solution you'd like

I'd like to add an exporter for postgres in the repository under the exporters folder.

Describe alternatives you've considered

No response

Additional context

We already support a wide variety of exporters in this repository. Postgres is one of the most used databases and it will be a great addition to add an exporter for it.

[atoulme]

@destrex271 will you be available to maintain this exporter moving forward? Any other folks interested in supporting?

[destrex271]

Yes I'll be glad to maintain this!

[atoulme]

You need a sponsor to move further. See CONTRIBUTING.md.

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

[FelixZY]

I found this issue after asking for this feature on stack overflow: https://stackoverflow.com/questions/79300155/how-can-i-get-data-from-the-opentelemetry-collector-into-postgresql

I think it would be an excellent idea to standardize the storage of telemetry, or at least provide standardized storage options. This makes it easier to add or replace the telemetry consumers for an existing application and reduces vendor lock-in.

New consumers would be able to load previous data and I would not need to worry about compatibility with my previous platform (will this app be able to import Jaeger data!?). Also, the choice of telemetry consumers could be delayed to the end of development rather than being forced from the start. Finally, standardizing storage (especially in a database) could make it easier for applications to access their own logs and metrics, which could in turn be used e.g. to enforce usage quotas etc..

[destrex271]

I found this issue after asking for this feature on stack overflow: https://stackoverflow.com/questions/79300155/how-can-i-get-data-from-the-opentelemetry-collector-into-postgresql

I think it would be an excellent idea to standardize the storage of telemetry, or at least provide standardized storage options. This makes it easier to add or replace the telemetry consumers for an existing application and reduces vendor lock-in.

New consumers would be able to load previous data and I would not need to worry about compatibility with my previous platform (will this app be able to import Jaeger data!?). Also, the choice of telemetry consumers could be delayed to the end of development rather than being forced from the start. Finally, standardizing storage (especially in a database) could make it easier for applications to access their own logs and metrics, which could in turn be used e.g. to enforce usage quotas etc..

Hi we were unable to secure any sponsors for this but we do have an unofficial working poc here https://github.com/destrex271/postgresexporter