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 and ran the Alert definition, but it did not execute immediately.

Once executed, the Alert definition takes some time to complete.

What happens if I deselect the availability rule?

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

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.