Skip to content

Service Log Collection

Starter
Professional

When container_and_service_enable is set to true, Glouton automatically detects all known services running on the machine — whether they run as host services or inside containers — and starts collecting their logs without any per-service configuration.

log.opentelemetry.auto_discovery.container_and_service_enable: true

This option is also enabled when using all_enable.

Each service has a built-in log format that parses log lines into structured fields (e.g., HTTP method, status code, client IP, severity level).

| Service | Host Log Files | Container Format | |---------|---------------|-----------------| | Apache | /var/log/apache2/access.log, /var/log/apache2/error.log | apache_both | | Nginx | /var/log/nginx/access.log, /var/log/nginx/error.log | nginx_both | | PostgreSQL | /var/log/postgresql/postgresql-*-main.log | postgresql_docker | | MySQL | /var/log/mysql/error.log | mysql_docker | | Redis | /var/log/redis/redis-server.log | redis_docker | | Valkey | /var/log/valkey/valkey-server.log | valkey_docker | | Kafka | containers only | kafka_docker | | HAProxy | containers only | haproxy_docker | | MongoDB | containers only | mongodb_docker | | RabbitMQ | containers only | rabbitmq_docker |

For the complete list of built-in formats, see Log Formats & Filters.