Empty message data section in saga visualization

,
1

Hi Guys,
I wonder why I have an empty message data section in saga visualization section.
I can display the message in the Body tab. I use rabbitmq + pgsql.

empty message data section
empty message data section1357×667 29.5 KB

please advice

2

That requires the saga audit plugin:

We should do a better job in the UI to indicate this. I created an issue to improve this in a future enhancement release:

3

sorry to inform you but that plugin is there already

endpointConfiguration.AuditSagaStateChanges(serviceControlQueue: configuration["Queues:SagaAudit"]);

rabbit queues
rabbit queues1021×168 15.3 KB

"Queues:SagaAudit points to Particular.XXX-Testing

ps. and the documentation regarding saga audit is fine, its stated clearly that this plugin must be installed

4

I’m sorry, as Hadi mentioned on the issue what should be shown there are the messages bodies. Your saga state is shown just fine in the middle.

What type of message bodies do these 4 messages have?

5

message body example

<PlaceOrder xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:baseType="CoinSwapping.Contracts.Commands.SagaCommand" xmlns="http://tempuri.net/CoinSwapping.Contracts.Commands.Orders">
  <Amount>0.000023</Amount>
  <CurrencyPairId>823</CurrencyPairId>
  <OrderType>BUY</OrderType>
  <SagaId>LTC-fd9dd78de2d3f29de5100d569c8c6bfea741f3261b7f202fe6f416674382177a</SagaId>
  <TimeStamp>2020-04-17T22:48:28.6323574Z</TimeStamp>
</PlaceOrder>

and i expect saga visualization data to not be empty

order saga
order saga2560×1080 182 KB

I also wonder if the properties on the right should be filled also

6

and now funny thing

funny

for some reason, the last message is not empty

7

guys, aby update on this ?

8

Issue created to analyze this specific issue: Message bodies not shown in saga view for message using inheritance · Issue #855 · Particular/ServiceInsight · GitHub

9

@Kamil_Wojciechowski we have just released ServiceInsight 2.5.0 which should address this issue. Please take a look and see if this works correctly in your environment.