Skip to content

Commit 3d7c72a

Browse files
Merge pull request #4869 from Particular/andreasohlund-patch-1
Add instructions on how to emit RavenDB telemetry
2 parents 712628d + 70d27cd commit 3d7c72a

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

docs/telemetry.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The following ingestion metrics with their corresponding dimensions are availabl
2323
- `result` - Indicates the outcome of the operation: `success`, `failed` or `skipped` (if the message was filtered out and skipped)
2424
- `sc.audit.ingestion.failures_total` - Failure counter
2525
- `message.category` - Indicates the category of the message ingested: `audit-message`, `saga-update` or `control-message`
26-
- `result` - Indicates how the failure was resolved: `retry` or `stored-poision`
26+
- `result` - Indicates how the failure was resolved: `retry` or `stored-poison`
2727
- `sc.audit.ingestion.consecutive_batch_failure_total` - Consecutive batch failures
2828

2929
Example queries in PromQL for use in Grafana:
@@ -32,6 +32,23 @@ Example queries in PromQL for use in Grafana:
3232
- Failure rate: `sum(rate(sc_audit_ingestion_failures_total[$__rate_interval])) by (exported_job,result)`
3333
- Message duration: `histogram_quantile(0.9,sum(rate(sc_audit_ingestion_message_duration_seconds_bucket[$__rate_interval])) by (le,exported_job))`
3434

35+
Example Grafana dashboard - https://github.com/andreasohlund/Docker/blob/main/otel-monitoring/grafana-platform-template.json
36+
3537
## Monitoring
3638

3739
No telemetry is currently available.
40+
41+
## RavenDB
42+
43+
To emit and visualize RavenDB telemetry:
44+
45+
1. Install a RavenDB developer license (needed to get support for emitting telemetry)
46+
2. [Enable and configure Raven to emit telemetry](https://ravendb.net/docs/article-page/6.2/csharp/server/administration/monitoring/open-telemetry) (the example below shows targeting a local OTEL collector)
47+
```
48+
environment:
49+
RAVEN_Monitoring_OpenTelemetry_Enabled: true
50+
RAVEN_Monitoring_OpenTelemetry_OpenTelemetryProtocol_Enabled: true
51+
RAVEN_Monitoring_OpenTelemetry_OpenTelemetryProtocol_Protocol: gRPC
52+
RAVEN_Monitoring_OpenTelemetry_OpenTelemetryProtocol_Endpoint: http://host.docker.internal:4317
53+
```
54+
3. Visualize the data, for example https://grafana.com/grafana/dashboards/22698-ravendb-prometheus/

0 commit comments

Comments
 (0)