Metrics: properly track messages transmitted through DistributedPubSub about phobos-issues HOT 6 CLOSED

Let me check with the customer and see if this matches what they're seeing

from phobos-issues.

Do we have any specs in Phobos for PubSub scenario? Or I will need to implement this? PubSub can be created between several nodes in same OS process, right? Just on different ports?
Did not work with that before, but will be happy to try it out 👍

from phobos-issues.

Do we have any specs in Phobos for PubSub scenario? Or I will need to implement this? PubSub can be created between several nodes in same OS process, right? Just on different ports?

We do not.

How I strongly recommend doing this:

1. https://phobos.petabridge.com/articles/quickstart.html - follow the quickstart tutorial first, so you can see what Phobos metrics look like in a normal application
2. https://github.com/petabridge/akkadotnet-cluster-workshop - try to update Phobos to 1.0.4 in this sample and see what the DistributedPubSub message metrics look like here. If they're weird or missing, that sample should help you work backwards to be able to create a reproducible unit test.

from phobos-issues.

Thanks!

from phobos-issues.

P.S. Latest version of phobos is 1.0.3 so far: https://sdkbin.com/publisher/petabridge/product/phobos

from phobos-issues.

@Aaronontheweb So, currently, I have added very simple DistriburedPubSub usage to Phobos.Web sample:
petabridge/Petabridge.Phobos.Web#18

I can see publish-subscribe trace:

And I can see published message info in akka_net_akka_messages_recv_total metrics:

I seems like messages are captured by Phobos metrics. Does not look like messages are lost, nor locally nor between nodes.

from phobos-issues.