Is your improvement related to a problem? Please describe.
ServiceInsight “Flow Diagram” becomes difficult to use for some message trees that have a lot of “leaf node” messages.
Part of that issue is that the Flow Diagram renders very wide-- but part of the issue is that it shows too much
Describe the suggested solution
Two options have been suggested - there may be other/better ways of achieving the desired outcome:
It would be nice if each message type in SI had the ability to A) collapse all messages under it, B) collapse configured message types under it (to hide less important messages), C) show all messages under it – and to be able to toggle between those modes. To make this work, the user would need to be able to configure each message type to describe which display mode it should be initially, and a list of less important important message types for under it.
Allow multiple correlation Ids. when looking at a message, it would show all messages that shared at least one correlation id. In this way, I could have the starting message have one correlation id, and when it gets to “noisy” message, that noisy message would have that same correlation id, but would also have another that it uses for the messages under it. When looking at the “noisy” message, it would show everything above and below it. When looking at message under the “noisy” message that only have the latter correlation id, it would only show messages up to the “noisy” message.
Describe the suggested improvement
Is your improvement related to a problem? Please describe.
ServiceInsight “Flow Diagram” becomes difficult to use for some message trees that have a lot of “leaf node” messages.
Part of that issue is that the Flow Diagram renders very wide-- but part of the issue is that it shows too much
Describe the suggested solution
Two options have been suggested - there may be other/better ways of achieving the desired outcome:
It would be nice if each message type in SI had the ability to A) collapse all messages under it, B) collapse configured message types under it (to hide less important messages), C) show all messages under it – and to be able to toggle between those modes. To make this work, the user would need to be able to configure each message type to describe which display mode it should be initially, and a list of less important important message types for under it.
Allow multiple correlation Ids. when looking at a message, it would show all messages that shared at least one correlation id. In this way, I could have the starting message have one correlation id, and when it gets to “noisy” message, that noisy message would have that same correlation id, but would also have another that it uses for the messages under it. When looking at the “noisy” message, it would show everything above and below it. When looking at message under the “noisy” message that only have the latter correlation id, it would only show messages up to the “noisy” message.
Additional Context
No response