Manage infrastructure health rules

Apply infrastructure health rules to automatically enforce health policies across matching resources. Define a rule once and it continuously applies the selected policies to all current and future resources that match your criteria, eliminating manual configuration and preventing drift.

Why use health rules

Without health rules, managing health policies requires:

• Opening each resource's health panel individually
• Enabling or disabling the same policies repeatedly across resources
• Remembering to configure policies for every new resource deployed

Health rules let you define a policy configuration once and have it applied automatically wherever it matches, ensuring consistent health monitoring across your infrastructure.

View health rules

To view health rules, select Infrastructure from the left navigation, then Health Rules.

The health rules page displays all rules in a table with these columns:

Column	Description
Rule Name	Display name of the rule.
Resource Type	Kubernetes resource type the rule targets (for example, Deployments, Hosts, Nodes, Pods).
Enabled Policies	Number of policies enabled by this rule out of the total available for the resource type, shown as a fraction (for example, 2/5).
Service	Service ownership filter, if set.
Environment	Environment ownership filter, if set.
Team	Team ownership filter, if set.
Updated At	Timestamp of the last modification.
Enabled	Toggle to enable or disable the rule.

Filter rules

Use the left sidebar filters to narrow the rules list:

• Rule Name: filter by one or more existing rules.
• Resource Type: filter by Deployments, Hosts, Nodes, Pods, and other Kubernetes resource types.
• Service: filter by ownership service tag.
• Environment: filter by ownership environment tag.
• Team: filter by ownership team tag.

Use the search bar above the rules table to find rules by name.

Create a health rule

Rule creation is a three-step wizard: Scope, Policies, then Summary.

1. Select Infrastructure, then Health Rules.
2. Select + Create rule. The New rule wizard opens at Step 1, Scope.
3. Step 1, Scope. Define which resources this rule applies to.
   • In Rule Name, enter a descriptive name, for example, Production Payments Health.
   • In Resource Type, select the Kubernetes resource type this rule targets, for example, Deployments, Hosts, Nodes, Pods, or Cron Jobs. Only resource types with available policies appear.
   • Filter the scope by ownership tags. Combine Team, Service, and Environment to narrow which resources match — for example, apply a rule only where service is payments-api and environment is production. Ownership tags are optional, but adding at least one is strongly recommended so the rule targets the resources you actually own. If no ownership tags are set, the rule applies to every resource of the selected type. For ownership tag setup, see Ownership.
   • (Optional) In Excluded Resources, select individual resources to exempt from this rule. Excluded resources do not have the rule's policies applied, even if they match the filter criteria. By default, no resources are excluded.
   • Select Next.
4. Step 2, Policies. Define which policies this rule enables. The table lists every policy available for the selected resource type, with a title, description, and an Enabled toggle. Search by policy name to narrow the list. Enable each policy you want this rule to enforce, then select Next.
5. Step 3, Summary. Review the scope and the policies the rule will enable. Saving this rule enables the selected policies on all matching resources.
   • Select Back to return to a previous step and edit values.
   • Select Create to save the rule.

The new rule appears in the health rules table. Allow up to 5 minutes for policies to propagate to all matching resources.

Example: enforce health policies for production payment services

A backend team wants to apply strict health monitoring to all production deployments for their payments service:

1. Create a rule named Production Payments Health.
2. Set resource type to Kubernetes Deployment.
3. Set filters: Service = payments-api, Environment = production, Team = backend.
4. Enable policies: Workload Readiness, Pod Resource Limits, CrashLoopBackOff.
5. Save the rule.

All matching deployments, including any new deployments that match these criteria in the future, automatically have these three policies enforced.

View rule details

Select any row in the health rules table to open the rule details drawer. The drawer has three tabs.

Details

Shows metadata about the rule:

Field	Description
Created by	Email of the user who created the rule.
Created at	Timestamp of rule creation.
Last modified by	Email of the user who last modified the rule.
Last updated	Timestamp of the last update.
Excluded resources	List of resources explicitly excluded from this rule.

The drawer header shows the rule name, the resource type badge, an Enabled toggle, an Edit Rule action, and a Delete Rule action.

Policies

Displays a table of all health policies enabled by this rule, showing the policy title and description.

Resources

Shows all resources that the rule currently applies to:

Column	Description
Name	Resource identifier.
Overall Health	Overall health status of the resource (not rule-specific). Shows Healthy or Critical.
Policies	Fraction of policies passing for this resource (for example, 2/2 or 0/2).
Service	Service ownership tag.
Environment	Environment ownership tag.
Team	Team ownership tag.

Select Infra Explorer in the top right to open a filtered view of these resources in Infrastructure Explorer.

The Overall Health column always shows the overall health of the resource, not just the health relative to this rule's policies. This keeps consistency with what you see in Infrastructure Explorer. If a resource shows as Critical but all policies from this rule are passing, an info icon appears with a tooltip explaining that the resource is Critical due to failing policies managed by other rules, and that all policies enabled by this rule are healthy.

Select any resource row to open the resource's Health section in a new drawer tab.

Edit a rule

Edit a rule in two ways:

• From the details drawer, select Edit Rule.
• From the table, open the more actions menu on a rule row and select Edit Rule.

The edit view shows the same fields as the create wizard collapsed into a single page, pre-populated with the existing configuration. Modify the rule name, resource type, ownership filters, excluded resources, or enabled policies, then select Update.

Enable and disable rules

Use the toggle in the Enabled column of the main table or the toggle in the rule details drawer.

• Disabling a rule stops it from enforcing policies on matching resources. The associated policies are deactivated for those resources.
• Re-enabling a rule reactivates policy enforcement.

Enabling a rule applies its policy configuration to all matching resources, overriding any existing manual policy settings. New matching resources automatically inherit these policies. Changes take effect within a few minutes.

Delete a rule

Open the more actions menu on a rule row and select Delete Rule, or open the rule details drawer and select Delete Rule. A confirmation prompt appears before deletion.

When a rule is deleted, the policies it managed are no longer enforced on the matching resources.

How rules interact with resource health

Health rules change how health policies are managed at the resource level.

Resources without rules

If no health rules apply to a resource, you can manually enable or disable individual health policies from the resource's Health section in Infrastructure Explorer.

Resources with rules

Once any rule applies to a resource, all health policy management for that resource becomes read-only:

• You cannot manually toggle individual policies.
• Policies are controlled entirely through health rules.
• A banner indicates that health policies for the resource are controlled by health rules and points you to either edit the rule or exclude the resource from health rules to make manual updates.
• You can still select individual policies to view their details.
• Policies not enabled by any rule show as Unmonitored.

To regain manual control over a specific resource, exclude it from all applicable rules.

View rules from a resource

In the resource details drawer, the Health section has two tabs.

The Health rules tab shows a table of all rules that apply to this resource. Select a rule row to open the rule details drawer. If no rules apply, an empty state shows with a link to the health rules page. If the resource is explicitly excluded from a rule, the rule appears with an Excluded indicator.

The Health policies tab shows the list of health policies for the resource, the same as the current view, but read-only when rules are active.

Multiple rules on the same resource

When multiple rules apply to the same resource:

• All policies from all applicable rules are enabled on the resource.
• If two rules enable the same policy, the policy is deduplicated and evaluated only once.
• If a resource is excluded from Rule A (which enables Policy X) but Rule B also enables Policy X and applies to the resource, Policy X remains active through Rule B.

Default rules

For accounts that previously toggled health policies manually, the default rules are available but turned off so they do not overwrite that configuration. Turn them on at any time.

Limitations

Propagation delay

Allow up to 5 minutes after creating, updating, or deleting a rule before changes are fully reflected across all matching resources.

Ownership tag dependency

Filter criteria depend on ownership tags (service, team, environment) being properly assigned to your resources. If ownership tags have not propagated yet or are not configured, rules using those filters do not match the expected resources. See Ownership for setup instructions.

• Only ownership-based filters (service, team, environment) are supported.
• Each filter supports a single value (for example, service = payments-api).

Excluded resources

Excluded resources are selected individually, with a maximum of 100 per rule.

Best practices

1. Scope rules with at least one ownership tag. Set at least one of Service, Team, or Environment when creating a rule so it targets the resources you intend to manage. Rules without any ownership tag apply broadly and can lock manual policy management on resources you did not plan to cover.
2. Use descriptive names. Name rules clearly so team members understand their purpose at a glance, for example, Production Payments — Critical Monitoring rather than Rule 1.
3. Review the default rules. Check the rules Coralogix creates for each resource type and customize or disable them to match your organization's needs.
4. Use exclusions sparingly. If you find yourself excluding many resources, consider adjusting the rule's filter criteria instead.
5. Coordinate with your team. Rules affect all matching resources and lock out manual policy changes. Communicate with team members before creating rules that affect shared infrastructure.

Related resources

• Infrastructure Explorer overview
• Health overview
• Ownership
• Permissions