Lots of different saga instances sharing the same correlation ID cause performance issues

[ramonsmits]

Describe the bug

Description

The Saga view in ServiceInsights is getting slower and slower if there is a lot of saga history.

Different saga instances sharing the same correlation ID are shown as one. If many of such instances exist all seem to be loaded while pretty much all instance are not part of the visualized message conversation

When there are many of these all are loaded when opening the saga view from a conversation.

Expected behavior

1. Only see saga instances that are involved in the message conversation
2. See each saga instance lifetime independently
3. Potentially have an option to open state of past or future instances

Actual behavior

All instances are shown as one saga state flow:

Versions

Latest version which is https://github.com/Particular/ServiceInsight/releases/tag/2.13.0

Steps to reproduce

Repro available:

• Reproduce ServiceInsight saga state issue docs.particular.net#6161

Steps:

1. Setup endpoint with a saga + saga audit plugin and enable auditing
2. Have the saga created and completed using the saga correlation ID
3. Observe the saga view in ServiceInsight

Relevant log output

No response

Additional Information

Forum post:

• https://github.com/Particular/docs.particular.net/pull/6161/files