Julien, David,

I answer somewhat random to the post. Sorry it took me some time, I
need to prepare for when I will be out of office for a couple of days.

Thanks for your interest in mmjsonparse. I have just created an issue
to clarify what we have on our mind for it. @david: this shows also
how yaml would be used.

I am not sure if everything requested will be done in the next
iteration - we will probably do a multi-step approach (getting the
yaml lib integration done right is an important step 0).

Issue: https://github.com/rsyslog/rsyslog/issues/6251

Regarding the unflatten() function: I think we should retain it, but
not further extend it. This follows our core strategy to enable
"fearless upgrades". All new functionality related to json
transformation I see in mmjsonparse.

Note that I am *very* interested in any feedback on this effort. We
really want to make sure schema modifications et al can be powerfully
and easily done. Nothing beats real-world use cases, and this is where
you feedback comes in.

Rainer

El mié, 15 oct 2025 a las 12:48, Julien Thomas via rsyslog
(<[email protected]>) escribió:
>
> On 15/10/2025 12:45, David Lang wrote:
> > Julien Thomas wrote:
> >
> >> I like mmjsontransform, it sounds good. You could then probably
> >> remove the unflatten script function contrib/fmunflatten as it is
> >> doing the same with more features. We are using it to normalize json
> >> (unflatten) before elasticsearch ingest but we could switch to your
> >> new module, that would save maintaining that code; moreover
> >> elasticsearch can do it at ingest time now.
> >
> > can you modify your module to be a shim around a call to the new
> > module? that would maintain backwards compatibility for anyone using
> > your module, while (almost) killing of the maintinance effort for your
> > module.
>
> I would say nobody uses it appart from us ;)
> That said, you are right, but I am sure we won't have time to work on
> that before... long time!
>
> Julien
> _______________________________________________
> rsyslog mailing list
> https://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
https://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