Why is heartbeat id a new guid instead of instance id?

[andersekdahl]

When we run a continous webjob without it being singleton, it's very useful that heartbeats are logged to Azure BlobStorage. However, these ids logged to BlobStorage are random guids which makes them less useful. I thought those ids where the same as the WEBSITE_INSTANCE_ID which would make them a lot more useful.

Is there any reason for it being a random guid instead of the WEBSITE_INSTANCE_ID? If not, I'm happy to create a PR for this.

Repro steps

Run a console application and use JobHost with valid connection strings to blob storage. See that you get heartbeats but with a guid generated here:

azure-webjobs-sdk/src/Microsoft.Azure.WebJobs.Host.Storage/Logging/DashboardLogger.cs

Line 70 in 4130350

Guid hostInstanceId = Guid.NewGuid();

Expected behavior

I'd expect the heartbeat blob name to be the WEBSITE_INSTANCE_ID if that env variable is set.

Actual behavior

A random guid is set as the heartbeat blob name.

Known workarounds

None that I know of.

[v-anvari]

Moving this issue to backlog for further updates