github-action-to-otlp icon indicating copy to clipboard operation
github-action-to-otlp copied to clipboard

Collects no data, github API says 404

Open wosc opened this issue 2 years ago • 2 comments
trafficstars

Hi, I like this idea very much (and much more than say buildevents which requires you to litter your workflows with tracing steps), but I don't get any data out of it, unfortunately. My configuration looks like this:

    - uses: codeboten/github-action-to-otlp@611adf25af400e7ac3025017961d88929b3ef1c6  # XXX repo-token seems unreleased
      with:
        endpoint: 'api.honeycomb.io:443'
        headers: 'x-honeycomb-team=${{steps.secrets.outputs.hny_apikey}},x-honeycomb-dataset=devel-gha'
        repo-token: ${{secrets.GITHUB_TOKEN}}

And I get this output:

Run codeboten/github-action-to-otlp@611adf25af400e7ac3025017961d88929b3ef1c6
/usr/local/bin/docker run --name e226228c0bb8ae4d47a8b7b15e679adc42bc_44abf4 --label 60e226 --workdir /github/workspace --rm -e "PROJECT" -e "BUILD_URL" -e "RAW" -e "GPG_KEY_PRIVATE" -e "CLOUDSDK_AUTH_CREDENTIAL_FILE_OVERRIDE" -e "GOOGLE_APPLICATION_CREDENTIALS" -e "GOOGLE_GHA_CREDS_PATH" -e "CLOUDSDK_CORE_PROJECT" -e "CLOUDSDK_PROJECT" -e "GCLOUD_PROJECT" -e "GCP_PROJECT" -e "GOOGLE_CLOUD_PROJECT" -e "VAULT_TOKEN" -e "TOKEN" -e "HNY_APIKEY" -e "INPUT_ENDPOINT" -e "INPUT_HEADERS" -e "INPUT_REPO-TOKEN" -e "OTEL_EXPORTER_OTLP_ENDPOINT" -e "OTEL_EXPORTER_OTLP_HEADERS" -e "GITHUB_TOKEN" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_EVENT_PATH" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "GITHUB_ACTION" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e "ACTIONS_ID_TOKEN_REQUEST_URL" -e "ACTIONS_ID_TOKEN_REQUEST_TOKEN" -e GITHUB_ACTIONS=true -e CI=true --network github_network_1b4d49ca8e644724a5b3399a6099c189 -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/runner/_work/_temp/_github_home":"/github/home" -v "/runner/_work/_temp/_github_workflow":"/github/workflow" -v "/runner/_work/_temp/_runner_file_commands":"/github/file_commands" -v "/runner/_work/edge-www/edge-www":"/github/workspace" 60e226:228c0bb8ae4d47a8b7b15e679adc42bc
2023/04/19 12:09:19 GET https://api.github.com/repos/ZeitOnline/edge-www/actions/runs/4743061057: 404 Not Found []

Almost as if the github API has no data for the current run while it is still running? Or am I holding something wrong? Thanks for any insights!

wosc avatar Apr 19 '23 12:04 wosc

Thanks for the feedback! I'll spend some time and try to repro, its possible the github api has changed since i'd originally written the code. I'll see if i can repro later this week

codeboten avatar Apr 19 '23 12:04 codeboten

Hi, were you able to find out what's going on here? Is there anything I can do to help? Thanks!

wosc avatar Sep 06 '23 11:09 wosc