-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
access log: support generic protocol #13085
Comments
See
|
|
This seems a valid feature request but need design proposal. @mattklein123 the extension filter is about how we filter log entries, but it doesn't let access log support generic protocol, other than TCP / HTTP. @cpakulski was looking into how to integrate MySQL logs (e.g. transaction logs which is in different layers than TCP), we saw same issue with current logging structure including ALS. It makes sense to have some extensible way to let TCP filters to emit custom logs easily (to access logger extensions, file/gRPC/etc). |
I agree. We actually need access logs for the DNS filter also at Lyft (cc @abaptiste) so whatever we come up with here can be used for that. Naively I would think that the general HTTP/TCP system should work with possible protocol specific data extensions? |
I am working on a prototype. The idea is to emit fairly flexible messages describing non-HTTP transactions, like database interactions. I could not fit them into gRPC message, as it is very HTTP specific. |
add ref to #14175 , which might be related to this issue |
Is there any progress here ? GRPC does make this problem very complex. Perhaps we could start by creating a generic file access logger for none HTTP protocol and gradually extend it to other access loggers such as GRPC. |
Title: access log: support generic protocol
Description:
I want to add access log support for dubbo and thrift filter, but find out current access log formatter only support TCP / HTTP, and it cannot be extended. Any thoughts about implement a generic access log formatter ?
Thanks !
The text was updated successfully, but these errors were encountered: