-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Query protocol and codebase for log type record #2449
Conversation
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.
In my opinion, query by traceId in the condition and included in the response would be more friendly to the user.
@JaredTan95 I will add it tomorrow. Any object? |
Okay. |
@TinyAllen Done. |
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
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.
Add a new page i think it is OK
I just created
http_access_log
metric, withqueryLogs
protocol, see GraphQL here.@peng-yongsheng @TinyAllen @liuhaoyang @hanahmily
This PR includes codebase only but would use it in any case. In the future, I may want to open a receiver for log collector, such as logstash, etc.
Do you think is it sensible to add traceId too for the future? Including in query protocol.
@TinyAllen
The query protocol is related to UI more, let's add some new page? maybe. Use could query logs through time, (service, instance, endpoint)IDs, status, response time(2xx,4xx,5xx are expected codes)
We need a discussion about this. If others thing traceid should be added, then I will adjust protocol.