-
Notifications
You must be signed in to change notification settings - Fork 999
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
Unify internal observability documentation - 1 of 3 #4246
Conversation
Still lots to do. Will start working on the content tomorrow. |
Thanks again, @tiffany76 ! Let us know when you want us to run a first review pass. |
/fix:refcache |
You triggered fix:refcache action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/8576259476 |
Ready for review! Make sure to view the preview because the rich diff doesn't render the tabbed panes. :) |
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.
Excellent work!
I'd place this document as a sub-doc for Troubleshooting. WDYT @svrnm ?
Co-authored-by: Fabrizio Ferri-Benedetti <fferribenedetti@splunk.com> Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
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.
LGTM!
I agree. Profiling looks out of the scope of this work. It may be even better to utilize profiling once it's part of OTel as a new signal. |
So, looks like we're almost there? Only thing to be resolved is the Grafana dashboard question, right? |
I just saw that my comments on that matter where still "pending", just submitted them! |
Co-authored-by: Severin Neumann <severin.neumann@altmuehlnet.de>
@svrnm I think this one is ready, but please let me know if you find any other changes I should make. Thanks! |
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.
Thank you so much @tiffany76! Let's ship it :)
Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
🎉 thank you @tiffany76 |
Self-monitoring is a risky practice. If an issue arises, the source of the | ||
problem is unclear and the telemetry is unreliable. |
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.
Late to the party, but this caution text doesn't make sense / is incomplete.
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.
I changed the caution text in #4322. Please let me know if the new alert makes more sense.
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.
Great, thanks! I'll add comments, if any in #4322.
Link to tracking issue: open-telemetry/opentelemetry-collector#8886.
Relates to #4192. For ease of review, that larger PR is being split into three smaller ones. This is the first of three.
This PR addresses the first section of a new internal observability document on opentelemetry.io:
Follow up PRs (2 and 3 of 3) will be created once this one is merged.
cc: @mx-psi @codeboten @theletterf @svrnm
Preview: https://deploy-preview-4246--opentelemetry.netlify.app/docs/collector/internal-telemetry/