You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4e48c0d
Browse filesBrowse the repository at this point in the historyBrowse files
Existing `ExecutionOtelPlugin.factory(...)` and `InvocationOtelPlugin.factory(...)`
122
+
calls remain supported.
123
+
124
+
For loading without handler-side imports or registration, set
125
+
`DURABLE_EXECUTION_PLUGINS=otel`. This selects execution mode; `otel-execution`
126
+
is still supported and `otel-invocation` selects invocation mode.
127
+
128
+
**Set exactly one OTel entry name.**`otel` and `otel-execution` select the same
129
+
view, but they are separate providers, so listing both puts two factories in the
130
+
`durable-otel-view` exclusive group. For example,
131
+
`DURABLE_EXECUTION_PLUGINS=otel-execution,otel` fails at startup with:
132
+
133
+
```text
134
+
Conflicting plugin factories otel-execution (ExecutionOtelPlugin) and otel (ExecutionOtelPlugin) in exclusive group 'durable-otel-view'. Configure only one plugin from this group.
135
+
```
136
+
137
+
The plugin JAR and configured ADOT/provider/exporter must still be available as
138
+
described below. Installing the JAR alone does not enable instrumentation.
139
+
73
140
## Installation
74
141
75
142
```xml
@@ -258,10 +325,11 @@ MyFunction:
258
325
259
326
With the layer and `DURABLE_EXECUTION_PLUGINS=otel-invocation` configured above, no OTel plugin dependency or registration code is required in the function artifact. The function can use its existing `DurableConfig`.
260
327
261
-
The OTel plugin JAR exposes two dynamic provider names:
328
+
The OTel plugin JAR exposes three dynamic provider names:
0 commit comments