Introduction

This section addresses common questions related to template-based alert definitions, including configuration options, behavior, and best practices.

These FAQs are designed to help you understand and manage alert definitions more effectively.

FAQs

Options not visible in Template-based Alert definition screens?

There are options to assign credentials, custom attributes, articles, and jobs when creating/updating the device management policy (old UI). Why am I not seeing these options in the Template-based Alert definitions screens?

Answer: All these actions have been moved to Resource Groups.
You can perform all these actions directly within Resource Groups.

Can I assign multiple templates to resources in a single alert definition?

Yes, you can assign multiple monitoring templates as long as they are compatible with the resource type.

I saved the Alert definition, but it did not run immediately.

After being saved, the Alert definition takes some time to finish processing.

What happens if I deselect the availability rule?

The alert definition will not evaluate resource availability, which may impact alert triggering for downtime scenarios.

What happened to Force Assign/Unassign option from the classic UI?

In the new UI, this behavior is handled by Overwrite resource level template assignments option.

  • If a resource does not meet the selected filter criteria, any templates currently assigned to that resource will be removed.

  • If this option is not selected, existing template assignments at the resource level will remain unchanged. Resources that do not meet the filter criteria will keep their current template assignments, and no templates will be unassigned.

Can I reuse a template across multiple alert definitions?

Yes, templates are reusable and can be applied to multiple definitions.

While customizing a Global Alert Definition, why does the resource filter query return no results?

The filter query may not be compatible with the selected resource type.

Example: If the alert definition targets VMware Virtual Machines, but the filter includes a condition like:
nativeType = "AWS EC2", no matching resources will be found.

Why? - Each resource type in OpsRamp has its own native type that identifies its origin or platform.

  • VMware resources have native types such as VMware Virtual Machine or VMware ESXi Host.

  • AWS resources have native types like AWS EC2, AWS RDS, etc.

So, when the alert definition is scoped to VMware, but your filter specifies a native type belonging to AWS, the system finds no matching resources because that combination can never exist under the same resource type.