In scaled out environments: define a policy to report stopped heartbeats only when instances count goes below a threshold

Particular / ServiceControl

Backend for ServiceInsight and ServicePulse

https://docs.particular.net/servicecontrol/

Other

51 stars 47 forks source link

In scaled out environments: define a policy to report stopped heartbeats only when instances count goes below a threshold #3317

Open mauroservienti opened 1 year ago

mauroservienti commented 1 year ago

Allow defining a policy that sets/configs some minimum instance count and only reports when the number of instances goes below it. Instead of reporting stopped heartbeats for every instance.

eirikurharaldsson commented 11 months ago

Is there any update on this?

mauroservienti commented 11 months ago

Thanks for chiming in, @eirikurharaldsson. At the moment, there isn't an ETA or an update. Being labeled as candidate-for-next-release, it might be picked up anytime soon.

eirikurharaldsson commented 2 weeks ago

Is this supported in ServiceControl 5?

eirikurharaldsson commented 2 weeks ago

Can i override the host identifier, so that the name is stable like dev1, dev2, dev3, test1, test2... (make it unique per container stage (dev, test, prod). https://docs.particular.net/nservicebus/hosting/override-hostid

I noticed this issue. Do you know if heartbeat plugin support override of the hostid? https://github.com/Particular/NServiceBus/issues/7026

awright18 commented 2 weeks ago

The latest version of the platform (ServicePulse 1.42.1 and ServiceControl 5.9) included this fix. Can you let us know if that helps in your scenario?