Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 怎么变更prometheus启动日志为debug?
|
username: 逍遥_猫
How can I change the Prometheus log level to debug mode when it starts with the cluster? I want to check the status of it pulling monitoring data.
tiup cluster stop tidb1 -R prometheus
Then manually start prometheus, it keeps reporting connection refused errors
Check the startup process, it is already in debug mode
Test Conclusion:
Does it mean that starting with debug reports an error, but starting with info is normal?
Does forcibly adding log.level in tiup cluster edit-config have any effect?
Maybe what you want is not logged.
However, the status of targets can be viewed in the Prometheus Web UI (http://IP:Port/targets).
Additionally, after the data is successfully scraped, it is written into tsdb, and you can directly write PromQL queries.
How can I see the historical data if this only shows the last one?
The debug startup is manually starting Prometheus with a string of parameters, resulting in an error and not logging any messages. After stopping with ctrl+c, no errors are logged. This is not the same as starting with tiup cluster start tidb1 -R prometheus, and I haven’t found a way to pass parameters with this startup method.
It seems that only the command line can be used; the configuration file is not supported.
Historical data or historical state? Historical data has already been written into TSDB.
There’s no need to look at historical states, right?
If you want to know whether a certain target has been interrupted or during which time period there was no data, you can still see it through TSDB’s data.
Use the tiup cluster edit-config command to edit the configuration file, and then reload.
I tried it, and even with the correct spelling, it doesn’t allow adding. 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 