Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(❗) docs: fix webapi userguide correlation ids #465

Merged
merged 2 commits into from
Sep 2, 2022
Merged

(❗) docs: fix webapi userguide correlation ids #465

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a78ecdc
docs: fix webapi userguide correlation ids
stijnmoreels Sep 2, 2022
8082d55
Update use-service-to-service-correlation-in-web-api.md
stijnmoreels Sep 2, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions ...Service-to-service Correlation/use-service-to-service-correlation-in-web-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ The following list shows each step in the diagram:
5. Service B responds to service A with the same information as the call to service B.
6. The user receives both the **transaction ID** and **operation parent ID** in their final response.

> Additional configuration is available to tweak this functionality, see the [dedicated Arcus Web API feature documentation](https://webapi.arcus-azure.net/features/correlation) for more in-depth information on HTTP correlation.
> 💡 Additional configuration is available to tweak this functionality, see the [dedicated Arcus Web API feature documentation](https://webapi.arcus-azure.net/features/correlation) for more in-depth information on HTTP correlation.

## API Demonstration
In this user-guide, two fictive API applications will be used to represent Service A and Service B of the diagram. Both services will be adapted to use service-to-service correlation.
Expand Down Expand Up @@ -288,8 +288,8 @@ curl -Method POST `
-Body '{ "ProductName": "Fancy desk", "Amount": 3 }'

// StatusCode : 202
// Headers: : X-Transaction-ID=8a622f
// X-Operation-ID=8a622fa4-a757-47a0-9db9-e22d00328087
// Headers: : X-Transaction-ID=8a622fa4-a757-47a0-9db9-e22d00328087
// X-Operation-ID=05353d3b-de3f-44e6-90cb-9a622884f290
```

The real result, though, happens in Application Insights.
Expand All @@ -313,4 +313,5 @@ In this user guide, you've seen how the Arcus HTTP correlation functionality can
* Observability blogs
* [Announcing Arcus Observability](https://www.codit.eu/blog/announcing-arcus-observability/)
* [Measure a Variety of Azure Dependencies with Observability v0.2](https://www.codit.eu/blog/measure-a-variety-of-azure-dependencies-with-observability-v0-2/)
* [Service Correlation Preparation & .NET 6 Support in Arcus Observability v2.4](https://www.codit.eu/blog/service-correlation-preparation-net-6-support-in-arcus-observability-v2-4/)
* [Service Correlation Preparation & .NET 6 Support in Arcus Observability v2.4](https://www.codit.eu/blog/service-correlation-preparation-net-6-support-in-arcus-observability-v2-4/)
* [Service-to-Service Correlation, One of the Biggest Arcus Features in Observability v2.5](https://www.codit.eu/blog/service-to-service-correlation-one-of-the-biggest-arcus-features-in-observability-v2-5/)