Skip to content

Latest commit

 

History

History
30 lines (22 loc) · 1.23 KB

operating.md

File metadata and controls

30 lines (22 loc) · 1.23 KB

Operating

Debugging

If you need to dynamically change the log level of the application, you can use the /logging HTTP endpoint. To set the log level use the POST method with URL parameter level of value error, warning, info or debug.

Example using cURL

# Use GET to get current log level.
$ curl -s http://0.0.0.0:8080/logging
current logging level is: debug

# Use POST to set the log level.
$ curl -XPOST -s http://0.0.0.0:8080/logging?level=info
logging level set to: info

Profiling

In case of issues with leaking resources for example, slo-exporter supports the Go profiling using pprof on /debug/pprof/ web interface path. For usage see the official docs.

Frequently asked questions

How to add new normalization replacement rule?

Event normalization can be done using the relabel module, see its documentation.

How to deal with malformed lines?

Before !87. If you are seeing too many malformed lines then you should inspect tailer package and seek for variable lineParseRegexp. After !87, slo-exporter main config supports to specify custom regular expression in field .module.tailer.loglineParseRegexp.