quot;David Lang"
To: "rsyslog-users"
Subject: [rsyslog] Question about maximum queue.workerthreads count
Date: Tue, Mar 10, 2015 5:30 PM
On Tue, 10 Mar 2015, Boylan, James wrote:
> Greetings everyone!
>
>
> Is there a hardcoded maximum number of worker threads for queues
Greetings everyone!
Is there a hardcoded maximum number of worker threads for queues and threads
for imtcp/imudp? Also what are the concerns with using a higher number of
threads for handling of these.
I find myself in a position to have to scale central logging servers vertically
and I'm at
yslog] re_extract does not support all regex
thx!
2015-01-28 14:47 GMT+01:00 Boylan, James :
> Sounds good!
>
> I'll create an issue and update it with all of the details. I'll add in
> the valgrind output as well once I have it.
>
> Thanks!
>
> -
[rsyslog] re_extract does not support all regex
Date: Wed, Jan 28, 2015 7:39 AM
2015-01-28 14:35 GMT+01:00 Boylan, James :
> Does anyone have any suggestions on this?
>
> I would suspect that I have just hit a limitation of the regex
> implementation in rsyslog except that it crashes w
James
--- Sent from my mobile phone ---
- Reply message -
From: "Boylan, James"
To: "rsyslog-users"
Subject: [rsyslog] re_extract does not support all regex
Date: Tue, Jan 27, 2015 2:45 PM
I was trying to use the regex '^[
]?.+?(?=\\|)\\|.+?(?=\\|)\\|.+?(?=\\
I was trying to use the regex '^[
]?.+?(?=\\|)\\|.+?(?=\\|)\\|.+?(?=\\^)\\^(.*)' with re_extract and found that
it would cause rsyslogd to crash on 8.4.2. However the pattern '^[
]?[A-Za-z0-9._-]+\\|[A-Za-z0-9._-]+\\|[A-Za-z0-9._-]+[\\^](.*)' works fine.
I didn't see anything specific in the d
Hey everyone -
As detailed in Github issue #146
(https://github.com/rsyslog/rsyslog/issues/146)
action.execOnlyWhenPreviousIsSuspended does not appear to be currently working.
Does anyone have an alternative method of addressing the use case where a
destination server ends up being down for a
Makes perfect sense!
-- James
From: rsyslog-boun...@lists.adiscon.com on
behalf of Rainer Gerhards
Sent: Tuesday, December 16, 2014 7:31 AM
To: rsyslog-users
Subject: Re: [rsyslog] master branch
2014-12-16 14:28 GMT+01:00 Boylan, James :
> A pract
ll check out.
On Tue, Dec 16, 2014 at 7:14 AM, Boylan, James wrote:
> If you are looking to shift that direction then 'master-ok' could work. Or
> 'master-tested'. Or even just 'stable' denoting that it has successfully had
> all testbench tests completed on
If you are looking to shift that direction then 'master-ok' could work. Or
'master-tested'. Or even just 'stable' denoting that it has successfully had
all testbench tests completed on it.
I think as long as it is documented in the readme.md file then you can really
name it whatever you feel wo
ent from my mobile phone ---
- Reply message -
From: "David Lang"
To: "rsyslog-users"
Subject: [rsyslog] Messages never leave suspended state
Date: Sun, Dec 14, 2014 8:14 PM
On Mon, 15 Dec 2014, Boylan, James wrote:
> The problem is that messages never seem to ever le
Hey all -
I've opened a Github issue on this
(https://github.com/rsyslog/rsyslog/issues/146) but I wanted to bring it up
here as well.
The problem is that messages never seem to ever leave a suspended state except
to resume on the action they were suspended on. I'm currently running on 8.4.2
This configuration defaults to 0. Doesn't this mean that if it can't send to a
destination it should not retry, it should just fail the message by default,
correct??
-- James
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
h
So I have been thinking, how badly would it impact performance and difficult
would it be to change the field() function so that instead of populating a
variable with *** FIELD NOT FOUND *** you could have that be default but give
the option to have it replace it something else? For example chang
I also have a python application I made for parsing the impstats file output
and submitting them to graphite.
I'm going to be working on daemonizing the utility and documenting how best to
configure to use it. Please feel free to look at it and open issues if you have
suggestions of features y
Sets are placed inside of the Ruleset block.
I generally place them at the top of the ruleset block so they get immediately
set before anything else is done and are nicely organized for when you want to
find them.
-- James
--- Sent from my mobile phone ---
- Reply message -
From: "sing
The only command line options I use consistently are -i, -f and -dn.
-- James
--- Sent from my mobile phone ---
- Reply message -
From: "Rainer Gerhards"
To: "rsyslog-users"
Subject: [rsyslog] anyone still using -s, -l rsyslog command line options?
Date: Mon, Nov 17, 2014 2:22 AM
Hi al
I think that the "permitEmpty=on" field is a reasonable starting place. I have
a config management app that I use with rsyslog that this field would help
significantly with.
-- James
--- Sent from my mobile phone ---
- Reply message -
From: "Rainer Gerhards"
To: "rsyslog-users"
Subjec
I've opened issue: https://github.com/rsyslog/rsyslog/issues/146 to track this.
Thanks for looking into it.
-- James
From: rsyslog-boun...@lists.adiscon.com on
behalf of Boylan, James
Sent: Wednesday, November 5, 2014 3:44 AM
To: rsyslog-users
Su
ssue.
-- James
--- Sent from my mobile phone ---
- Reply message -
From: "Rainer Gerhards"
To: "rsyslog-users"
Subject: [rsyslog] Issues with action.execOnlyWhenPreviousIsSuspended
Date: Wed, Nov 5, 2014 3:38 AM
2014-11-05 10:35 GMT+01:00 Boylan, James :
> Rainer -
sSuspended
Date: Wed, Nov 5, 2014 2:35 AM
James,
I suggest filing a bug on github. That way, I'll remember when I have time
again.
Thanks,
Rainer
2014-11-04 21:24 GMT+01:00 Boylan, James :
> I'm attempting to use this function, however when the first action is
> suspended, th
I'm attempting to use this function, however when the first action is
suspended, the follow up actions never seem to execute. It just sits in a
'Suspended' state forever. Any help on this would be appreciated since from
what I can tell it is configured the way it should be.
*.*
A lot of how this works depends on how many people are contributing. With a lot
of active contributors a common practice is to have a release branch and a
development branch. It makes it cleaner from a commit history when you can
squash many commits into a single one to push into the release bra
For the first scenario, it could be several things. A pastebin of the config
would help.
For the second, if you are using an appender I actually recommend urlencoding
the message payload. That will remove the multi-line issue completely and is
how we are currently handling our java logs, both o
I've been trying some more advanced changes in the use of omelasticsearch
lately, something that would be nice is the ability to use templates in the
searchType option like you can in the searchIndex option.
There is a lot of benefit of people using type specific features within
Elasticsearch.
the init environment (like
SELinux tags), if it fails, then it's something in the init script itself.
David Lang
On Sat, 6 Sep 2014, Boylan, James wrote:
> I've actually have this hang every time the init.d script starts, not just
> after a reboot. I'll be doing some final t
I've actually have this hang every time the init.d script starts, not just
after a reboot. I'll be doing some final tests with the older init.d script.
We'll see if it resolves it for me and if it does, I'll put together a PR for
it and we can see if it helps others with similar issues.
-- Jame
ithub rhel package
project and we will do that as soon as we can (probably end of next week).
Rainer
Sent from phone, thus brief.
Am 05.09.2014 16:52 schrieb "Boylan, James" :
> I'm having problems with 8.2.2 as installed with the RPMs in the Adiscon
> Repo. Its odd, but for som
I'm having problems with 8.2.2 as installed with the RPMs in the Adiscon Repo.
Its odd, but for some reason, when installed onto a CentOS 5 system, the yum
install hangs on Cleanup. On further investigation I have found that the init.d
script is hanging on startup and that if you manually run th
Rainer -
You can definitely define specific fields to be specific data types. Here is
teh Elasticsearch documetnation page on it. Look at the section for
'Customizing field mappings.'
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/mapping-intro.html
-- James
lf of Rainer Gerhards
> Sent: Friday, September 5, 2014 7:25 AM
> To: rsyslog-users
> Subject: Re: [rsyslog] Available global() Directives
>
> On Fri, Sep 5, 2014 at 1:14 PM, Boylan, James
> wrote:
>
>
>
> > > ?$MaxOpenFiles
> > >
> >
> > seem
, Boylan, James
wrote:
> Good morning everyone!
>
>
> I needed to verify if the following Legacy global directives had been
> migrated to the new global() configuration object.
>
>
> $RepeatedMsgReduction
>
not supported
> $OptimizeForUniprocessor
>
dead, does
Good morning everyone!
I needed to verify if the following Legacy global directives had been migrated
to the new global() configuration object.
$RepeatedMsgReduction
$OptimizeForUniprocessor
?$MaxOpenFiles
$umask
The aren't in the documentation and I just needed to verify.
Thanks!
-- Jame
From: rsyslog-boun...@lists.adiscon.com on
behalf of Boylan, James
Sent: Tuesday, August 12, 2014 8:43 AM
To: rsyslog-users
Subject: [rsyslog] rsyslog segfaults being experienced
So I'm changing the Subject on this to be more accurate in the hope that
someone else
So I'm changing the Subject on this to be more accurate in the hope that
someone else might have seen this behavior in the past. I admit that it has be
somewhat stumped. I have many client side instances of rsyslog running that is
collecting application longs then sending them to a central log s
cb1d190) at wti.c:313
#12 0x7f2a9bf1f4f2 in wtpWorker (arg=0x7f2a9cb1d190) at wtp.c:388
#13 0x7f2a9b88e851 in start_thread () from /lib64/libpthread.so.0
#14 0x7f2a9a51b90d in clone () from /lib64/libc.so.6
-- James
From: rsyslog-boun...@lists.adiscon.
Does anyone know off-hand if there were Segfault related bug fixes in the
linkedlist code after rsyslog 7.4.6? I've recently come acress a segfault that
has forced me to configure my Main Message Queue as a FixedArray to prevent it
from Segfaulting itself to death.
I'm aiming to start testing
-boun...@lists.adiscon.com] On Behalf Of Muhammad Asif
Sent: Friday, July 18, 2014 6:27 AM
To: rsyslog-users
Subject: Re: [rsyslog] Want to run python code using omprog on rsyslog 7.6.3
http://pastebin.com/WNDHhWLi
and
http://pastebin.com/6MRNWTRH
On Fri, Jul 18, 2014 at 4:17 PM, Boylan, James
wrote:
If possible it would be extremely helpful if you could start rsyslog with a -dn
option. Take the output of that and post it into pastebin for viewing.
Unfortunately with no output to go on, it is difficult to say definitively what
might be the problem.
Also, as Rainer has pointed out, omprog fo
All syslog daemons that act as system loggers run as root as far as I know. It
would be extremely hack-y to implement it otherwise and would likely create new
vulnerabilities far more dangerous than just running them as root.
-- James
- Reply message -
From: "Otis Gospodnetic"
To: "rsy
o: rsyslog-users
Subject: Re: [rsyslog] Has ActionExecOnlyWhenPreviousIsSuspended been updated
to the new config format?
James, sorry I don't understand the question. It does what it always did, at
least this is how it should be.
Rainer
Sent from phone, thus brief.
Am 19.05.2014 15:31
With all the work being done, I wasn't sure if this option had been updated yet
so I needed to check.
I'll be doing some testing with it shortly, but I figured if anyone knew
already they could let me know. I'll respond with the results of my testing
when I'm done.
-- James
___
Yes. To get access to the new configuration format you need to upgrade to at
least v7.
-- James
-- Sent from my mobile --
- Reply message -
From: "Mauricio Tavares"
To: "rsyslog-users"
Subject: [rsyslog] $ModLoad imtcp or module(load="imtcp")
Date: Fri, Mar 28, 2014 1:08 PM
CentOS 6.4
In my experience it uses the : separator assumption that is part of the older
RFC to try and guess what should be there.
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of Rainer Gerhards
Sent: Wednesday, March 26
I agree completely. This is a page I've looked for a lot as well. I'll work on
adding some links to v7 and up tonight.
-- James
-- Sent from my mobile --
- Reply message -
From: "David Lang"
To: "rsyslog-users"
Subject: [rsyslog] where is the current queue documentation?
Date: Mon, Mar
GMT+01:00 Michael Biebl :
> 2014-03-21 14:13 GMT+01:00 Boylan, James :
>> I've uploaded the current version of the documentation to the site.
>>
>> http://www.rsyslog.com/doc/v5-stable/
>> http://www.rsyslog.com/doc/v7-stable/
>> http://www.rsyslog.com/doc/v8
I've uploaded the current version of the documentation to the site.
http://www.rsyslog.com/doc/v5-stable/
http://www.rsyslog.com/doc/v7-stable/
http://www.rsyslog.com/doc/v8-stable/
http://www.rsyslog.com/doc/master/
This is of course still a work in progress. But if anyone sees something they
This is caused because the syslog payload as defined in the RFC expects a tag
separated by a : in the message payload. Since you don't have one it is
assuming everything before the first : is that tag and formatting it
accordingly.
-- James
-- Sent from my mobile --
- Reply message -
F
Is the version of omprog in 7.6.0 support the binary parameter with command
line options? From the current documentation it looks like it does, but I
wanted to confirm.
-- James
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslo
Also, if you are having DNS timeout issues but you are sending it to the same
place regularly, you might consider using NSCD. It will implement the DNS
caching for you if you are unable to upgrade to a newer version of rsyslog.
-- James
From: rsyslog-bou
Repairing the rainerscript section is a critical point in my opinion. It has a
lot of extremely useful features that need clarifying. It is one of the first
areas I'll be focusing on once the documentation is to a point where it is
formatted in a readable form.
-- James
-Original Message---
If we were to setup a URL for downloading the docs tarball, would it be
possible to pull that tarfile when you build a release tarfile instead of
including it in the git repo?
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.com
A short term note. If you go into the specific documentation version there is a
search window there that should allow for searching to a degree that will be
more and more accurate as I get formatting and updates to the documentation as
whole.
Definitely need to figure out why it isn't searchin
David called out a good point that needs clarified in the documentation.
In the documentation $RepeatedMsgReduction has a default state that specifies
'depending on -e' and when I finally found documentation on -e here:
http://manpages.ubuntu.com/manpages/hardy/man8/rsyslogd.8.html it specifies
Subject: Re: [rsyslog] [doc] Please take a look at imfile in rsyslog-doc's
v5-stable branch and give opinions
On Mon, Feb 17, 2014 at 3:07 PM, Michael Biebl wrote:
> 2014-02-17 14:52 GMT+01:00 Rainer Gerhards :
> > On Mon, Feb 17, 2014 at 2:33 PM, Boylan, James
> > >
7, 2014 8:08 AM
To: rsyslog-users
Subject: Re: [rsyslog] [doc] Please take a look at imfile in rsyslog-doc's
v5-stable branch and give opinions
2014-02-17 14:52 GMT+01:00 Rainer Gerhards :
> On Mon, Feb 17, 2014 at 2:33 PM, Boylan, James wrote:
>
>> Michael -
>>
>> Y
21:19 GMT+01:00 Boylan, James :
> If you see something, definitely let me know. What file are you seeing it in?
This typo is in source/index.rst
diff --git a/source/index.rst b/source/index.rst index b0967aa..d42b33a 100644
--- a/source/index.rst
+++ b/source/index.rst
@@ -23,7 +23,7 @@ rsys
: [rsyslog] [doc] Please take a look at imfile in rsyslog-doc's
v5-stable branch and give opinions
btw, can you commit a typo fix for "Compatability", please.
This one is starring at me every time I browse the new docs :-)
2014-02-14 20:30 GMT+01:00 Boylan, James :
> That we
ons
Looks great so far ! ;)
How about adding an overview of these manuals into
http://www.rsyslog.com/doc/newdoc/ ?
Best regards,
Andre Lorbach
> -Original Message-
> From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
> boun...@lists.adiscon.com] On Behalf Of Boylan, J
s well. :)
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of Boylan, James
Sent: Friday, February 14, 2014 8:48 AM
To: rsyslog-users
Subject: Re: [rsyslog] [doc] Please take a look at imfile in rsyslog-doc's
v5-stable
the
difference:
old: http://www.rsyslog.com/doc/imfile.html
new:
http://people.debian.org/~biebl/rsyslog-doc/configuration/modules/imfile.html
(Keep in mind that one is for v5 and the other is for v8)
It definitely looks better structured. Thanks for your work James!
2014-02-13 2:23 GMT+01:00 Boyl
I would definitely be interested is something like that. And the timing would
work well with a lot of US professionals as I'm sure most could classify it as
training time for work.
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adisco
mhdfs documentation
I think that was a yet-uncought copy&paste error.
Rainer
On Thu, Feb 13, 2014 at 12:59 AM, Boylan, James wrote:
> So in the documentation it has omhdfs labeled as Unix sockets Output
> Module. Is that accurate? Wouldn't Hadoop FileSystem Output Module be
>
Something I came across that might work for just getting the data backed up is
this: https://github.com/joeyh/github-backup
Now sure how versatile the tool is. But it's a starting point.
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.a
I have updated the format for imfile in the v5-stable rsyslog-doc branch. Could
someone please take time and check out that repo then compile using the
instructions to view the html? I'd like feedback on what everyone thinks of
that new layout for the imfile module.
-- James
___
So in the documentation it has omhdfs labeled as Unix sockets Output Module. Is
that accurate? Wouldn't Hadoop FileSystem Output Module be more accurate?
http://www.rsyslog.com/doc/omhdfs.html
I'll update the docs if needed.
-- James
___
rsyslog maili
Best news I've heard all day. Time to build out the new RPMs. :)
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of Rainer Gerhards
Sent: Wednesday, February 12, 2014 1:45 PM
To: rsyslog-users
Subject: Re: [rsyslog]
cool idea. Unfortunately, I don't have time to
do it immediately. It would be great if you could put the request into a
github issue (even better if you flag it as feature request ;)).
Thanks,
Rainer
On Wed, Feb 12, 2014 at 3:10 AM, Boylan, James wrote:
> Has any consideration been put into
Has any consideration been put into setting up omprog so that the program
spawns as another user? Something along the lines of:
*.* action(type="omprog"
binary="/path/to/binary --param1 lal
Is there a plan to release 7.5.x as v7-stable?
-- James
-- Sent from my mobile --
- Reply message -
From: "Rainer Gerhards"
To: "rsyslog-users"
Subject: [rsyslog] templates using local variables as a property
Date: Tue, Feb 11, 2014 2:42 PM
Right now, it's absolutely safe to consider t
Where can variables be used?
args, of course I meant to say "instead of the *set* you do the action()"...
On Tue, Feb 11, 2014 at 5:59 PM, Rainer Gerhards
wrote:
> what if instead of the if you do the action() inside those ifs?
>
>
> On Tue, Feb 11, 2014 at 5:39 PM,
ject: Re: [rsyslog] Where can variables be used?
On Tue, Feb 11, 2014 at 5:26 PM, Boylan, James wrote:
> I was afraid of that. I'm currently using 7.4.6, but it sounds like
> this functionality isn't available in even the newer versions yet? (If
> not I will probably be openi
discon.com
[mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of David Lang
Sent: Tuesday, February 11, 2014 10:23 AM
To: rsyslog-users
Subject: Re: [rsyslog] Where can variables be used?
On Tue, 11 Feb 2014, Boylan, James wrote:
> Is it possible to use $! variables in a situation like:
I agree with everyone else on this. Having a lot of issues active is not an
issue so long as there are still commits being done to the project and the
issues are being responded to and/or worked on.
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-bou
Is it possible to use $! variables in a situation like:
# Forward to Archive
*.*
action(name="currAppLog.port-21516.archive"
type="omfwd"
Which version of rsyslog was the ability for 'if' to parse
(field($timegenerated,':',3) % 2 == '0') introduced? 7.5.x+? I'm working on
troubleshooting some config errors and I need to rule out some possibilities.
Thanks!
-- James
___
rsyslog m
I would personally suggest going with Modules since that is what all of the
documentation refers to them as. That was we keep it consistent.
Input Modules, Output Modules, Parser Modules, Message Modification Modules,
etc.
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon
I tend to agree. We should be spending most of our effort on 'Current
versions.' Trying to back track old documentation on legacy setups is a huge
time sink that doesn't really benefit the future of the community in my opinion.
-- James
-Original Message-
From: rsyslog-boun...@lists.adi
Gordon -
This is a nice tutorial. Do you mind if I pull it into the rsyslog-doc project
in the tutotials section? Also what version of Rsyslog did you complete this on?
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.com] On Beh
While it is technically not a big deal to build a logger in
python/ruby/perl/etc, not everyone who uses rsyslog is assured to be able to
program at all. I think having a tool like this which is redesigned with the
advanced features of rsyslog is a fantastic idea. It gives a tool to those who
ca
Hey Everyone -
I have the initial version for all branches (v5-stable, v7-stable, v7-devel and
v8-devel aka master) pushed into the rsyslog-doc repo on Github. I still need
to work through getting all of the indexes updates for them all. They should
almost all be linked properly in v5-stable, b
Rainer -
I'm going to run with a quick test to see if I just put the files into the
correct place in the newer versions and then do the merge, if it will accept
it. My hope is that it will. If not I'll end up doing just that.
-- James
-Original Message-
From: rsyslog-boun...@lists.adi
Does the python script work with the omprog version that is with v7.4.x as
well? Or just with v8+? I'm curious as I'd like to play around with it a little
outside of my v8 test environment.
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lis
As a note, If you really need to have the DNS lookups consider installing nscd.
That will cache the DNS queries locally and addresses the fact that 4.x doesn't
have a DNS cache.
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.c
I believe you are correct, Rainer. As far as I know Github 'Releases' are just
tags. Github takes tags and in the release section uses tags to define a
'release' which is then compressed for easy download as a single file.
It's not a bad way to implementing a release file. Even for your own use.
I agree with Rainer.
While 'doing it right' from from the start and building from the ground up
perspective is a fantastic goal, the reality of trying to fit that in with an
entirely new direction is difficult at best. When you have a mounting list of
items that need to be worked on already, s
if we should place such non-C plugins into the main
rsyslog repo. I see lot's of good in this (assuming the contributor is happy
with that, of course), but that means that changes can only go into them via
PR, patches...
Rainer
On Wed, Jan 22, 2014 at 4:07 PM, Boylan, James wrote:
> I
Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of Rainer Gerhards
Sent: Wednesday, January 22, 2014 10:42 AM
To: rsyslog-users
Subject: Re: [rsyslog] non-C output plugins
On Wed, Jan 22, 2014 at 5:35 PM, Boylan, James wrote:
> Hmm. That&
Wed, Jan 22, 2014 at 5:44 PM, Boylan, James wrote:
> I think it might not be as hard to locate once the documentation is
> complete. We can work on including these scripts in the core documentation.
> That would make finding and using them far easier.
>
> And capitalization noted. W
nt: Wednesday, January 22, 2014 10:35 AM
To: rsyslog-users
Subject: Re: [rsyslog] non-C output plugins
On Wed, Jan 22, 2014 at 4:05 PM, Rainer Gerhards
wrote:
> On Wed, Jan 22, 2014 at 4:02 PM, Rainer Gerhards
> > wrote:
>
>> On Wed, Jan 22, 2014 at 3:59 PM, Boylan, James
r Gerhards"
To: "rsyslog-users"
Subject: [rsyslog] non-C output plugins
Date: Wed, Jan 22, 2014 9:04 AM
On Wed, Jan 22, 2014 at 4:02 PM, Rainer Gerhards
wrote:
> On Wed, Jan 22, 2014 at 3:59 PM, Boylan, James wrote:
>
>> I agree with everyone that omprog should be a go
I agree with everyone that omprog should be a good solution for this. I'm going
to be doing some tests in the near future with omprog so I'll be looking at
Radu's post as well. :)
Mostly I think using a stdout pipe is a good way of handling this. It is
similar to how Hadoop handles non-Java map
hat sounds good. Let me see if I can get at least some starting help from a
co-worker over here :-)
BTW: Florian created that image, something I should have mentioned in the first
place.
Rainer
>
>
> 2014/1/22 Boylan, James
>
> > That is a fantastic image. Now I need to find
That is a fantastic image. Now I need to find that shirt. :)
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of Rainer Gerhards
Sent: Wednesday, January 22, 2014 7:21 AM
To: rsyslog-users
Subject: Re: [rsyslog] rs
I agree with many of the points about the mission statement. I would really
like to see Rsyslog continue on the path of becoming one of the defacto unified
data transport solutions. To me, a true unified data transport needs to not
just be able to send the messages to a destination, but control
I agree with Radu. That kind of alerting it well outside the scope of Rsyslog
and you would also have to consider the potential performance impact that kind
of monitoring would have on the application.
-- James
-Original Message-
From: rsyslog-boun...@lists.adiscon.com
[mailto:rsyslog
6, 2014 10:39 AM
To: rsyslog-users
Subject: Re: [rsyslog] Main queue settings in new format?
On Thu, Jan 16, 2014 at 5:21 PM, Boylan, James wrote:
> The only way I know of doing it is by creating a new ruleset and
> defining a queue for it. Ie:
>
> ruleset(name="SysLogs "
The only way I know of doing it is by creating a new ruleset and defining a
queue for it. Ie:
ruleset(name="SysLogs "
queue.type="FixedArray"
queue.size="100"
queue.dequeuebatchsize="1000"
queue.workerthreads="4") {
## Ruleset contents
}
I'm not sure there i
slog-users
Subject: Re: [rsyslog] Redhat/CentOS init/sysconfig/default config files
On Wed, Jan 15, 2014 at 2:53 PM, Boylan, James wrote:
> Does it make sense to leave these files in the default Rsyslog GIT
> repo or move them into the Rsyslog-pkg-redhat-centos repo? Since we
> are buildi
] Service/Init issue in RHEL packages for 7.4.8-1?
On Wed, Jan 15, 2014 at 3:01 PM, Boylan, James wrote:
> Thanks Andre. I'll watch for the files and update my fork.
>
>
OK, and for the time being I'll not do anything and just how things progress ;)
Let me know if I should d
1 - 100 of 280 matches
Mail list logo
