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

Enforce HTTP instrumentation functionality #525

Closed
ivantopo opened this issue Mar 31, 2018 · 2 comments
Closed

Enforce HTTP instrumentation functionality #525

ivantopo opened this issue Mar 31, 2018 · 2 comments

Comments

@ivantopo
Copy link
Contributor

There are a number of features that we are definitely going to provide for all HTTP instrumentation modules:

  • Context Propagation.
  • Distributed Tracing, which builds on top of the previous feature.
  • Metrics based on the Spans created for DT.

But there is now way at the moment to enforce that at least certain span and metric tags are present on all integrations. One thing that is worth noting is Brave's HttpTracing which kind of resonates with what I think we should have, just with a broader scope.

@ivantopo
Copy link
Contributor Author

Related to this: kamon-io/kamon-play#31

@ivantopo
Copy link
Contributor Author

I'm closing this issue because it is either too old to be relevant or stale. Stop by our Github Discussions section and drop a message if you need any additional help with the topic.

Have a nice day!

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

No branches or pull requests

1 participant