-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 query logging/tracing #1706
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue/PR has been automatically marked as stale because it has not had recent activity. Please comment on status otherwise the issue will be closed in a week. Thank you for your contributions. |
We need that!
…On Thu, 27 Feb 2020 at 11:14, stale[bot] ***@***.***> wrote:
This issue/PR has been automatically marked as stale because it has not
had recent activity. Please comment on status otherwise the issue will be
closed in a week. Thank you for your contributions.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#1706?email_source=notifications&email_token=ABVA3O55SFMX6J4FJ6D4FSDRE6OCTA5CNFSM4JH2VRSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEND65SY#issuecomment-591916747>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVA3O7MH2CTC5GVIGGAUYDRE6OCTANCNFSM4JH2VRSA>
.
|
This issue/PR has been automatically marked as stale because it has not had recent activity. Please comment on status otherwise the issue will be closed in a week. Thank you for your contributions. |
Still needed, no progress on this yet. Help wanted! @mkabischev did something promising! |
Tracing is done, but we might want to log more on debug. |
This was merged: grpc-ecosystem/go-grpc-middleware#223 so we might want to think about upgrading middleware and getting this in. However the current version is not fully correct on middleware sides, the |
valgrind-out.txt |
Small feedback as a tracing user : It's working great and it's a really useful tool to troubleshoot our Thanos architecture. |
Is this issue grpc-ecosystem/go-grpc-middleware#275 a blocker for solving #1706(Query Logging)? |
Well not blocker, just some dependency we need to work on. I am maintainer on grpc middleware, as well, so yea we might want to push something forward. TBH the v2 is mainly done so we can just try upgrade Thanos to that (: (just some minor import tweaks I need to fix first, probably tomorrow) |
Still an issue |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Let's get back to this since @aymericDD want to help in this. Let's figure out what exactly is missing. Sounds to me like tracing is done. But logging might need more metadata/better usability.
Feel free @aymericDD to give more details on what's your current problem is. |
Let's make sure we reuse exactly the same statistics and metadata as for tracing. |
Some starting point: thanos/pkg/server/grpc/grpc.go Line 85 in 24602c4
|
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
Still an issue |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
#5521 done |
We should log queries and preserve those optionally in tracing. This is to clearly figure out which query caused unexpected behavior or hit limit!
Nice to have: middleware logging: grpc-ecosystem/go-grpc-middleware#223 cc @adrien-f (: Although we can host something temporarily.
Related Prometheus issue: prometheus/prometheus#6223
AC :
The text was updated successfully, but these errors were encountered: