You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/configuration/configuration.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ You can configure Kepler by passing flags when starting the service. The followi
23
23
|`--host.sysfs`| Path to sysfs filesystem |`/sys`| Any valid directory path |
24
24
|`--host.procfs`| Path to procfs filesystem |`/proc`| Any valid directory path |
25
25
|`--monitor.interval`| Monitor refresh interval |`5s`| Any valid duration |
26
+
|`--monitor.max-terminated`| Maximum number of terminated workloads to keep in memory until exported |`500`| Any non-negative integer (0 for unlimited) |
26
27
|`--web.config-file`| Path to TLS server config file |`""`| Any valid file path |
staleness: 1000ms # Duration after which data is considered stale (default: 1000ms)
81
+
maxTerminated: 500# Maximum number of terminated workloads to keep in memory (default: 500)
74
82
75
83
host:
76
84
sysfs: /sys # Path to sysfs filesystem (default: /sys)
@@ -139,12 +147,15 @@ log:
139
147
monitor:
140
148
interval: 5s
141
149
staleness: 1000ms
150
+
maxTerminated: 500
142
151
```
143
152
144
153
- **interval**: The monitor's refresh interval. All processes with a lifetime less than this interval will be ignored. Setting to 0s disables monitor refreshes.
145
154
146
155
- **staleness**: Duration after which data computed by the monitor is considered stale and recomputed when requested again. Especially useful when multiple Prometheus instances are scraping Kepler, ensuring they receive the same data within the staleness window. Should be shorter than the monitor interval.
147
156
157
+
- **maxTerminated**: Maximum number of terminated workloads (processes, containers, VMs, pods) to keep in memory until the data is exported. This prevents unbounded memory growth in high-churn environments. Set to 0 for unlimited (no limit). When the limit is reached, the least power consuming terminated workloads are removed first.
0 commit comments