Disable logging of GET /notification_recipients

My email history search failed but I think there is a way to disable
logging of certain api routes; anyone know how?

I'd like to suggest that we disable the logging of

2017-01-24T22:51:22 9e5f9d73 [app] [I] Started GET
"/notification_recipients" for 127.0.0.1 at 2017-01-24 22:51:22 +0000
2017-01-24T22:51:22 9e5f9d73 [app] [I] Processing by
NotificationRecipientsController#index as / 2017-01-24T22:51:22 9e5f9d73
[app] [D] Setting current user thread-local variable to admin
2017-01-24T22:51:23 9e5f9d73 [app] [D] Body: {"notifications":[],"total":0}
2017-01-24T22:51:23 9e5f9d73 [app] [I] Completed 200 OK in 26ms (Views:
0.3ms | ActiveRecord: 0.9ms)

since my log will be about 99% that after a weekend afk.

Thoughts?

> My email history search failed but I think there is a way to disable
> logging of certain api routes; anyone know how?
>
> I'd like to suggest that we disable the logging of
>
> 2017-01-24T22:51:22 9e5f9d73 [app] [I] Started GET
> "/notification_recipients" for 127.0.0.1 at 2017-01-24 22:51:22 +0000
> 2017-01-24T22:51:22 9e5f9d73 [app] [I] Processing by
> NotificationRecipientsController#index as / 2017-01-24T22:51:22
> 9e5f9d73 [app] [D] Setting current user thread-local variable to admin
> 2017-01-24T22:51:23 9e5f9d73 [app] [D] Body: {"notifications":[],"total":0}
> 2017-01-24T22:51:23 9e5f9d73 [app] [I] Completed 200 OK in 26ms (Views:
> 0.3ms | ActiveRecord: 0.9ms)
>
> since my log will be about 99% that after a weekend afk.
>

there are two redmine issues that will probably help reducing it, [1] and
[2]. bottom line, it should only request notifications when the user
session is active and idle time out did not met, I'm uncreatain we should
disable logging as it can lead to other surprises down the road… I do
agree that long term we want to move away from pulling to websocket based
notifications.

Ohad

[1] Bug #18191: notification should not keep initiating new pull requests when there is an active request - Foreman
[2] Bug #18192: notification should not keep fetching events when timeout occured - Foreman

··· On Wed, Jan 25, 2017 at 12:52 AM, Tom McKay wrote:

Thoughts?


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Those two issues are useful but don't really address what I see. I don't
need the server being hammered for notifications every 10 seconds. Some
scaling back would be very welcome.

#18438 is Bug #18438: Allow adjusting notification checking period - Foreman "Bug #18438: Allow adjusting
notification checking period - Foreman"

··· On Wed, Jan 25, 2017 at 1:49 AM, Ohad Levy wrote:

On Wed, Jan 25, 2017 at 12:52 AM, Tom McKay thomasmckay@redhat.com > wrote:

My email history search failed but I think there is a way to disable
logging of certain api routes; anyone know how?

I’d like to suggest that we disable the logging of

2017-01-24T22:51:22 9e5f9d73 [app] [I] Started GET
"/notification_recipients" for 127.0.0.1 at 2017-01-24 22:51:22 +0000
2017-01-24T22:51:22 9e5f9d73 [app] [I] Processing by
NotificationRecipientsController#index as / 2017-01-24T22:51:22
9e5f9d73 [app] [D] Setting current user thread-local variable to admin
2017-01-24T22:51:23 9e5f9d73 [app] [D] Body: {“notifications”:[],“total”:0}
2017-01-24T22:51:23 9e5f9d73 [app] [I] Completed 200 OK in 26ms (Views:
0.3ms | ActiveRecord: 0.9ms)

since my log will be about 99% that after a weekend afk.

there are two redmine issues that will probably help reducing it, [1] and
[2]. bottom line, it should only request notifications when the user
session is active and idle time out did not met, I’m uncreatain we should
disable logging as it can lead to other surprises down the road… I do
agree that long term we want to move away from pulling to websocket based
notifications.

Ohad

[1] Bug #18191: notification should not keep initiating new pull requests when there is an active request - Foreman
[2] Bug #18192: notification should not keep fetching events when timeout occured - Foreman

Thoughts?


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.