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(godeltaprof): service info mapping injection #93

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

korniltsev
Copy link
Collaborator

No description provided.

)

const (
LabelNameServiceRepository = "service_repository"
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't think you need this.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I was going to add both mapping and labels in one PR, but decided to separate

Copy link
Contributor

@kolesnikovae kolesnikovae left a comment

Choose a reason for hiding this comment

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

It looks like only heap, mutex, and block profiles will have version info embedded into mapping.BuildID. Are we going to do same with CPU and goroutine profiles?

I'm wondering if we do really need/want to inject the version information into mappings:

  • Use of static labels is probably the most straight forward and convenient way for push mode.
  • In pull mode, we could implement a generic mechanism of metadata propagation through the HTTP response headers. Grafana Agent could extract the headers and inject them as series labels.

@korniltsev
Copy link
Collaborator Author

I like headers idea much more than the current PR mapping implementation. @cyriltovena wdyt ?

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.

None yet

3 participants