Problem with receiving traces in OTEL Collector

[davide-russo-tfs]

Hello,

I'm trying to do a simple test by using the run-with-telemetry GH Action with the Github Receiver by OpenTelemetry.
The following services are running on my personal laptop:

• OpenTelemetry Collector v. 0.119.0
• Github Runner

I created a simple GH Action Workflow to deploy a few resources into a Databricks workspace. This is the config file:

name: deploy_databricks

on:
  push:
    branches: [ "main" ]
  workflow_dispatch:

permissions: read-all

concurrency: 1

env: 
  DATABRICKS_TOKEN: ###
  otel-exporter-otlp-endpoint: localhost:4317
  otel-service-name: test_otel_github

jobs:
  deploy_resources:
    runs-on: self-hosted 
    steps:
      - uses: actions/checkout@v4
      - uses: databricks/setup-cli@main  # Download Databricks CLI

      - name: "Deploy resources with monitoring"
        uses: krzko/[email protected]
        with:
          otel-exporter-otlp-endpoint: ${{ env.otel-exporter-otlp-endpoint }}
          otel-service-name: ${{ env.otel-service-name }}
          step-name: Deploy resources with monitoring
          run: databricks bundle deploy

This is instead the config file of the OpenTelemetry collector that I'm using:

receivers:
  github:
    scrapers:
      scraper:
    webhook:
      endpoint: localhost:4317
    tls:
      insecure: true

exporters:
  debug:
    verbosity: basic

service:
  pipelines:
    traces:
      receivers: [github]
      exporters: [debug]

The workflow executes successfully but I don't receive any trace in output:

In addition, I see the following error in the logs of the GH Workflow:

I followed the documentation of the repo but can't find the mistake I'm committing.
Any help is super appreciated, thanks

[krzko]

Hey @davide-russo-tfs,

The OpenTelemetry Github Receiver that you are using is different to the intended use cases for run-with-telemetry.

The one that you have enabled, was recently renamed from git and only provides metrics telemetry and not traces.

I donated my implementation (27460) of the receiver with trace telemetry capabilities to the maintainers of the OpenTelemetry Collector a couple of years ago, and it's still not been implemented.

For this reason I created a custom OTel Collector distribution with the Github Actions receiver with traces enabled, so folks can take advantage of converting Github events to spans. This is the version which will work nicely with run-with-telemetry.

It's a shame they've taken 2 years to approve a fully implemented solution. We've been running this implementation for a couple of years without issue, so its battle hardened in the enterprise. I guess that's the nature of large Open Source projects sometimes.