marc/opentelemetry-trace-export-forgejo-action
1
0
Fork 0
Code Issues 2 Pull requests Releases Activity Actions
A Forgejo-specific OTel trace export action that makes instrumenting CI/CD pipelines easy as pie. 🥧
6 commits 1 branch 0 tags 95 KiB
Python 95.8%
Dockerfile 4.2%
Find a file
Marc Cataford 18546df072
Some checks failed
/ static_analysis (push) Failing after 1m25s
Details
ci: add static analysis steps (format+lint+validate yaml)
2024-10-18 22:12:42 -04:00
.forgejo/workflows ci: add static analysis steps (format+lint+validate yaml) 2024-10-18 22:12:42 -04:00
.gitignore Initial commit 2024-10-18 04:40:13 +00:00
.pre-commit-config.yaml build: add pre-commit hooks 2024-10-18 21:10:29 -04:00
action.yaml feat: initial upload 2024-10-18 00:48:18 -04:00
Dockerfile refactor: use bin within container to invoke export function 2024-10-18 21:05:30 -04:00
pyproject.toml build: add pre-commit hooks 2024-10-18 21:10:29 -04:00
README.md feat: initial upload 2024-10-18 00:48:18 -04:00
requirements.txt feat: initial upload 2024-10-18 00:48:18 -04:00
tracer.py build: add pre-commit hooks 2024-10-18 21:10:29 -04:00
uv.lock build: add pre-commit hooks 2024-10-18 21:10:29 -04:00

README.md

opentelemetry-trace-export-forgejo-action

Handles the export of OTel traces from Forgejo Actions.

Usage

The action pulls action run metadata from non-documented Forgejo APIs and run context data; as long as it runs as the last step, it should capture details from every job in the pipeline.

jobs:
  stepA:
    ...
  stepB:
    ...
  export-otel-traces:
    ...
    needs: [stepA, stepB]
    steps:
      - uses: https://forge.karnov.club/marc/opentelemetry-trace-export-forgejo-action
        with:
          otlp-endpoint: <GRPC endpoint to send traces to>
          otlp-service-name: <Service name to attach to traces>
          forgejo-token: <Action-scoped token>
          forgejo-base-url: <Base url of the Forgejo instance where the actions are running>
          run-id: <Current CI run ID>
          repo-name: <Current repository name>