Additional Logs on Verbose

[AnserAli57]

when running sql_exporter on Verbose it only gives information like cache metric status , Database Driver Status
can we have some additional logging on verbose mode as in What query its executing and how much time that query is taking to return value

[burningalchemist]

Hi @AnserAli57, which version you're using?

There is a feature for scrape duration metric already implemented and the query used is also referenced in the logs.

If you use a single target mode, you need to name the target so this data becomes visible. Just add name field to the target section and restart the exporter.

Give it a try and let me know? 🙂👍

Configuration reference from the docs:

# The target to monitor and the list of collectors to execute on it.
target:
  # Target name (optional). Setting this field enables extra metrics e.g. `up` and `scrape_duration` with
  # the `target` label that are always returned on a scrape.
  name: "prices_db"
  # Data source name always has a URI schema that matches the driver name. In some cases (e.g. MySQL)
  # the schema gets dropped or replaced to match the driver expected DSN format.
  data_source_name: 'sqlserver://prom_user:prom_password@dbserver1.example.com:1433'

[AnserAli57]

hi @burningalchemist

I was using an old version i switched to latest one was able to gets some good insights on logs , although as it does give me the info of how long it took for every scrape on a metric but i'm trying to find a way to get time taken by every query thats being executed .

also is there anyway i can add other labels instead of these three
[target,collector,query]

[burningalchemist]

Hey @AnserAli57, I think on the query execution duration this is something I may add to the next release, indeed. Thanks for your suggestion. 👍

On the other labels for the logContext matter it's unavailable. The logContext is rather an internal context, and serves to understand which stage of the pipeline the debug message comes from:

job (optional) > target > collector > metric > query.

If there is a scrape error, sql_exporter also creates a respective scrape_error metric with these details.

Adding additional labels for the time being doesn't seem to relate much in this particular scope, so it's not ready for any arbitrary key/value pairs.