Observability

BeanCRM API exports logs, traces, and metrics with OpenTelemetry OTLP when OpenTelemetry:Enabled is enabled.

Configuration

Use these production variables for a public HTTPS OTLP collector, such as the Bean monitoring collector:

OpenTelemetry__Enabled=true
OpenTelemetry__ServiceName=BeanCrmAPI
OpenTelemetry__OtlpEndpoint=https://monitor-collector.bean.com.ar
OpenTelemetry__Protocol=HttpProtobuf
OpenTelemetry__Environment=Production

With HttpProtobuf, the API sends each signal to the standard OTLP HTTP paths:

• traces: /v1/traces
• metrics: /v1/metrics
• logs: /v1/logs

For an internal collector listening on port 4317, use gRPC instead:

OpenTelemetry__OtlpEndpoint=http://collector:4317
OpenTelemetry__Protocol=Grpc

If OpenTelemetry__Protocol is omitted, BeanCRM chooses gRPC for port 4317 and HTTP/protobuf for other ports.

Troubleshooting

If API errors are visible in Coolify logs but not in SigNoz, verify that the protocol matches the exposed collector endpoint. A public HTTPS collector usually expects HttpProtobuf; using gRPC against that endpoint can prevent logs from arriving.