Guidance needed to understanding the events generated by Self Hosted Integration Runtime (SHIR)

Question

I am using SHIR (Self-hosted Integration Runtime) with my Azure Data Factory. The overall set-up is working fine, it is delivering expected results.

But

1 I can see a lot of events in the Event Viewer on the machine which I do not understand and therefore cannot evaluate if I have to act on those events.

Is there somewhere documentation available that explain different events?

Here are some of the more frequent events that I observe on my machines (there are much more):

41014 - Warning - Worker process xxx disconnected

93 - Event - Error occurred while uploading the heartbeat for the node xxx

10010 - Event - Application 'xxx' (pid xxx) cannot be restarted - Application SID does not match Conductor SID..
41015 - Warning - Worker exits due to reaching IdleWorkerRecycleInternal

2 I have installed 2 SHIRs on 2 different machines and do not remember being asked to configure the events collection and categorization. I just followed standard installation path. However it seems like same events are assigned different categories on those 2 machines.

See example screenshot

Is it something that I can configure from the application side?

Answer 1

Hi Masha Galitskaia,

Thank you for posting query in Microsoft Q&A Platform.

Self hosted IR events are captured in two event viewer journals named: Connectors – Integration Runtime and Integration Runtime respectively.

We can view these events in event viewer. Please check below documentation to understand little more this.

Monitor self-hosted integration runtime (SHIR) virtual machines in Azure

Regarding the events which are seeing or mentioned, below are high level details.

1. Event ID 41014 - Warning - Worker process xxx disconnected: This event indicates that the worker process of the Integration Runtime disconnected. It could be due to a temporary network issue or an unexpected shutdown of the worker process. You can monitor the frequency and impact of these events to determine if further investigation or action is required.
2. Event ID 93 - Error occurred while uploading the heartbeat for the node xxx: This event suggests that there was an issue while uploading the heartbeat from the SHIR node to the Azure Data Factory service. The heartbeat is a periodic signal that the node sends to indicate its availability. This error might indicate a network problem or an issue with the SHIR's connection to the Azure Data Factory service.
3. Event ID 10010 - Event - Application 'xxx' (pid xxx) cannot be restarted - Application SID does not match Conductor SID: This event indicates that the SHIR encountered an error while attempting to restart an application. It specifically mentions a mismatch between the Application SID (Security Identifier) and the Conductor SID. This error might require further investigation to determine the root cause and resolve it.

Event ID 41015 - Warning - Worker exits due to reaching IdleWorkerRecycleInternal: This event signifies that a worker process in the SHIR was recycled due to reaching the idle worker recycle threshold. The idle worker recycle is a mechanism to manage resources efficiently by recycling idle workers after a certain period of inactivity. This event is generally a warning and doesn't require immediate action unless it happens excessively or affects your workload.

Hope this helps. Please let me know if any further queries.

---

Please consider hitting Accept Answer button. Accepted answers help community as well.

Answer 2

It is not really helping, as I still got no answer how did the configuration of log categories became different even though I did exactly the same installation in both cases. But I guess there is nothing else you can help with. Thanks!