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.

Sign up for GitHub

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

Jump to bottom

[QUESTION] may be a bug of proxied_response_duration_seconds metric #410

Open
gogodjzhu opened this issue Mar 14, 2024 · 1 comment
Open

[QUESTION] may be a bug of proxied_response_duration_seconds metric #410

gogodjzhu opened this issue Mar 14, 2024 · 1 comment

Comments

@gogodjzhu
Copy link

Which feature your question relates to?
I would like to inquire about the feature related to the metric proxied_response_duration_seconds, which is described as 'Response duration proxied from ClickHouse'. I believe this metric is intended to monitor the actual duration of each request from chproxy to ClickHouse. However, upon reviewing the code, I find it to be unconventional.

Question details
Could you please provide clarification regarding the code found at

chproxy/proxy.go

Line 264 in b4ef8e0

monitorDuration(since)
?

Additional context/motivations
I am seeking to understand if there might be a bug in the code or if there is a misunderstanding regarding the usage of the mentioned metric. Your insights would be greatly appreciated.
@shivagupta-byte
Copy link

we are not even getting this metric in prometheus, is this a known bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gogodjzhu @shivagupta-byte