The current JFR/Flamegraph is based on the volume of method calls, which often results in common library methods being displayed instead of customer application code that they really care about.
Want to provide customers some type of filtering mechanism (regex?) whereby they can either specify explicitly what they want included/shown or excluded/hidden.
Acceptance Criteria
Customers have the ability to either filter in/out what they desire, so they can see only their application code.
Design Consideration/Limitations
Can this be done exclusively in the UI? Should it be done exclusively in the UI?
workato-integration[bot]
commented
9 months ago
Description
Impacts both the JFR daemon and the UI.
The current JFR/Flamegraph is based on the volume of method calls, which often results in common library methods being displayed instead of customer application code that they really care about.
Want to provide customers some type of filtering mechanism (regex?) whereby they can either specify explicitly what they want included/shown or excluded/hidden.
Acceptance Criteria
Customers have the ability to either filter in/out what they desire, so they can see only their application code.
Design Consideration/Limitations
Can this be done exclusively in the UI? Should it be done exclusively in the UI?
Dependencies
N/A
Additional context
N/A