Folks,

I created a patch a couple of days ago and would appreciate if someone
could try it out. Without confirmation, I don't like to merge it ;)

Full details are in the github bug:
https://github.com/rsyslog/rsyslog/issues/104

Rainer


On Mon, Aug 11, 2014 at 3:30 PM, Rainer Gerhards <[email protected]>
wrote:

> I maintain omelasticsearch as good as i can and had hoped to be ablw to
> fix this experimentally befor going on vacation.  Didn't work out.
> Hopefully i'll be able to look at it in the near future. Probably all tgat
> is needed is to nit check the "ok" property but rather "status" - plus a
> config option which tell which one to check.
>
> Rainer
>
> Sent from phone, thus brief.
> Am 11.08.2014 14:36 schrieb "Radu Gheorghe" <[email protected]>:
>
> Hi David,
>>
>> Just a couple comments from me:
>> - omelasticsearch is contributed in the sense that someone payed Adiscon
>> to
>> develop it. So I assume Rainer knows what's in there, but it's not his
>> responsibility to maintain the module as Elasticsearch API changes. So I
>> guess you're right, it's up to the community to maintain it, I just wanted
>> to paint the whole context I'm aware of
>> - if a test setup is needed, our Logsene
>> <http://www.sematext.com/logsene/>should
>> work well for that. It exposes the ES API (not 100%, but at least all the
>> indexing and search options are covered), so one could easily create a
>> free
>> account and register a free application to test pretty much all that is
>> Elasticsearch-related
>>
>> Best regards,
>> Radu
>> --
>> Performance Monitoring * Log Analytics * Search Analytics
>> Solr & Elasticsearch Support * http://sematext.com/
>>
>>
>> On Mon, Aug 11, 2014 at 1:50 PM, David Lang <[email protected]> wrote:
>>
>> > omelasticsearch is a contributed module, Rainer does not have a setup to
>> > test it, he depends on the community to maintain it (other than when he
>> > makes core changes)
>> >
>> > so for this sort of thing patches from someone are needed
>> >
>> > David Lang
>> >
>> >
>> >  On Mon, 11 Aug 2014, Radu Gheorghe wrote:
>> >
>> >  Hi Cristian,
>> >>
>> >> This issue seems to be caused by the fact that omelasticsearch looks
>> for
>> >> ok=true in the reply, and that's missing from ES 1.0 and later. It was
>> >> reported here: https://github.com/rsyslog/rsyslog/issues/104
>> >>
>> >> I'm not sure if someone is working on the issue, AFAIK Rainer is in
>> >> vacation, so if you or anyone else can submit a patch it would be much
>> >> appreciated - we already have two volunteers for testing, including
>> myself
>> >> :)
>> >>
>> >> Best regards,
>> >> Radu
>> >>
>> >> --
>> >> Performance Monitoring * Log Analytics * Search Analytics
>> >> Solr & Elasticsearch Support * http://sematext.com/
>> >>
>> >>
>> >> On Mon, Aug 11, 2014 at 11:34 AM, Cristian Falcas <
>> >> [email protected]>
>> >> wrote:
>> >>
>> >>  Hello,
>> >>>
>> >>> I'm using rsyslog to send logs to an elasticsearch instance and I have
>> >>> set
>> >>> also the errorFile parameter for all actions of this type.
>> >>>
>> >>> Unfortunately the error log files are spamed with correct result:
>> >>>
>> >>>         "reply":        {
>> >>>                 "took": 0,
>> >>>                 "errors":       false,
>> >>>                 "items":        [{
>> >>>                                 "create":       {
>> >>>                                         "_index":       "2014-08-11",
>> >>>                                         "_type":        "default",
>> >>>                                         "_id":
>>  "kzmXHE5hQfm0REMjzxPv7g",
>> >>>                                         "_version":     1,
>> >>>                                         "status":       201
>> >>>                                 }
>> >>>                         }]
>> >>>
>> >>>
>> >>> Status 201 should not be logged as an error.
>> >>>
>> >>> Best regards,
>> >>> Cristian Falcas
>> >>> _______________________________________________
>> >>> rsyslog mailing list
>> >>> http://lists.adiscon.net/mailman/listinfo/rsyslog
>> >>> http://www.rsyslog.com/professional-services/
>> >>> What's up with rsyslog? Follow https://twitter.com/rgerhards
>> >>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a
>> myriad
>> >>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
>> >>> DON'T LIKE THAT.
>> >>>
>> >>>  _______________________________________________
>> >> rsyslog mailing list
>> >> http://lists.adiscon.net/mailman/listinfo/rsyslog
>> >> http://www.rsyslog.com/professional-services/
>> >> What's up with rsyslog? Follow https://twitter.com/rgerhards
>> >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a
>> myriad
>> >> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
>> >> DON'T LIKE THAT.
>> >>
>> >>  _______________________________________________
>> > rsyslog mailing list
>> > http://lists.adiscon.net/mailman/listinfo/rsyslog
>> > http://www.rsyslog.com/professional-services/
>> > What's up with rsyslog? Follow https://twitter.com/rgerhards
>> > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
>> > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
>> > DON'T LIKE THAT.
>> >
>> _______________________________________________
>> rsyslog mailing list
>> http://lists.adiscon.net/mailman/listinfo/rsyslog
>> http://www.rsyslog.com/professional-services/
>> What's up with rsyslog? Follow https://twitter.com/rgerhards
>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
>> DON'T LIKE THAT.
>>
>
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to