As Gary already mentioned you really should consider using Log4j’s dynamic
reloading of the configuration along with support for composite configurations.
I am using this at storing our log4j configuration files in a Spring Cloud
Configuration Server backed by Git. We have a common log4j2.xml th
The script filters are already dynamic for script engines. Have you looked at
that?
Matt Sicker
> On Oct 22, 2021, at 03:22, Gary Gregory wrote:
>
> Why not reuse the feature that lets log4j automatically reload a
> configuration file if it detects the file has changed?
>
> Then we only have
Why not reuse the feature that lets log4j automatically reload a
configuration file if it detects the file has changed?
Then we only have to consider what kind of configuration is needed.
Gary
On Fri, Oct 22, 2021, 02:18 Adwait Kumar Singh <
theadvaitkumarsi...@gmail.com> wrote:
> This is a sam
This is a sample Rule I had in mind,
{
> "loggerThresholds": {
> "a.b.c.Class1": "WARN",
> "a.b.c.Class2": "TRACE",
> "a.b.c.Class3": "OFF"
> },
> "allowlistedHosts": [
> "a.b.c.us-west-1.com",
> "a.b.c.us-west-2.com"
> ],
> "ruleValidityTime": "2022-01-24T00:03:31.59
After thinking about this more I can’t quite figure out what the user would be
specifying in the configuration. A Java lambda expression? I.e what is the rule
syntax? Or are they expected to just configure predefined rules with perhaps
some variables. But if that is the case how is this really a
This sounds interesting. I might give it a whirl but firstI am trying to
finish up some work on
Apache Flume so it can get a new release and I need to do some other work here
as we
are overdue for a release.
Ralph
> On Oct 21, 2021, at 11:28 AM, Adwait Kumar Singh
> wrote:
>
> The problem
The problem I am stuck on is the best way to get the user to provide the
ruleSupplier via configuration.
On Thu, Oct 21, 2021 at 11:55 PM Adwait Kumar Singh <
theadvaitkumarsi...@gmail.com> wrote:
> Yes I mean filtering on those loggers.
>
> I don't expect the Supplier to be dynamically changed,
Yes I mean filtering on those loggers.
I don't expect the Supplier to be dynamically changed, only the rules they
are fetching. Something roughly like this
public class RuleBaseFilter extends AbstractFilter {
//This will be initialized only once
Supplier> rulesSupplier;
@Override
Sorry, you have lost me a little bit.
When you say dynamically turn on/off loggers I am assuming you really mean
enable/disable filtering on those Loggers?
Are you thinking that the rules can be added or removed dynamically? Or just
the
parameters to the rules? I ask because you can’t really
This is still in the proof of concept phase, but what I am trying to do is
create a filter which allows developers to dynamically turn on/off loggers
based on some parameters without restarting their system. The parameters
can be varied, like:
1. Turn on WARN log levels of a particular class.
2. Tu
It sounds to me like you want to create a new type of plugin similar to
PatternConerters. I am curious as to what your filter does. Is it something
that would be useful to others so that we would be interested in including it?
Ralph
> On Oct 21, 2021, at 6:07 AM, Adwait Kumar Singh
> wrote:
>
I am creating a filter which requires the user to give a Supplier to
fetch some custom rules. I am wondering how to go about getting this
Supplier from the configuration xml.
One way I have thought of is using some sort of Registry and then just
asking the user to provide a key to lookup into the
12 matches
Mail list logo
