multi-target and custom queries

[lucian-vanghele]

Component(s)

receiver/oracledb

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

I want to be able to use use custom queries against multiple targets. having hardcoded queries is not the best ideas, sometimes there are differences between oracle versions.
I tried to add 2 receivers towards 2 different targets, I only received one set of metrics not even sure for which db.

Describe the solution you'd like

whatever solves the problem is better than current way.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/oracledb: @dmitryax @crobert-1 @atoulme

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

[crobert-1]

Can you give more information on what custom queries would look like? Are you wanting to enable/disable different metrics from different targets, or are you wanting to write your own query that would then be used to generate custom metrics?

(Also, if you're interested in getting some help debugging your problem of only receiving one set of metrics, please include your full configuration 👍 )

[lucian-vanghele]

@crobert-1 - thanks for replying.

First issue about custom queries: I want to be able to create metrics using my own queries (you know how creative DBAs could be). See for eg https://github.com/iamseth/oracledb_exporter or https://github.com/free/sql_exporter. I see sqlqueryreceiver uses this principle, I will also give it a try but then ... what is the purpose of this oracledb receiver?

Second problem: I was able to fix it by enabling the resource_to_telemetry_conversion on prometheus exporter. I'm only interested now if queries towards these multiple targets are actually performed in paralel.

[crobert-1]

Thanks @lucian-vanghele, the sqlquery receiver would definitely be the better fit here for custom queries. I believe you could use it with the Oracle DB receiver to gather all the metrics you're looking for.

There is overlap between the sqlquery receiver and most (if not all) of the other SQL receivers. The benefit of the dedicated receivers is the ability to simply enable/disable metrics, without having to worry about underlying queries. There's more flexibility with the sqlquery receiver, but then it's up to the user to figure out how to query the backend DB properly, what format and naming scheme the metrics should have, etc.

[lucian-vanghele]

@crobert-1 - I believe most, if not all, of the Oracle users (administrators actually) would like to have full control on these queries. So, I'm not sure how many will see the benefit you mentioned.
collection_interval is also a critical aspect which is missing in oracledb receiver.

[crobert-1]

I believe most, if not all, of the Oracle users (administrators actually) would like to have full control on these queries. So, I'm not sure how many will see the benefit you mentioned.

That's fair! You're welcome to try out the SQL query receiver then and let us know if that works for your use case. Also, if you have any specific metrics or queries that would be especially helpful, you'd be welcome to request them to be added to the oracle DB receiver 👍

collection_interval is also a critical aspect which is missing in oracledb receiver.

My apologies! It's available but for some reason we forgot to document it properly. I've submitted a PR to add it to the README. Thanks for bringing this up!

[lucian-vanghele]

I already tested sqlquery receiver, it works ok for now. However, I don't see the instance.name attribute (as for oracledb receiver) so I had to add it as a static attribute for each metric in order to be able to distinguish between timeseries related to different oracle instances. Also, I don;t find what is the timeout setting as some queries can take several seconds. I assume all receivers are executed parallel each in its own thread (as there is this collection_interval setting), right?

[crobert-1]

Also, I don;t find what is the timeout setting as some queries can take several seconds. I assume all receivers are executed parallel each in its own thread (as there is this collection_interval setting), right?

The timeout setting is disabled by default, so unless you've set it, it shouldn't impact any functionality here. Yes, all receivers are executed in parallel, so the collection interval for the receiver has no impact on other receivers, and other receivers' collection intervals won't impact the oracle DB receiver.

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

• receiver/oracledb: @dmitryax @crobert-1 @atoulme

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.