GitLab monitoring: Setting up Logz.io and ELK stack
Apr 13, 2018Daniel Berman
Summary
This post details the technical steps for integrating GitLab logs with the ELK Stack or Logz.io using Filebeat. It outlines the types of GitLab logs available (production_json.log, production.log, api_json.log, application.log), provides Filebeat configuration examples for shipping these logs to Elasticsearch or Logz.io, and demonstrates basic log analysis and visualization techniques in Kibana, such as querying for failed logins and error responses, and visualizing commits and issues.
More from the Log Management and Observability trail
- Green DevOps: Why carbon measurement belongs in your CI/CD pipeline
- Automate detection testing with GitLab CI/CD and Duo
- How to build CI/CD observability at scale
- Track vulnerability remediation with the updated GitLab Security Dashboard
- More granular product usage insights for GitLab Self-Managed and Dedicated