allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <d...@brondsema.net>
Subject [allura:tickets] Ticket 3938 discussion
Date Wed, 31 Aug 2016 14:38:03 GMT
- **labels**:  --> cleanup
- **summary**: Stats logging should not go to the "console" handler --> Stats logging should
not go to the "console" handler; remove it
- **Comment**:

I think the `h.log_action` code and related logging configuration can be removed completely.
 The activity stream is a better way to keep track of actions.  And `/rest/` api activity
in specific generates a lots of unnecessary log entries now.



---

** [tickets:#3938] Stats logging should not go to the "console" handler; remove it**

**Status:** open
**Milestone:** unreleased
**Labels:** cleanup 
**Created:** Thu Mar 22, 2012 05:58 PM UTC by Dave Brondsema
**Last Updated:** Thu Mar 22, 2012 05:58 PM UTC
**Owner:** nobody


We use `h.log_action` in many places to log details about actions that happen.  In production.ini,
`handler_stats` is configured to write those details to a separate log file.  But they still
go to handler_console too.  To have them not go there, I think we need a the log_action events
to go to a different base logger (e.g. allura.stats) instead of whatever package logger is
there (e.g. allura.model.repo_refresh).  `class StatsHandler` filters by checking for an "action"
attribute on the event, but we need a simple way to separate them so that it can be adjusted
via the logging ini settings.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message