Azure Data Factory - self-hosted integration runtime - missing metrics in Data Factory (v2) overview

von Euw Barbara 21 Reputation points
2026-08-18T12:15:02.3233333+00:00

We just noticed, that the metrics from the self hosted integration runtime, like Integration Runtime CPU or Integration Runtime Memory are missing.
The last metrics, we have are from Apr. 29 of this year (around 6:00 CEST) - before this time, we have all the information.
adfmetrics

Any idea why this metrics disappeared? No changes were done from our site...

Azure Data Factory
Azure Data Factory

An Azure service for ingesting, preparing, and transforming data at scale.


Answer accepted by question author
Smaran Thoomu 495 Reputation points Microsoft External Staff Moderator
2026-08-21T10:52:44.8233333+00:00

Hi @von Euw Barbara
Thank you for the details, and apologies for the delay and inconvenience this issue has caused.

Based on the information you provided, we have further investigated the issue. Since the SHIR is healthy and the Integration Runtime metrics are also missing directly under Data Factory > Monitoring > Metrics, this does not appear to be limited to the Overview page or an issue with the SHIR node itself.

We have identified a known issue affecting Self-hosted Integration Runtime metrics in the Switzerland North region. The issue started around April 29, 2026, which aligns with the timeline you reported. Our investigation has confirmed that the affected Integration Runtime metrics are not currently being emitted by the Data Factory service in this region, while other Data Factory metrics continue to be available.

We have engaged the relevant product/monitoring teams and the issue remains under investigation. At this time, there is no confirmed fix or ETA available.

You do not need to repeat the SHIR checks or provide the April Event Logs at this stage, as the current investigation points to a service-side metric emission issue rather than a problem with your SHIR configuration.

We understand that these metrics and alerts are important for monitoring the health of your SHIR environment, and we apologize for the continued impact. We will continue to track this with the product team and share an update as soon as we have further information regarding a fix or mitigation.

Thank you for your patience and understanding.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.