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.

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

feat: add dependency ID to az key vault dependency tracking #251

Conversation

stijnmoreels
Copy link
Member

Add dependency ID method overload for tracking Azure Key Vault dependencies.

Relates to #243

@netlify
Copy link

netlify bot commented Nov 2, 2021

✔️ Deploy Preview for arcus-observability ready!

🔨 Explore the source changes: 2f13d09

🔍 Inspect the deploy log: https://app.netlify.com/sites/arcus-observability/deploys/61d7f4953baf0700081b6d7e

😎 Browse the preview: https://deploy-preview-251--arcus-observability.netlify.app

### Making it easier to link services

Service-to-service correlation requires linkage between tracked dependencies (outgoing) and requests (incoming).
Tracking any kind of dependency with the library has the possibility to provide an dependency ID. This ID will be needed later when the incoming request is tracked (dependency ID = request's parent ID).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Tracking any kind of dependency with the library has the possibility to provide an dependency ID. This ID will be needed later when the incoming request is tracked (dependency ID = request's parent ID).
Tracking any kind of dependency with the library has the possibility to provide a dependency ID. This dependency ID will be needed later when the incoming request is tracked (dependency ID = request's parent ID).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure how to interpret the last sentence ? The (dependency) ID is needed later when the incoming request is tracked. You mean that the dependencyId is used in the logging of the downstream dependency to correlate the request id with the dependency id ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, something like that. Maybe we should specify that the 'later' part is in the other dependency.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the last sentence with a more thorough explanation. We also need to update the links but that can only be done when #250 is done.

@fgheysels
Copy link
Member

I think some things need to be clarified in the docs before we can merge this.

@stijnmoreels
Copy link
Member Author

I think some things need to be clarified in the docs before we can merge this.

Besides the open comment, something else?

@fgheysels fgheysels assigned stijnmoreels and unassigned fgheysels Jan 6, 2022
Copy link
Member

@fgheysels fgheysels left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, but I think I'd remove the secretname & keyvaulturi validation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants