Content-Length: 70649 | pFad | http://phabricator.wikimedia.org/T380960
sSome kernel warning and error messages need to be ignored.
Examples:
We could update the detector to read a config file with regexes, or lines, to ignore.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T209460 CloudVPS: network architecture | |||
| Resolved | aborrero | T270704 cloud: introduce new edge network architecture for eqiad1 and codfw1dev | |||
| Unknown Object (Task) | |||||
| Resolved | aborrero | T376589 cloudgw1002: network interface problem | |||
| Resolved | aborrero | T376719 alerting: detect if a kernel had a panic | |||
| Open | None | T380960 kernel error detector: have a way to ignore certain messages |
Another possibility (maybe on top of) would be to be able to acknowledge the errors, for example read a timestamp from a file before which the errors will be ignored (ex. if an issue might happen again, but the current event is not relevant anymore).
That would be nice to have. But I would not know how to implement this off the top of my head. How would you implement it?
That would be nice to have. But I would not know how to implement this off the top of my head. How would you implement it?
Maybe something like cookbook wmcs.ack_kernel_errors --hostname <> creates the file on the node with the timestamp (say /etc/prometheus/kernel_errors_exporter.yaml), then the script reads that file.
Fetched URL: http://phabricator.wikimedia.org/T380960
Alternative Proxies: