<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenText Analytics Database 26.2.x – Alerts</title>
    <link>/en/ot-cad/settings/alerts/</link>
    <description>Recent content in Alerts on OpenText Analytics Database 26.2.x</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/ot-cad/settings/alerts/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Ot-Cad: Monitoring alerts</title>
      <link>/en/ot-cad/settings/alerts/alerts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/ot-cad/settings/alerts/alerts/</guid>
      <description>
        
        
        &lt;h2 id=&#34;pre-configured-alerts&#34;&gt;Pre-configured alerts&lt;/h2&gt;
&lt;p&gt;The system provides pre-configured alerts to provide system monitoring capabilities without manual setup. Each alert has a pre-configured threshold that defines the acceptable performance limit. The system then sends a message notification when the database exceeds that threshold.&lt;/p&gt;
&lt;p&gt;You can monitor the system using preconfigured alerts without setting them up manually.&lt;/p&gt;
&lt;h3 id=&#34;queries&#34;&gt;Queries&lt;/h3&gt;
&lt;p&gt;Query performance alerts notify you when queries exceed execution time thresholds. The system provides the following pre-configured alerts to monitor queries:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Failed query number - The total number of queries that failed during execution due to errors.&lt;/li&gt;
&lt;li&gt;Query running time - A query that is neither in the queue nor completed is a running query. The Query Running Time reflects the elapsed time since the query started executing.&lt;/li&gt;
&lt;li&gt;Queued query number - The number of queries currently waiting in the queue for resources before execution begins.&lt;/li&gt;
&lt;li&gt;Retried query number - The number of queries that are placed on hold for different reasons, such as limited resources.&lt;/li&gt;
&lt;li&gt;Spilled query number - The number of queries that were written to disk when the system did not have enough memory.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;resource-pool&#34;&gt;Resource pool&lt;/h3&gt;
&lt;p&gt;The system sends alerts when an individual resource pool reaches a specified state or usage level. For details about resource pool configuration parameters, see &lt;a href=&#34;../../../../en/admin/managing-db/managing-workloads/resource-pool-architecture/built-resource-pools-config/#&#34;&gt;Built-in resource pools configuration&lt;/a&gt;. You can configure the following resource pool alerts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ended query with queue time exceeding limit - The number of queries that were not executed because their queue time exceeded the allowed limit.&lt;/li&gt;
&lt;li&gt;Ended query with runtime exceeding limit - The number of queries that were stopped because they ran longer than the time limit set by the resource pool.&lt;/li&gt;
&lt;li&gt;Maximum allowed resource value - The maximum resource limits (such as memory, CPU) allowed for a query defined in the resource pool.&lt;/li&gt;
&lt;li&gt;Minimum starting resource value - The minimum resources required for a query to start running.&lt;/li&gt;
&lt;li&gt;Queries with resource rejections - The number of queries that were rejected due to insufficient resources.&lt;/li&gt;
&lt;li&gt;Queries reaching the max allowed execution time - Set a time threshold to see how many queries reached that limit during execution.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;custom-alerts&#34;&gt;Custom alerts&lt;/h2&gt;
&lt;p&gt;Create custom alerts to measure system performance metrics that are not monitored by the pre-configured alerts. Create a dynamic SQL query that triggers an alert when it returns any results. You can configure how often an alert is generated, the alert criticality level, and who receives email alerts. For example, you can create custom alerts that monitor the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Failed logins within a configurable time period&lt;/li&gt;
&lt;li&gt;Idle database user sessions using a configurable time limit

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

You must have administrator privilege to create, edit, clone, and delete custom alerts.

&lt;/div&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;Createnotf&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;create-a-custom-alert&#34;&gt;Create a custom alert&lt;/h3&gt;
&lt;p&gt;Create custom alerts to track abnormalities and performance fluctuations for queries and resource pools using your own database schemas and tables. When the database triggers an active alert, you receive notifications according to the alert priority.

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

Creating custom alerts on custom tables is not recommended because it can increase query execution time and affect performance. Custom alerts are designed to work optimally with system tables.

&lt;/div&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;In the Settings Overview page, select &lt;strong&gt;Alerts&lt;/strong&gt;.
The Alerts page appears.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Choose &lt;strong&gt;Custom alert&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the &lt;strong&gt;Alert name&lt;/strong&gt; field, enter a unqiue name for the custom alert.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the &lt;strong&gt;Description&lt;/strong&gt; field, enter an optional description for the custom alert.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the &lt;strong&gt;Trigger condition query&lt;/strong&gt; field, enter the following SQL query and choose &lt;strong&gt;Run&lt;/strong&gt;:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;SELECT
  login_timestamp,
  user_name,
  node_name,
  client_hostname,
  reason
FROM
  login_failures
WHERE
  reason in (&amp;#39;INVALID USER&amp;#39;, &amp;#39;FAILED&amp;#39;, &amp;#39;INVALID DATABASE&amp;#39;)
  AND login_timestamp &amp;gt; sysdate - INTERVAL &amp;#39;{{Time_Interval}}&amp;#39;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The AND clause of the preceding query encloses the variable of type String named &lt;code&gt;Time_Interval&lt;/code&gt; in double curly braces to represent a valid SQL syntax element.&lt;/p&gt;
&lt;p&gt;A variable is a dynamic value that is evaluated at runtime that you can configure after you save the alert. You can add up to 6 variables per custom alert. Variable names may consist of a maximum of 14 alpha-numeric characters, including underscores. Verify that the variable uses the correct data type and format. Variables of type String require single quotes around the curly braces.&lt;/p&gt;
&lt;p&gt;A SQL query triggers an alert if it returns one or more rows.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;From the &lt;strong&gt;Interval&lt;/strong&gt; list, choose the time interval at which the SQL query is executed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the &lt;strong&gt;Criticality level&lt;/strong&gt; area, choose the alerty priority. By default, the alert criticality is &lt;strong&gt;Low&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Choose the option &lt;strong&gt;Send an email copy&lt;/strong&gt;. In the &lt;strong&gt;Add new user&lt;/strong&gt; field, enter the email address of the recipient. For multiple recipients, enter the email addresses separated by a comma.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Choose &lt;strong&gt;Create&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Turn the alert on or off using the switch at the right of the alert row.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;edit-a-custom-alert&#34;&gt;Edit a custom alert&lt;/h3&gt;
&lt;p&gt;After creating a custom alert, you can edit the details to suit your requirements.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;In the Alerts page, select a custom alert.&lt;/li&gt;
&lt;li&gt;Hover over &lt;strong&gt;⋮&lt;/strong&gt; and select &lt;strong&gt;Edit&lt;/strong&gt;. All the details of the custom alert are populated. You cannot edit the name of the custom alert. For more information about editing a custom alert, see &lt;a href=&#34;#Createnotf&#34;&gt;Create a custom alert&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;clone-a-custom-alert&#34;&gt;Clone a custom alert&lt;/h3&gt;
&lt;p&gt;You can create a clone or replica of an existing custom alert. The settings of the existing custom alert are copied to the cloned custom alert. You can edit these settings in the cloned custom alert.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;In the Alerts page, select a custom alert.&lt;/li&gt;
&lt;li&gt;Hover over &lt;strong&gt;⋮&lt;/strong&gt; and select &lt;strong&gt;Clone&lt;/strong&gt;. Information in all fields is pre-populated. You can edit this information. For more information about editing a custom alert, see &lt;a href=&#34;#Createnotf&#34;&gt;Create a custom alert&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;delete-a-custom-alert&#34;&gt;Delete a custom alert&lt;/h3&gt;
&lt;p&gt;You can delete a custom alert that is no longer in use or required.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;In the Alerts page, select a custom alert.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Hover over &lt;strong&gt;⋮&lt;/strong&gt; and select &lt;strong&gt;Delete&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the Confirmation dialog, select &lt;strong&gt;Delete&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The custom alert is deleted.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;

      </description>
    </item>
    
    <item>
      <title>Ot-Cad: Alert configuration</title>
      <link>/en/ot-cad/settings/alerts/alert-configuration/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/ot-cad/settings/alerts/alert-configuration/</guid>
      <description>
        
        
        &lt;h2 id=&#34;alert-configuration&#34;&gt;Alert configuration&lt;/h2&gt;
&lt;p&gt;Enable and customize settings for pre-configured or custom alerts for each database. Pre-configured and custom alerts generate messages when the component they measure exceeds the specified threshold.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;Confset&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;configurable-settings&#34;&gt;Configurable settings&lt;/h3&gt;
&lt;p&gt;Select &lt;strong&gt;Alerts&lt;/strong&gt; in the Settings Overview page. To configure an alert, you must turn the switch on the right of the row to the on position. By default, custom alerts are turned off. Pre-configued and custom alerts have the following settings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Trigger condition&lt;/strong&gt; - Add lower and upper limits on acceptable operating values for the component. Move the arrow up or down to either increase or decrease the query count.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Interval&lt;/strong&gt; - Choose how often the system executes the underlying SQL for the alert.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resource pool&lt;/strong&gt; - Choose the resource pool to which you need to add this alert.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Criticality level&lt;/strong&gt; - Choose the alerty priority. By default, the alert criticality is &lt;strong&gt;Low&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Send an email copy&lt;/strong&gt; - Choose this option to enter the email address of the recipient. For multiple recipients, enter the email addresses separated by a comma.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;configuring-resource-pool-alerts&#34;&gt;Configuring resource pool alerts&lt;/h3&gt;
&lt;p&gt;Resource pool alerts use the same configurable settings as the other alerts, but you can set alerts per resource pool.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Login to OTCAD.&lt;/li&gt;
&lt;li&gt;In the Settings Overview page, select &lt;strong&gt;Alerts&lt;/strong&gt;.
The Alerts page appears.&lt;/li&gt;
&lt;li&gt;In the Resource pools tab, select the resource pool to which you need to add this alert.&lt;/li&gt;
&lt;li&gt;Edit the trigger condition, interval, resource pool, criticality level, and recipient user email address. For more information, see &lt;a href=&#34;#Confset&#34;&gt;Configurable settings&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;configuring-query-alerts&#34;&gt;Configuring query alerts&lt;/h3&gt;
&lt;p&gt;You can configure alerts that monitor queries.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Login to OTCAD.&lt;/li&gt;
&lt;li&gt;In the Settings Overview page, select &lt;strong&gt;Alerts&lt;/strong&gt;.
The Alerts page appears.&lt;/li&gt;
&lt;li&gt;In the Queries tab, select the query to which you need to add this alert.&lt;/li&gt;
&lt;li&gt;Edit the trigger condition, interval, criticality level, and recipient user email address. For more information, see &lt;a href=&#34;#Confset&#34;&gt;Configurable settings&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;view-alerts&#34;&gt;View alerts&lt;/h3&gt;
&lt;p&gt;The Alerts page organizes alerts to help you effectively monitor the state of your database. Pre-configured and custom alerts generate messages when the component they measure exceeds the specified threshold.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Log in to OTCAD.&lt;/li&gt;
&lt;li&gt;Click the &lt;strong&gt;Bell&lt;/strong&gt; icon in the upper‑right corner of the application.
The Alerts page appears.&lt;/li&gt;
&lt;li&gt;From the &lt;strong&gt;Date range&lt;/strong&gt; list, choose the period to view the alert. Do one of the following:
&lt;ul&gt;
&lt;li&gt;Choose &lt;strong&gt;Last 15 min&lt;/strong&gt; to view only those alerts that were created in the last 15 minutes.&lt;/li&gt;
&lt;li&gt;Choose &lt;strong&gt;Last 1 hour&lt;/strong&gt; to view only those alerts that were created in the last one hour.&lt;/li&gt;
&lt;li&gt;Choose &lt;strong&gt;Last 7 days&lt;/strong&gt; to view only those alerts that were created in the last 7 days.&lt;/li&gt;
&lt;li&gt;Choose &lt;strong&gt;Last 14 days&lt;/strong&gt; to view only those alerts that were created in the last 14 days.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;From the &lt;strong&gt;Notification type&lt;/strong&gt; list, choose the type of alert. Do one of the following:
&lt;ul&gt;
&lt;li&gt;Choose &lt;strong&gt;All&lt;/strong&gt; to view both resource pool and query alerts.&lt;/li&gt;
&lt;li&gt;Choose &lt;strong&gt;Queries&lt;/strong&gt; to view only query alerts.&lt;/li&gt;
&lt;li&gt;Choose &lt;strong&gt;Resource pool&lt;/strong&gt; to view only resource pool alerts.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;In the &lt;strong&gt;Severity&lt;/strong&gt; area, choose the option to view the alerts by severity. Do one of the following:
&lt;ul&gt;
&lt;li&gt;Choose &lt;strong&gt;Low&lt;/strong&gt; to view alerts with low priority.&lt;/li&gt;
&lt;li&gt;Choose &lt;strong&gt;High&lt;/strong&gt; to view alerts with high priority.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Mark as read&lt;/strong&gt; after you view an alert and do not wish to view the same alert again.

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

&lt;pre&gt;&lt;code&gt;The system does not display notifications that are marked as read.
&lt;/code&gt;&lt;/pre&gt;


&lt;/div&gt;&lt;/li&gt;
&lt;/ol&gt;

      </description>
    </item>
    
  </channel>
</rss>
