Configuration of uniquely identified running instances on Azure App Service

[kpuranen (Kimmo Puranen)]

Hi,

When endpoint is running on Azure App Service (web job), which one of these configurations would be recommended i.e. could the first one cause any problems to routing, monitoring or to any other tools?

1. One “fixed” instance identity for one web site.

var webSiteName = Environment.GetEnvironmentVariable("WEBSITE_SITE_NAME");

endpointConfiguration
	.UniquelyIdentifyRunningInstance()
	.UsingNames("endpointName", webSiteName);

2. Multiple instance identities for one web site.

var webSiteName = Environment.GetEnvironmentVariable("WEBSITE_SITE_NAME");
var instanceId = Environment.GetEnvironmentVariable("WEBSITE_INSTANCE_ID");
var displayName = $"{webSiteName}_{instanceId.Substring(0, 6)}";

endpointConfiguration
	.UniquelyIdentifyRunningInstance()
	.UsingNames(instanceId, webSiteName)
	.UsingCustomDisplayName(displayName);

Question is related to:

Remove unused endpoint instances from ServicePulse configuration

Hi, Is there any automated way to remove unused endpoint instances from the ServicePulse configuration? We’re using endpoints on Azure App Service web jobs with .NET Core, Azure Service Bus, NServiceBus v7.1.10, ServicePulse v1.22.0 and ServiceControl v4.3.3. The problem is on ServicePulse which is making notifications of heartbeat failures because there have been accumulated hundreds of endpoint instances which are not in use any more. Those endpoints can be clicked off from ServicePulse’s C…

[boblangley]

Kimmo:

Setting the display name using the WEBSITE_INSTANCE_ID will not have any affect on routing. However it will identify instances in monitoring / servicepulse. If you are sure you will never scale the website, then omitting the WEBSITE_INSTANCE_ID will not cause any problems, however in general I would recommend every customer running NServiceBus endpoints in a web job and using ServicePulse follow the second option and include the WEBSITE_INSTANCE_ID as many features in ServicePulse are designed to report on physical instances of the endpoint, not just the logical endpoint as a whole.