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
spin up an instance of apm-integration-testing
a. use with opbeans-dotnet, which is the only service that supports otel baggage.
b. run example python3 ./scripts/compose.py start --with-opbeans-dotnet main
c. kibana will be available on 127.0.0.1:5601
opbean-swift should automatically connect to local apm-server and opbeans service (see note below). You can make changes to these connections using agent-conf.json and apiData.json.
configure a baggage manager and register it OpenTelemetry.registerBaggageManager(...). Do this because default baggage manager is probably a no-op.
Add a new baggage attribute: request.source: opbeans-swift. This should get automatically added to all out going requests, but you can verify this by looking at opentelemetry-swift URLSession instrumentation
Note:
You'll need to expose opbeans-dotnet in docker-compose.yml (in apm-integration-testing):
...
"ports": [
"127.0.0.1:3004:3000"
]
to
"ports": [
"3004:3000"
]
then docker-compose up -d
The text was updated successfully, but these errors were encountered:
a. use with opbeans-dotnet, which is the only service that supports otel baggage.
b. run example
python3 ./scripts/compose.py start --with-opbeans-dotnet main
c. kibana will be available on 127.0.0.1:5601
OpenTelemetry.registerBaggageManager(...)
. Do this because default baggage manager is probably a no-op.request.source: opbeans-swift
. This should get automatically added to all out going requests, but you can verify this by looking at opentelemetry-swift URLSession instrumentationNote:
You'll need to expose opbeans-dotnet in docker-compose.yml (in apm-integration-testing):
to
then
docker-compose up -d
The text was updated successfully, but these errors were encountered: