Am 8. Januar 2025 15:51:31 MEZ schrieb Jim Jagielski <j...@jagunet.com>:
>
>
>> On Jan 8, 2025, at 9:17 AM, Edson Alves Pereira <eap.eapere...@gmail.com>
>> wrote:
>>
>> I wanted something built-in with apache which would not need a third party
>> tool.
>>
>> On Wed, Jan 8, 2025 at 11:10 AM Eric Covener <cove...@gmail.com
>> <mailto:cove...@gmail.com>> wrote:
>>> On Wed, Jan 8, 2025 at 8:41 AM Edson Alves Pereira
>>> <eap.eapere...@gmail.com <mailto:eap.eapere...@gmail.com>> wrote:
>>> >
>>> > Hello guys, I´d like to add a Rolling Log feature to Apache Web Server,
>>> > some like if the user add:
>>> >
>>> > RollingLog = true
>>> >
>>> > on httpd.conf, Apache will automatically add ( -YYYYMMDD ) to the end of
>>> > log´s file name.
>>>
>>> People commonly use rotatelogs / piped logging and OS facilities like
>>> logrotated which are both pretty flexible.
>>> Why another way?
>
>
>
>Would love to see it. I can see how some would prefer something built in.
OTOH under Linux, you can use systemd to start httpd and use /dev/stdout as log
target and use journald to capture the access logs.
Same for container use case, access log will probably always get directed to
stdout and taken care of logging systems like fluentd or fluentbit or similar.
A JSON output support for access logs would be really helpful in this
constellation... :-)
Not sure what OS is mostly used by httpd, but probably Linux and most distros
are systemd based and already offer a superior logging system with journald,
but YMMV.
>
>--
>Jim
> "I don't need a compass to tell me which way the wind shines."
>
>
>
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
