Updating failedScrapes, incase of zero rows returned first time when SQL exported started(on initial time sql exported started) #152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scenario : Initially there is no data or zero rows returned for a SQL query for a particular DB and then if we start sql_exporter (metrics will be empty at this time). In this case, sql_exporter Metrics UI doesn't have any details to show that SQL query is executed and it is failed.
With this change, SQL Exporter Metrics UI helps and gives more detailed info to the user on query execution status. Instead of no logs for failed case (zero rows returned) now Metrics will have failed details.
Below is entry will come in Metrics with this code change.
sql_exporter_last_scrape_failed{database="DB",driver="postgres",host="hostNmae",query="sql_exporter_query",sql_job="sql_exporter_query",user="reader"} 1