GitLab log files and forwarding to a SIEM
Which GitLab logs matter for operations and security, shipping structured JSON logs to Elasticsearch, OpenSearch or Splunk, and handling stdout logs on the Helm chart.

Day-two operation of self-managed GitLab: logs, health checks, Prometheus metrics, maintenance mode and collecting data for support.
Which GitLab logs matter for operations and security, shipping structured JSON logs to Elasticsearch, OpenSearch or Splunk, and handling stdout logs on the Helm chart.
Using /-/readiness and /-/liveness correctly in load balancers and probes, IP allowlisting for monitoring hosts and why /health_check should not drive autoscaling.
Putting GitLab into read-only Maintenance Mode for upgrades, migrations and Geo failover: what users can still do, background jobs and the Premium requirement.
Scraping GitLab's bundled exporters into Prometheus and Grafana, the metrics worth alerting on and monitoring Gitaly, PostgreSQL and Redis tiers separately.
Preparing a support case for self-managed GitLab: gitlab-ctl tail captures, the main log locations by component and what to collect before escalating to GitLab or a partner.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.