Alert callback option – possible bug?

[Jim Kosloskey]

Cloverleaf 2209. I am testing using the callback option to externalize the Alert.

So far in testing the Alert works as expected and I think is quite useful.

However, I do note the data sent (controlled by the elements selected in the Advanced Panel of the Alert Action Panel) is a list of lists that seems to be malformed.

The last element of the list is missing the close brace {SiteName test_jim’.

To be proper that should read {SiteName test_jim}’ I think.

Has anyone done this and can confirm the same observation – or – perhaps a different result?

 

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

Topic

[Jim Kosloskey]

Upon further inspection the data sent from the callback Alert Action option is more seriously malformed.

Here is what was delivered in full:

‘callback {alert00 {{Thread status of conn_8 is not up } {{Source conn_8} {CurrentTime {Wed Feb 07 11:34:33 2024}} {SiteName test_jim’

Obviously the leading and trailing single quotes need to be removed but look at the entire string.

I think {{Thread status of conn_8 is not up } should read {{Thread status of conn_8 is not up }} Note the added closing curly brace).

Also {{Source conn_8}  should read {{Source conn_8}}.

And lastly, {SiteName test_jim should read {SiteName test_jim}} to close the site name child element and the parent element.

So, I think it should look like this:

‘callback {alert00 {{Thread status of conn_8 is not up }} {{Source conn_8}} {CurrentTime {Wed Feb 07 11:34:33 2024}} {SiteName test_jim}}’

I definitely think this is a bug. Unfortunately, I cannot report this to INFOR so I hope someone who is reading this that can report it will.

Maybe this is a structure I just don’t understand.

I also think it would be better if this data were presented as a structured message format (like a VRL, or HRL, or even XML or JSON) so that the message could naturally flow through the routing and Xlate (or Tcl) via the engine rather than have to apply Tcl code at the IB Tps of the callback target to create a structured message from a list of lists or whatever non-native Cloverleaf message structure this is. Just my .02.

 

• This reply was modified 11 months ago by Jim Kosloskey. Reason: Added what I think should be the structure

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Jim Kosloskey]

Here is more indication this is a bug.

The Alert Log in hcimonitord directory show the Alert being fired with a proper list:

[02/07/2024 11:34:33] : Alert Fired Action
: Alert: conn_8 | Alert_1
: Message: Thread status of conn_8 is not up
: Notification #: 0
: Action: callback {alert00 {{Thread status of conn_8 is not up } {{Source conn_8} {CurrentTime {Wed Feb 07 11:34:33 2024}} {SiteName test_jim}}}}

Now I see this is intended to be a list of lists of lists.

If the target of the callback is a Cloverleaf thread acting as server, then the solution while the bug is in place is to add 4 } at the end of the message in the IB Tps UPoC.

If the target is not Cloverleaf, then the receiving system need to be aware of this bug and how to correct for it.

I am assuming (not a good thing to do) that the same thing will happen no matter what combination of data is presented from the Alert. I hope that is the case or the solution will be data dependent.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies