Use of user defined paramters (UDP) in event filters on monitoring events

Idea review. Thank you for taking the time to raise this suggestion. As noted, when specifying an event filter, you can use xpath expressions to examine a value held in part of the logical message tree in order to decide whether or not to emit the event. Details here:

https://www.ibm.com/docs/en/app-connect/12.0?topic=basics-example-xpath-expressions-event-filtering

This capability is incredibly flexible because the choice of whether to emit an event can be made on a message-by-message basis as opposed to a fixed setting for an entire environment. In the proposed idea, the decision to emit an event is instead based upon the value of a message flow's user-defined property. Similarly, one could imagine using references to other static values such as the name of the flow, its containing application or the name of the integration server to which it is deployed. These kind of environmental static values are available in ESQL and graphical data maps. In concept we understand the requirement along these lines and we agree it would bring additional benefit. In the meantime of course, it would be possible to apply a workaround of sorts and take these kind of static environmental values and place them into the logical tree using a prior message flow node and so be able to reference them in later nodes when deciding whether to emit a monitoring event. This would only work in message flow nodes downstream so wouldnt be able to be applied directly to an input node. So, whilst somewhat of a fringe requirement we're happy to move it to Future Consideration status and test the appetite from the user community - this is the first time this has been raised many years after monitoring events have been available, but its never too late to make things *even* better of course ;o)