You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's almost perfect, but the Nginx log format uses a slightly different date format: 127.0.0.1 - - [16/Dec/2024:14:41:54 +0000] "GET /api/users/me HTTP/1.1" 200 0 "-" "-"
However, I was wondering if we could align the format with NGINX/Apache by default, as it can enhance compatibility across the ecosystem without much trouble! 🤔
This discussion was converted from issue #465 on January 20, 2025 14:26.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi there 👋,
I was setting up Netdata on my side and noticed that it's compatible with Apache and NGINX log formats.
While configuring, I set the log format as follows:
--access-log-fmt '%(addr)s - - [%(time)s] "%(method)s %(path)s %(protocol)s" %(status)d 0 "-" "-"'
This outputs:
127.0.0.1 - - [2024-12-16 14:34:34 +0000] "GET /api/users/me HTTP/1.1" 200 0 "-" "-"
It's almost perfect, but the Nginx log format uses a slightly different date format:
127.0.0.1 - - [16/Dec/2024:14:41:54 +0000] "GET /api/users/me HTTP/1.1" 200 0 "-" "-"
I've created a custom formatter on my side:
However, I was wondering if we could align the format with NGINX/Apache by default, as it can enhance compatibility across the ecosystem without much trouble! 🤔
Just a suggestion, feel free to close it 😋
Beta Was this translation helpful? Give feedback.
All reactions