spiegel_podman/libpod/define
Jan Rodák de856dab99
Add --health-max-log-count, --health-max-log-size, --health-log-destination flags
These flags can affect the output of the HealtCheck log. Currently, when a container is configured with HealthCheck, the output from the HealthCheck command is only logged to the container status file, which is accessible via `podman inspect`.
It is also limited to the last five executions and the first 500 characters per execution.

This makes debugging past problems very difficult, since the only information available about the failure of the HealthCheck command is the generic `healthcheck service failed` record.

- The `--health-log-destination` flag sets the destination of the HealthCheck log.
  - `none`: (default behavior) `HealthCheckResults` are stored in overlay containers. (For example: `$runroot/healthcheck.log`)
  - `directory`: creates a log file named `<container-ID>-healthcheck.log` with JSON `HealthCheckResults` in the specified directory.
  - `events_logger`: The log will be written with logging mechanism set by events_loggeri. It also saves the log to a default directory, for performance on a system with a large number of logs.

- The `--health-max-log-count` flag sets the maximum number of attempts in the HealthCheck log file.
  - A value of `0` indicates an infinite number of attempts in the log file.
  - The default value is `5` attempts in the log file.
- The `--health-max-log-size` flag sets the maximum length of the log stored.
  - A value of `0` indicates an infinite log length.
  - The default value is `500` log characters.

Add --health-max-log-count flag

Signed-off-by: Jan Rodák <hony.com@seznam.cz>

Add --health-max-log-size flag

Signed-off-by: Jan Rodák <hony.com@seznam.cz>

Add --health-log-destination flag

Signed-off-by: Jan Rodák <hony.com@seznam.cz>
2024-09-25 14:01:35 +02:00
..
annotations.go Fix podman stop and podman run --rmi 2024-08-20 09:51:18 -04:00
autoupdate.go auto-update: validate container image 2022-09-26 17:07:05 +02:00
checkpoint_restore.go Added optional container checkpointing statistics 2021-11-15 11:50:24 +00:00
config.go logging: new mode -l passthrough-tty 2024-02-28 17:23:59 +01:00
container.go Add support for Job to kube generate & play 2024-09-05 11:36:38 -04:00
container_inspect.go Add --health-max-log-count, --health-max-log-size, --health-log-destination flags 2024-09-25 14:01:35 +02:00
containerstate.go Send container stats over API on a per-interface basis 2024-02-06 17:05:07 -05:00
diff.go podman diff accept two images or containers 2021-07-02 17:11:56 +02:00
errors.go fix race conditions in start/attach logic 2024-07-12 15:11:34 +02:00
exec_codes.go podman exec CID without command should exit 125 2024-04-12 07:44:22 -04:00
exit_code_propagation.go kube play: exit-code propagation 2023-05-25 14:46:34 +02:00
fileinfo.go Fixes from make codespell 2021-04-21 13:16:33 -04:00
healthchecks.go Add --health-max-log-count, --health-max-log-size, --health-log-destination flags 2024-09-25 14:01:35 +02:00
info.go Add rootless network command to podman info 2024-03-26 09:56:48 -04:00
mount.go Add support for ramfs as well as tmpfs in volume mounts 2023-08-21 07:14:57 -04:00
mount_freebsd.go pkg/specgen: add support for 'podman run --init' on FreeBSD 2023-06-28 14:43:50 +01:00
mount_linux.go Use constants for mount types 2023-07-14 07:17:21 -04:00
mount_unsupported.go libpod/define: Make TypeBind a platform-specific constant 2022-08-30 16:32:24 +01:00
pod_inspect.go Include lock number in pod/container/volume inspect 2023-06-05 12:28:50 -04:00
podstate.go Add a Degraded state to pods 2020-10-21 13:31:40 -04:00
runtime.go Add support for containers.conf 2020-03-27 14:36:03 -04:00
sdnotify.go add "healthy" sdnotify policy 2023-07-25 11:17:44 +02:00
version.go Bump Go module to v5 2024-02-08 09:35:39 -05:00
volume_inspect.go Include lock number in pod/container/volume inspect 2023-06-05 12:28:50 -04:00