You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Julie Sheffield (JIRA)" <ji...@apache.org> on 2010/09/18 02:08:37 UTC

[jira] Created: (LOG4NET-267) Added overload to RemoteLoggingServerPlugin to allow callers to pass in an additional logger to use if the number of errors goes over a specified threshold

Added overload to RemoteLoggingServerPlugin to allow callers to pass in an additional logger to use if the number of errors goes over a specified threshold
-----------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: LOG4NET-267
                 URL: https://issues.apache.org/jira/browse/LOG4NET-267
             Project: Log4net
          Issue Type: Improvement
          Components: Other
    Affects Versions: 1.2.10
         Environment: N/A (compiled against .NET 2.0)
            Reporter: Julie Sheffield
            Priority: Minor
             Fix For: v.Next


I had a requirement for my project that the ops team be notified every time the number of error-level or higher alerts logged system-wide was more than a certain threshold in any given day.  (i.e. notify ops after every 25 errors, but reset the count every day, so there might be multiple notifications on a single day if the error log were getting flooded, but a few errors per day will not raise the alarm.)  I think this might be of use for other people's projects as well, so I thought I would contribute the code.  To use it, the service calling the remote sink would pass in a named logger and a threshold to an overloaded constructor.  If no logger is passed in to the constructor, the plugin will use its original behavior with no performance implication beyond one check for null.

Please see attached code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (LOG4NET-267) Added overload to RemoteLoggingServerPlugin to allow callers to pass in an additional logger to use if the number of errors goes over a specified threshold

Posted by "Julie Sheffield (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LOG4NET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julie Sheffield updated LOG4NET-267:
------------------------------------

    Attachment: RemoteLoggingServerPlugin.cs

Code allowing callers of the plugin to specify an additional logger to log errors to after every specified number of messages per day

> Added overload to RemoteLoggingServerPlugin to allow callers to pass in an additional logger to use if the number of errors goes over a specified threshold
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-267
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-267
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Other
>    Affects Versions: 1.2.10
>         Environment: N/A (compiled against .NET 2.0)
>            Reporter: Julie Sheffield
>            Priority: Minor
>             Fix For: v.Next
>
>         Attachments: RemoteLoggingServerPlugin.cs
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> I had a requirement for my project that the ops team be notified every time the number of error-level or higher alerts logged system-wide was more than a certain threshold in any given day.  (i.e. notify ops after every 25 errors, but reset the count every day, so there might be multiple notifications on a single day if the error log were getting flooded, but a few errors per day will not raise the alarm.)  I think this might be of use for other people's projects as well, so I thought I would contribute the code.  To use it, the service calling the remote sink would pass in a named logger and a threshold to an overloaded constructor.  If no logger is passed in to the constructor, the plugin will use its original behavior with no performance implication beyond one check for null.
> Please see attached code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.