You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Nick Dimiduk <nd...@apache.org> on 2020/05/13 21:41:07 UTC
[DISCUSS] Separate web access logs
Heya,
Looks like since HBASE-24310 we have nicely formatted logs of access to our
WebUI endpoints, following a standard web server log format. I think it'll
be a common requirement for environments to process these logs following
standard processes for web servers, so I think we should document how to
separate them out to their own dedicated file, thus HBASE-24366. However,
I'm wondering if we should make the separate file as the default
configuration. Are there different answers to this question for 2.x vs. 3.0
releases?
Maybe you're a lurking operator who has opinions about this? Please speak
up! :D
Thanks,
Nick
Re: [DISCUSS] Separate web access logs
Posted by Nick Dimiduk <nd...@apache.org>.
Sorry Duo, I missed your reply.
Yes, I think that's fine with me. We can change the default log4j to
silence this logger by default and include commented guidance for enabling
it.
On Wed, May 13, 2020 at 7:08 PM 张铎(Duo Zhang) <pa...@gmail.com> wrote:
> For now the default config is just disable the access log?
>
> No sure if it is useful to output these access logs as for me I do not care
> the access to status pages too much...
>
> Nick Dimiduk <nd...@apache.org> 于2020年5月14日周四 上午6:20写道：
>
> > Having read through a region server log with this feature enabled,
> looking
> > to diagnose another issue, I'm going to change my tone. I think having
> > these messages in the standard server log is too noisy, makes them even
> > harder to read. In my case, it looks like automation is pinging the /jmx
> > endpoint on a regular basis, and we're seeing those interaction here.
> >
> > So, I propose we change the default configuration to ship these logs to a
> > dedicated access.log.
> >
> > On Wed, May 13, 2020 at 2:41 PM Nick Dimiduk <nd...@apache.org>
> wrote:
> >
> > > Heya,
> > >
> > > Looks like since HBASE-24310 we have nicely formatted logs of access to
> > > our WebUI endpoints, following a standard web server log format. I
> think
> > > it'll be a common requirement for environments to process these logs
> > > following standard processes for web servers, so I think we should
> > document
> > > how to separate them out to their own dedicated file, thus HBASE-24366.
> > > However, I'm wondering if we should make the separate file as the
> default
> > > configuration. Are there different answers to this question for 2.x vs.
> > 3.0
> > > releases?
> > >
> > > Maybe you're a lurking operator who has opinions about this? Please
> speak
> > > up! :D
> > >
> > > Thanks,
> > > Nick
> > >
> >
>
Re: [DISCUSS] Separate web access logs
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
For now the default config is just disable the access log?
No sure if it is useful to output these access logs as for me I do not care
the access to status pages too much...
Nick Dimiduk <nd...@apache.org> 于2020年5月14日周四 上午6:20写道：
> Having read through a region server log with this feature enabled, looking
> to diagnose another issue, I'm going to change my tone. I think having
> these messages in the standard server log is too noisy, makes them even
> harder to read. In my case, it looks like automation is pinging the /jmx
> endpoint on a regular basis, and we're seeing those interaction here.
>
> So, I propose we change the default configuration to ship these logs to a
> dedicated access.log.
>
> On Wed, May 13, 2020 at 2:41 PM Nick Dimiduk <nd...@apache.org> wrote:
>
> > Heya,
> >
> > Looks like since HBASE-24310 we have nicely formatted logs of access to
> > our WebUI endpoints, following a standard web server log format. I think
> > it'll be a common requirement for environments to process these logs
> > following standard processes for web servers, so I think we should
> document
> > how to separate them out to their own dedicated file, thus HBASE-24366.
> > However, I'm wondering if we should make the separate file as the default
> > configuration. Are there different answers to this question for 2.x vs.
> 3.0
> > releases?
> >
> > Maybe you're a lurking operator who has opinions about this? Please speak
> > up! :D
> >
> > Thanks,
> > Nick
> >
>
Re: [DISCUSS] Separate web access logs
Posted by Nick Dimiduk <nd...@apache.org>.
Having read through a region server log with this feature enabled, looking
to diagnose another issue, I'm going to change my tone. I think having
these messages in the standard server log is too noisy, makes them even
harder to read. In my case, it looks like automation is pinging the /jmx
endpoint on a regular basis, and we're seeing those interaction here.
So, I propose we change the default configuration to ship these logs to a
dedicated access.log.
On Wed, May 13, 2020 at 2:41 PM Nick Dimiduk <nd...@apache.org> wrote:
> Heya,
>
> Looks like since HBASE-24310 we have nicely formatted logs of access to
> our WebUI endpoints, following a standard web server log format. I think
> it'll be a common requirement for environments to process these logs
> following standard processes for web servers, so I think we should document
> how to separate them out to their own dedicated file, thus HBASE-24366.
> However, I'm wondering if we should make the separate file as the default
> configuration. Are there different answers to this question for 2.x vs. 3.0
> releases?
>
> Maybe you're a lurking operator who has opinions about this? Please speak
> up! :D
>
> Thanks,
> Nick
>