Lagoon provides access to the following logs via Kibana:
<<<<<<< HEAD 1. Logs from the Kubernetes Routers, including every single HTTP and HTTPS request with: ======= * Logs from the Kubernetes Routers, including every single HTTP and HTTPS request with:
c5708ed6d405ed33273a925012b66d0fe1156036 * Source IP * URL * Path * HTTP verb * Cookies * Headers * User agent * Project * Container name * Response size * Response time * Logs from containers: *
stderrmessages * Container name * Project * Lagoon logs: * Webhooks parsing * Build logs * Build errors * Any other Lagoon related logs * Application logs: * For Drupal: install the Lagoon Logs module in order to receive logs from Drupal Watchdog. * For Laravel: install the Lagoon Logs for Laravel package. * For other workloads: * Send logs to
udp://application-logs.lagoon.svc:5140* Ensure logs are structured as JSON encoded objects. * Ensure the
typefield contains the name of the Kubernetes namespace (
To access the logs, please check with your Lagoon administrator to get the URL for the Kibana route (for amazee.io, this is https://logs.amazeeio.cloud/).
Each Lagoon user account has their own login and will see the logs only for the projects to which they have access.
Each Lagoon user account also has their own Kibana Tenant, which means no saved searches or visualizations are shared with another account.
If you would like to know more about how to use Kibana: https://www.elastic.co/webinars/getting-started-kibana.