We observe a performance increase when using filters inside a Chain.
Knowing the metrics for each filter is critical to our usage of SI.
3.0 adds the id attribute for endpoints inside a chain, but the id is not used when the endpoint is published in JMX - the object class and hash code id (instance name) is presented instead, making it impossible to know which endpoint is which.
The endpoint id prefixed with the chain id would be ideal for identifying the filter in JMX.
Stuart Williams opened INT-3125 and commented
We observe a performance increase when using filters inside a Chain.
Knowing the metrics for each filter is critical to our usage of SI.
3.0 adds the id attribute for endpoints inside a chain, but the id is not used when the endpoint is published in JMX - the object class and hash code id (instance name) is presented instead, making it impossible to know which endpoint is which.
The endpoint id prefixed with the chain id would be ideal for identifying the filter in JMX.
Affects: 3.0 Backlog
Attachments:
The text was updated successfully, but these errors were encountered: