Logs on GitLab.com

Information about logs on GitLab.com.

How we log on GitLab.com

Fluentd parses our logs, then sends them to:

• Stackdriver Logging, which stores logs long-term in Google Cold Storage (GCS).
• Cloud Pub/Sub, which forwards logs to an Elastic cluster using pubsubbeat.

For more information, see our runbooks for:

• A detailed list of what we’re logging.
• Our current log retention policies.
• A diagram of our logging infrastructure.

Erase CI/CD job logs

By default, GitLab does not expire CI/CD job logs. Job logs are retained indefinitely, and can’t be configured on GitLab.com to expire. You can erase job logs by either:

• Using the Jobs API.
• Deleting the pipeline the job belongs to.