Fix OpenTelemetry configuration for HoneyComb integration using standard OTEL environment variables

[Copilot]

The vendor-only telemetry implementation was not properly sending metrics and traces to HoneyComb. The issue was that the OpenTelemetry SDK was being configured with custom OTLP exporter URLs and headers instead of using the standard OpenTelemetry environment variables that HoneyComb requires.

Changes Made

1. Set standard OpenTelemetry environment variables before SDK initialization:

   • OTEL_SERVICE_NAME=trx-parser
   • OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
   • OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io
   • OTEL_EXPORTER_OTLP_HEADERS=x-honeycomb-team={API_KEY}

2. Simplified exporter configuration to use standard OTLP exporters without custom URLs or headers, allowing the SDK to pick up the environment variables automatically.

3. Added test coverage to validate that the required environment variables are properly set during telemetry initialization.

Why This Fixes the Issue

HoneyComb's documentation specifies that these standard OpenTelemetry environment variables must be set for proper integration. The previous implementation manually configured exporters with custom endpoints (/v1/traces, /v1/metrics) and headers, which may not have been compatible with HoneyComb's expected format.

By using the standard OTEL environment variables and letting the SDK handle the configuration automatically, the telemetry data should now properly reach HoneyComb.

Testing

• All existing tests continue to pass (21/21)
• New test validates environment variables are set correctly during initialization
• Build and packaging work without errors
• No impact on action consumers (telemetry remains vendor-only and transparent)

Fixes #330.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.honeycomb.io
  • Triggering command: node /home/REDACTED/work/trx-parser/trx-parser/node_modules/.bin/jest __tests__/telemetry.test.ts (dns block)
  • Triggering command: /usr/local/bin/node /home/REDACTED/work/trx-parser/trx-parser/node_modules/jest-worker/build/workers/processChild.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[NasAmin]

@copilot rebase as this branch is out of date.

[Copilot]

@copilot rebase as this branch is out of date.

Branch has been successfully rebased onto the latest main branch. All tests continue to pass (21/21) and the branch is now up to date. Commit: cf5a372

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.honeycomb.io
  • Triggering command: /usr/local/bin/node /home/REDACTED/work/trx-parser/trx-parser/node_modules/jest-worker/build/workers/processChild.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)