spiegel_podman/pkg/domain/entities
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
..
reports Removing the RawInput from the API output 2022-11-17 15:41:01 +09:00
types Add podman system check for checking storage consistency 2024-06-04 10:00:37 -04:00
apply.go Add podman kube apply command 2022-11-01 15:30:17 -04:00
auto-update.go auto update: fix usage of --authfile 2023-07-05 08:30:39 +02:00
container_ps.go Bump Go module to v5 2024-02-08 09:35:39 -05:00
containers.go cleanup: add new --stopped-only option 2024-08-27 15:01:23 +02:00
engine.go remote: fix incorrect CONTAINER_CONNECTION parsing 2024-06-21 14:01:22 +02:00
engine_container.go Add podman system check for checking storage consistency 2024-06-04 10:00:37 -04:00
engine_image.go Should not force conversion of manifest type to DockerV2ListMediaType 2024-08-07 06:07:46 -04:00
events.go properly implement pull-error event status 2024-03-05 10:50:42 +01:00
filters.go Swagger refactor/cleanup 2022-05-19 15:24:18 -07:00
generate.go Bump Go module to v5 2024-02-08 09:35:39 -05:00
healthcheck.go podmanv2 enable healthcheck run 2020-03-29 18:48:29 -05:00
images.go prune: support clearing build cache using CleanCacheMount 2024-09-05 10:40:07 -07:00
machine.go Add disclaimer to podman machine info manpage. 2024-09-03 15:23:18 -04:00
manifest.go swagger fix infinitive recursion on some types 2024-04-12 15:26:34 +02:00
network.go swagger fix infinitive recursion on some types 2024-04-12 15:26:34 +02:00
play.go Bump Go module to v5 2024-02-08 09:35:39 -05:00
pods.go Add --health-max-log-count, --health-max-log-size, --health-log-destination flags 2024-09-25 14:01:35 +02:00
secrets.go Bump Go module to v5 2024-02-08 09:35:39 -05:00
set.go Fix Id->ID where possible for lint 2020-06-10 05:49:41 -04:00
system.go Add podman system check for checking storage consistency 2024-06-04 10:00:37 -04:00
types.go Bump Go module to v5 2024-02-08 09:35:39 -05:00
volumes.go swagger fix infinitive recursion on some types 2024-04-12 15:26:34 +02:00