v0.11.1: repeated restarts and OOM kills stay on the map for a day
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
4c5eb288cb
commit
8ed76cd01a
@@ -1,3 +1,6 @@
|
||||
v0.11.1:
|
||||
fixes:
|
||||
- "A container restarted three times or more stays marked for 24 hours after its last restart or OOM kill, not 30 minutes: a pod OOM-killed five times in a day was no longer shown 40 minutes after the last kill. A single restart still clears after 30 minutes."
|
||||
v0.11.0:
|
||||
features:
|
||||
- "HTTP details where Cilium parses L7 (a CiliumNetworkPolicy with an http rule on the port): requests, responses by class, p50 and p95 latency and the ten busiest paths on the link, IDs in paths grouped as :id. Links with 5xx responses are drawn in the warning colour. Headers are never requested from Hubble. The docs have an example policy that turns this on for one service without restricting it."
|
||||
|
||||
Reference in New Issue
Block a user