Open Abuelodelanada opened 11 months ago
There are to things to consider here. In prometheus-scrape-config we should validate input and block if the data is wrong.
Also, if Prometheus receives a bad scrape config, it should skip that job and continue working. Which it does. An open question is if it should set a blocked status to notify the user that something is wrong.
Bug Description
Setting and empty string to
scrape_interval
config only produce anERROR
indebug-log
but not in the juju status nor in the command line. Besides removes part of the prometheus config without alerting.To Reproduce
Deploy this bundle:
Check that
zinc
scrape jobs landed atprometheus
:scrape_interval
:juju config scrape-config scrape_interval="12s"
Set an empty string to that config:
$ juju config scrape-config scrape_interval=""
Check the command return no error:
Check that
zinc
scrape job has gone:Environment
Relevant log output
Additional context
No response