nginx_proxy | The nginx_proxy logs capture HTTP request details, such as source IPs, requested URLs, and response status codes. | Monitor routing decisions, load balancing actions, errors during proxying, and buffering behavior. Includes connection details, such as IP addresses used and handling of slow client connections. |
nginx-exporter | The nginx-exporter container provides metrics for real-time data on request rates, connection states, and other performance indicators. | Use these logs to diagnose active connections, HTTP requests, and errors related to metric scraping. |
proxy | If your setup has a dedicated proxy container separate from the nginx_proxy , its logs likely include similar request and response details. | Logs incoming and outgoing requests, records HTTP status codes, URLs, client IP addresses, and identifies network-related errors such as failed connections, timeouts, or DNS issues. |
keycloak | The keycloak container logs focus on authentication and authorization events. | Monitor login attempts, token issuances, and any errors related to identity management or user account configuration. |
configurator | The configurator container handles dynamic application settings. | Review these logs for errors in configuration files or loading of new settings. If you see repeated reload attempts, investigate potential misconfigurations. |
repo_api | Logs from the repo_api container track API requests and responses. | Find status codes, endpoint usage stats, and application-level errors. Monitoring these logs helps you diagnose failing API calls or performance slowdowns. |
database_migrator | The database_migrator logs capture schema updates, migration scripts, and any associated errors. | If a migration fails, these logs can pinpoint the exact database operation or script that caused the issue. |
repo_worker | The repo_worker container often performs background jobs or asynchronous tasks. These logs might include job execution times, error messages, and status updates on queued tasks. | Monitor details on job dispatching, event handling, and Prometheus metrics, with security requirements for internal access only |
repo_dispatcher | The repo_dispatcher container is responsible for routing tasks. | These logs relate to job scheduling, event dispatching, and the outcome of triggered processes. |
postgres | postgres container logs cover database-level events like connections, queries, and errors. | These logs show database queries, connection attempts, transaction processes, and any errors or warnings related to database integrity and performance, particularly during upgrades or backups. Check these logs if you’re tracking database performance or investigating query timeouts. |
postgres-exporter | The postgres-exporter container provides metrics instead of raw logs. | Monitor database performance details for metrics collection, export status, connection attempts to the PostgreSQL database, and any encountered errors during metrics scraping, helping to |
redis | The redis logs often show keyspace events, connection details, and error messages related to data persistence. | Use these logs to track ephemeral key usage, detect potential memory leaks, and troubleshoot connection issues. |
redis-exporter | The redis-exporter container shows metrics on Redis usage—such as memory consumption, key eviction rates, and command execution frequency. | Provides metrics on cache performance, hit/miss ratios, and memory usage. Essential for monitoring Redis health and performance. Review these metrics to optimize your caching strategy and forecast resource needs. |
prometheus | The prometheus logs can highlight scraping errors, rule evaluation problems, or storage-related issues. | Logs metric collection, storage details, and alerting rules. Important for ensuring accurate and timely monitoring data. Review these logs if your metrics aren’t updating as expected or alerts fail to trigger. Check for error messages or slow scrape warnings. |
node_exporter | The node_exporter logs report on the health of the exporter process. | These logs provide metrics on system resources like CPU, memory, and disk usage. Check for messages about missing permissions or inaccessible system files. |