Skip to content

Commit a4de0f2

Browse files
author
GitHub Actions
committed
Configuring log aggregation and observability for sonataflow
1 parent 3db8483 commit a4de0f2

File tree

6 files changed

+664
-0
lines changed

6 files changed

+664
-0
lines changed
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
ifdef::context[:parent-context: {context}]
3+
4+
[id="configure-opentelemetry-for-sonataflow-workflows_{context}"]
5+
= Configure OpenTelemetry for SonataFlow workflows
6+
7+
8+
:context: configure-opentelemetry-for-sonataflow-workflows
9+
10+
[role="_abstract"]
11+
To maintain high availability and performance of your serverless workflows, you must implement a comprehensive observability strategy. You can enable the OpenTelemetry extension, configure exporters for Jaeger and Loki, and interpret the generated telemetry data to monitor SonataFlow workflow health and performance.
12+
13+
// Enable OpenTelemetry for SonataFlow workflows
14+
include::../modules/extend_orchestrator-in-rhdh/proc-enable-opentelemetry-for-sonataflow-workflows.adoc[leveloffset=+1]
15+
16+
// Configuring telemetry exporters for Jaeger and Loki
17+
include::../modules/extend_orchestrator-in-rhdh/proc-configure-telemetry-exporters.adoc[leveloffset=+1]
18+
19+
// SonataFlow OpenTelemetry attributes and events
20+
include::../modules/extend_orchestrator-in-rhdh/proc-configure-observability-tools.adoc[leveloffset=+1]
21+
22+
// Troubleshooting OpenTelemetry integration
23+
include::../modules/extend_orchestrator-in-rhdh/ref-troubleshoot-opentelemetry-connectivity.adoc[leveloffset=+1]
24+
ifdef::parent-context[:context: {parent-context}]
25+
ifndef::parent-context[:!context:]
26+

0 commit comments

Comments
 (0)