The problem card is not tagged properly

jellypuno — Wed, 18 Mar 2026 15:42:48 GMT

Summary

If you receive a problem card containing incorrect or unexpected tags or management zones, this usually occurs because tags and Management Zones are applied throughout the entire lifecycle of a problem.
Any entity that is affected at any point—and that contains a tag or belongs to a Management Zone—will pass those attributes to the problem card.

This article explains why this happens and how to fix it by reviewing your Tagging rules, Management Zone rules, and dimensional rules for Metric-Based Events.

Why Incorrect Tags Appear on Problem Cards

Tags appear on a problem card because:

The affected entity had those tags at some point during the lifecycle of the problem.
Management Zones and tags may be inherited from parent entities if propagation rules are enabled.
Dimensional rules for Metric-Based Events may be unintentionally adding entities to Management Zones.

Use the troubleshooting steps below to determine where the incorrect tag or Management Zone originated.

Troubleshooting Steps

Check Tagging and Management Zone Propagation Rules

Misconfigured propagation settings may cause tags or Management Zones to appear in a problem card.

How to check:

Go to Settings → Preferences → Management Zones
Select the relevant Management Zone rule
Look for settings that enable inheritance or propagation

4. Turn off these options if you do not want tags or zones to propagate

Tip: As a best practice, create separate rules for each entity type. This helps avoid unnecessary or unintended attributes being added to your entities.

Check Dimensional Rules (Metric-Based Events Only)

For Metric-Based Events, dimensional rules may add metrics to a specific Management Zone—and this may create unintended tags or zones on the problem card.

Example scenario

A dimensional rule groups metrics into a Management Zone
This Management Zone is applied to the problem
The problem card inherits tags linked to that zone

Review your dimensional rules to confirm whether an event-based configuration is adding unwanted attributes.

What's Next

If the problem persists or these solutions don't apply, please contact us via chat and provide the following:

A link to the affected problem.
The troubleshooting steps you have already tried.

Re: The problem card is not tagged properly

ChadTurner — Fri, 12 May 2023 18:48:22 GMT

Thank you for this notice 🙂

Re: The problem card is not tagged properly

sujit_k_singh — Fri, 29 Mar 2024 06:41:33 GMT

@jellypunoThank you for sharing this. I have a question: Does this imply that the best practice is to create conditions separately instead of enabling toggles for both services and processes in one condition, such as inside the host monitoring rule?"

Re: The problem card is not tagged properly

jellypuno — Tue, 02 Apr 2024 08:23:15 GMT

@sujit_k_singh Yes, that is the ideal approach.

article The problem card is not tagged properly in Troubleshooting

The problem card is not tagged properly

Summary

Why Incorrect Tags Appear on Problem Cards

Troubleshooting Steps

Check Tagging and Management Zone Propagation Rules

Check Dimensional Rules (Metric-Based Events Only)

What's Next

Related reading

Re: The problem card is not tagged properly

Re: The problem card is not tagged properly

Re: The problem card is not tagged properly