We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Currently, logs from the server itself are not formatted as a JSON as the other applications logs as noticed by @jsoriano in #1103
For instance:
{"log.level":"info","@timestamp":"2023-10-25T17:43:33.554Z","log.logger":"http","message":"HEAD / HTTP/2.0","source.address":"172.17.0.1","http.request.method":"HEAD","url.path":"/","url.domain":"localhost","http.response.code":200,"http.response.body.bytes":72,"event.duration":29288,"source.ip":"172.17.0.1","user_agent.original":"curl/7.81.0","url.port":8080,"ecs.version":"1.6.0"} 2023/10/25 17:43:39 http: TLS handshake error from 172.17.0.1:53032: remote error: tls: protocol version not supported 2023/10/25 17:43:43 http: TLS handshake error from 172.17.0.1:37008: remote error: tls: protocol version not supported
It would be great that all logs were formatted using the same logger if possible.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, logs from the server itself are not formatted as a JSON as the other applications logs as noticed by @jsoriano in #1103
For instance:
It would be great that all logs were formatted using the same logger if possible.
The text was updated successfully, but these errors were encountered: