Engine Output change in Cloverleaf 6.2

[Ron Meijsen]

Hi,

The Product Advisory Board of Cloverleaf has been asked their input on the Engine Output (EO) messages that are created by Cloverleaf.

Currently, Cloverleaf does not allow ERR or WARN EO to be suppressed, even if such EO aliases like disable_all are applied.

Product management of Infor have had several requests to suppress certain ERR or WARN messages in EO.

Topic

[Terry Kellum]

Needs to be granular.  I want to have enough information to be able to diagnose “out of the blue” issues, but there are some errors and warning the are really just “noise” and do not contribute to awareness of the engine state.  While they are useful for deeper levels of troubleshooting, they are worse than useless when performing first level diagnosis.  Detailed engine panics, errors that drop messages, these sorts of “always a problem” should still be logged by default.

Rob should be able to guide the software team on the relative strengths of classes of EO output.

[Rob Abbott]

Hi Terry (and everyone else), if you have some examples of ERR or WARN that are “noise” please list them out, so we can move them to a state that can be disabled.

Thanks!

Rob Abbott
Cloverleaf Emeritus

[Terry Kellum]

While I don’t remember if I have dug this one down, it’s an annoyance that merely means that the connection has been dropped.  If you’ve coded the integration to drop connection intentionally, it’s an irritant.

[tcp :read:ERR /0:   save_trans:02/25/2015 11:44:18] Raw read failed: Connection reset by peer

[tcp :read:ERR /0:   save_trans:02/25/2015 11:44:18] Unable to read msg length

[tcp :read:ERR /0:to_outbound_save:02/25/2015 11:44:18] Read 0 bytes — peer disconnected?

[tcp :read:ERR /0:to_outbound_save:02/25/2015 11:44:18] Unable to read msg length

I don’t really consider disconnection to be an error, especially when its a feature.  Thanks!!!

[Bob Richardson]

Greetings,

Rob and company, my favorite to suppress is:

Engine idle — 02/26/2015 08:00:32

It is always comforting to know that Cloverleaf is taking a break from doing any work and still getting paid (like some humans I know).

On another note:  how about setting up a knowledge database on how to interpret panic dump error messages?  Especially those somewhat cryptic “cpp” lines that point to the logic that failed?

And, thanks. for asking the community here on its feedback!

[John Mercogliano]

I agree with Terry, any connection issues should be a no more then a warning or even info.  Since you should have alerts setup for real connection issues.

My basic criteria would be the only things tagged as errors are issues that cause a message to stop processing or places a message in the error db.  Anything else should be warnings or info.

Thanks,

John Mercogliano
Sentara Healthcare
Hampton Roads, VA

[G Terpstra]

The engine idle is also one of my favorits to be filtered.

But most of all, the documentation on the EO options should be improved.

I am not able to read from the documentation which option I should enable to get the hexadecimal messages in the logging and preferably turn all other messages off.

[Author]

Replies