I like the idea, but I'm not sure if this is possible.
How I do my server logging:
AttributeCreator downstream of the outputport with a "log" attribute, where I describe the TransformerName (like "Tester_02 Failed") and a description what went wrong ("square has 6 points which is not ok").
Add timestamp.
Collect and merge all logmessages.
Send collected log to channel. In my case, this is email.
I like the idea, but I'm not sure if this is possible.
How I do my server logging:
AttributeCreator downstream of the outputport with a "log" attribute, where I describe the TransformerName (like "Tester_02 Failed") and a description what went wrong ("square has 6 points which is not ok").
Add timestamp.
Collect and merge all logmessages.
Send collected log to channel. In my case, this is email.
Hi thanks, that's what i'am doing right now but the lazy person in me wanted a faster way :)
Hi thanks, that's what i'am doing right now but the lazy person in me wanted a faster way :)
Hello @essb, I was thinking similarly to @nielsgerrits, the logfile may be the best option. You could also try the LogMessageStreamer, however, it looks like you'd still need to parse the transformer name from log.message (eg. Creator_XML_Creator (CreationFactory): Created 1 features). Hope this helps, Kailin.