The Send Logs to Loki GitHub Action collects logs from all jobs in a GitHub Actions workflow and sends them to a Loki instance. Logs are labeled with metadata like job names, job IDs, and custom labels, making them easily searchable and organized in Loki.

• Aggregates logs from all jobs in a workflow, including job-specific logs.
• Allows dynamic injection of custom labels.
• Automatically retries fetching logs if they are not immediately available.

- name: Set up Python
  uses: actions/setup-python@v4
  with:
    python-version: '3.x'
- name: Send Logs to Loki
  uses: skroutz/action-send-logs-to-loki@latest
  with:
    loki_endpoint: "https://loki.example.com"
    labels: "job=github-actions,run_id=${{ github.run_id }}"
    github_token: ${{ secrets.GITHUB_TOKEN }}

1. Log Aggregation: The action iterates over all jobs in the workflow using the GitHub Actions API.
2. Log Retrieval: Logs are fetched for completed jobs and skipped for jobs still in progress.
3. Log Transmission: Logs are sent to Loki with the specified labels.

• Add Custom Labels: Use the labels input to include additional metadata for your logs.
  • Example: labels: "job=github-actions,env=production"
• Loki Endpoint: Specify the Loki instance URL with loki_endpoint.
• Retry Configuration: Use the max_retries and retry_interval_seconds inputs to control log fetch retry behavior.

By default, job_name are automatically added as labels for each job. (Be mindful of cardinality!)

This action requires Python 3. It is recommended to use the official GitHub action to ensure the correct Python version is installed:

- name: Set up Python
  uses: actions/setup-python@v4
  with:
    python-version: '3.x'

• Logs are only fetched for completed jobs. Logs for in-progress jobs will be skipped.
• Timestamps in Loki are processed as arrived. Therefore Loki timestamps are injected at the time of transmission, along with GitHub Actions real Timestamps.