-
Notifications
You must be signed in to change notification settings - Fork 250
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
[website_docs] fix broken links, copyedits and file renames #1120
[website_docs] fix broken links, copyedits and file renames #1120
Conversation
|
||
[Manual Instrumentation][manual-instrumentation] will give provide you the ability to enrich your traces with domain specific data. | ||
|
||
[Automatic Instrumentation][auto-instrumentation] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cartermp - this entire page talks about automatic instrumentation and that same link is given elsewhere in the page, so it seemed odd to me to mention it again here in the list of "more things to look into". Hence, I removed the reference. Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me.
[Context Propagation][context-propagation] is perhaps one of the most powerful concepts in OpenTelemetry because it will upgrade your single service trace into a _distributed trace_, which makes it possible for OpenTelemetry vendors to visualize a request from end-to-end across process and network boundaries. | ||
|
||
[Span Events][events] allow you to add a human-readable message on a span that represents "something happening" during its lifetime. | ||
|
||
[Manual Instrumentation][manual-instrumentation] will give provide you the ability to enrich your traces with domain specific data. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cartermp - note that I converted these paragraphs into a list.
(fyi maintainers - I hit approve since I think @chalin's changes make sense w.r.t. what we're doing with docs all-around. I recognize that this requires your approval to move forward 🙂) |
instrumentation
qualifier opentelemetry.io#997With these changes, the OTel website build is successful (i.e., #1104 is fixed):
/assign @cartermp
/cc @austinlparker