What is 'Directly ingested signal' and how do I get rid of it?

Hello Staffan Wärnberg, we understand that in your Azure Monitor Health Models, certain entities are showing a signal called “Directly ingested signal.” Once this signal enters a Degraded or Unhealthy state, it never changes, and there is no option to remove it in the portal.

It seems the “Directly ingested signal” is a system-generated, catch-all signal for telemetry that isn’t mapped to a defined Health Model signal. It cannot be deleted manually.

Its state remains stuck in Degraded/Unhealthy if:

1. No new healthy telemetry is ingested.
2. The incoming telemetry is invalid or mismatched.

To resolve the issue, you can either:

1. Remap the telemetry to a proper signal.
2. Ignore the signal for health evaluation.
3. Stop or remove bad telemetry from orphaned or stale resources.

 Identify the affected entity

• Go to Azure Monitor > Health Models > Designer.
• Open the Health Model and select the entity showing the “Directly ingested signal.”

Determine the source of the signal: Check the Log Analytics workspace or custom metrics feeding the Health Model. Identify if the telemetry comes from active resources, orphaned VMs, or offboarded agents.

Remap the telemetry: In the Health Model Designer:

1. Go to Signals > Add Signal.
2. Select your data source.
3. Define thresholds and evaluation logic.

This replaces the catch-all signal for proper health calculation.

Ignore the signal: this is optional

• In the entity > Signals > “Directly ingested signal.”
• Enable “Do not consider this signal for health evaluation” to prevent it from affecting overall entity health.

Stop orphaned or stale telemetry

• Remove decommissioned VMs or agents from monitoring scope.
• Ensure no telemetry is being sent from stale resources.

Refresh the Health Model Designer. Confirm that mapped signals report Healthy / Degraded / Unhealthy correctly and that the “Directly ingested signal” no longer impacts overall health if ignored or replaced.

If the issue still persists, please help us with the more details,

“Is the ‘Directly ingested signal’ showing up for active resources that are still sending telemetry, or is it appearing for decommissioned/offboarded resources where no new telemetry is arriving?”

If it’s active resources, the solution is likely remapping or adjusting thresholds.

If it’s stale/offboarded resources, the solution is likely removing orphaned telemetry or ignoring the signal.

Well, the problem is that this signal is not showing up anywhere except in the Health state. It's not available in the designer or the signals blade.

Above shows the active signals on the entity. If I edit the entity, the below is shown:

The signal definition blade doesn't show this signal either.

Any comments on this?

Hello Staffan Wärnberg, Apologies for the delayed response, Azure Monitor Health Model supports two paths for health:-

• Modeled health, where signals are explicitly defined with thresholds, evaluation rules, and recovery logic.
• Direct health ingestion, where a component writes health state directly to an entity.

When health state is written directly (without a modeled signal definition), Azure Monitor records the state but has no associated signal object. In this case, the UI represents it as a “Directly ingested signal.”

Because there are no evaluation rules or recovery logic, the health state remains at the last ingested value. If it is written as Unhealthy or Degraded and no subsequent Healthy state is ingested, the entity never recovers.

Since this signal is system-generated and has no manifest or definition, it does not appear in the Designer or Signals blade and is visible only in the health state view.

We have reached out to you in Private messages for additional details, could you please look into it and share us the details? Thanks