-
Notifications
You must be signed in to change notification settings - Fork 521
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
Add doc about long-running traces #3977
Conversation
@zalegrala Let me know when you want me to review. Thank you for adding doc! |
I'll take review any time @knylander-grafana. Do you have 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.
Thank you for adding the doc! A few minor suggestions, but otherwise looks good.
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'm good! nice addition
Co-authored-by: Joe Elliott <[email protected]>
Co-authored-by: Kim Nylander <[email protected]>
Co-authored-by: Kim Nylander <[email protected]>
Co-authored-by: Kim Nylander <[email protected]>
Co-authored-by: Kim Nylander <[email protected]>
Co-authored-by: Kim Nylander <[email protected]>
88b24d0
to
5a417c8
Compare
What this PR does:
Here we add a bit of doc to point folks at when they are using the long-running trace pattern.
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]