Feature request
Add OpenTelemetry export support so indexer logs, traces, and metrics can be sent to external observability backends (Logfire, Grafana, Datadog, etc.).
Use case
When running HyperIndex in production, it's valuable to have structured observability integrated with the rest of the infrastructure. Currently context.log output is only visible in the HyperIndex dashboard. With OTEL export, indexer telemetry would flow into the same observability stack as the rest of the application (API routes, contracts, frontend).
Specific scenarios:
- Tracing effect execution (notifications, cast posting) end-to-end across indexer → API → upstream
- Monitoring re-indexing progress and effect cache hit rates
- Alerting on effect failures or rate limit saturation
- Correlating on-chain event processing latency with downstream API performance
Context
Discussed in Envio Slack — Dmitry Zakharov suggested filing this issue to gauge demand.
Feature request
Add OpenTelemetry export support so indexer logs, traces, and metrics can be sent to external observability backends (Logfire, Grafana, Datadog, etc.).
Use case
When running HyperIndex in production, it's valuable to have structured observability integrated with the rest of the infrastructure. Currently
context.logoutput is only visible in the HyperIndex dashboard. With OTEL export, indexer telemetry would flow into the same observability stack as the rest of the application (API routes, contracts, frontend).Specific scenarios:
Context
Discussed in Envio Slack — Dmitry Zakharov suggested filing this issue to gauge demand.