<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenText Analytics Database 26.2.x – Monitoring database messages and alerts with MC</title>
    <link>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/</link>
    <description>Recent content in Monitoring database messages and alerts with MC on OpenText Analytics Database 26.2.x</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Mc: Message center</title>
      <link>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/message-center/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/message-center/</guid>
      <description>
        
        
        &lt;p&gt;The &lt;strong&gt;Message Center&lt;/strong&gt; organizes system performance alerts to help you effectively monitor the state of your database. &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/alert-config/&#34;&gt;Pre-configured&lt;/a&gt; and &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/custom-alerts/&#34;&gt;custom alerts&lt;/a&gt; generate messages when the component they measure exceeds the specified threshold.&lt;/p&gt;
&lt;p&gt;Access the &lt;strong&gt;Message Center&lt;/strong&gt; in the following ways:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;On the MC Home page, select &lt;strong&gt;Message Center&lt;/strong&gt; in the &lt;strong&gt;MC Tools&lt;/strong&gt; section.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select the message envelope icon in the top-right of any database-specific page, then select &lt;strong&gt;Message Center&lt;/strong&gt; in the quick view.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the database &lt;strong&gt;Overview&lt;/strong&gt; tab, select the number (including 0) in the &lt;strong&gt;Unread Messages (This Week)&lt;/strong&gt; widget.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&#34;../../../../images/mc/message-center-overview.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;The Message Center can retrieve up to 10,000 of the most recent messages generated for a database. By default, it lists up to 600 messages generated in the previous week. For details on how to retrieve messages that predate the previous week, see &lt;a href=&#34;#Date&#34;&gt;Date Filtering&lt;/a&gt;.

&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;p&gt;To adjust the maximum number of messages listed in the Message Center, edit the &lt;code&gt;messageCenter.maxEntries&lt;/code&gt; value in the &lt;code&gt;/opt/vconsole/config/console.properties&lt;/code&gt; file from the command line. For example, the following value increases the number of alerts listed in the Message Center to 5000:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;messageCenter.maxEntries=5000&lt;/code&gt;&lt;/p&gt;


&lt;/div&gt;&lt;/p&gt;
&lt;h2 id=&#34;filter-the-messages-grid&#34;&gt;Filter the messages grid&lt;/h2&gt;
&lt;p&gt;The Management Console provides options that filter the messages that populate the messages grid by database, keyword, message type, and date. Use one or more of these options to view only the messages that you want to manage.&lt;/p&gt;
&lt;h3 id=&#34;database-filtering&#34;&gt;Database filtering&lt;/h3&gt;
&lt;p&gt;Select &lt;strong&gt;Showing&lt;/strong&gt; to list the databases that are associated with the logged in user account. Choose a specific database to view only messages for that database, or select &lt;strong&gt;(All DBs)&lt;/strong&gt; to view and manage messages across all of your databases.&lt;/p&gt;
&lt;h3 id=&#34;keyword-filtering&#34;&gt;Keyword filtering&lt;/h3&gt;
&lt;p&gt;Use the search bar at the top-right of the screen to list messages that contain the entered text. For example, if you enter 29, the grid lists any messages that contain those characters within the message title or message details available when you click the plus (+) icon to expand the message row.&lt;/p&gt;
&lt;h3 id=&#34;message-type-filtering&#34;&gt;Message type filtering&lt;/h3&gt;
&lt;p&gt;After you select a value for &lt;strong&gt;Showing&lt;/strong&gt;, the number of messages for that value are totaled and grouped by type near the top-right corner of the screen, below the search bar. These message types use the &lt;a href=&#34;https://datatracker.ietf.org/doc/html/rfc5424&#34;&gt;syslog standard&lt;/a&gt; to define severity levels. The MC message types are defined as follows:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;All Messages&lt;/strong&gt;: Messages that are not archived or deleted, and are within &lt;code&gt;messageCenter.maxEntries&lt;/code&gt; for the previous week.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;High Priority&lt;/strong&gt;: Messages that you &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/alert-config/&#34;&gt;assigned a High Priority&lt;/a&gt; alert priority on the &lt;strong&gt;Alerts&lt;/strong&gt; tab. These messages correspond to syslog levels 0 and 1.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Need Attention&lt;/strong&gt;: Critical or error messages that indicate that correspond to syslog levels 2 and 3.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Informational&lt;/strong&gt;: Warning, notice, informational, or debugging messages that correspond to syslog levels 4, 5, 6, and 7.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To populate the grid with only a single message type, select the number or message type description.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;Date&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&#34;date-filtering&#34;&gt;Date filtering&lt;/h3&gt;
&lt;p&gt;Select &lt;strong&gt;Retrieve Older Messages&lt;/strong&gt; to enter &lt;strong&gt;From&lt;/strong&gt; and &lt;strong&gt;To&lt;/strong&gt; dates to list messages that were generated before the previous week. OpenText™ Analytics Database stores 10,000 of the most recent database messages so that you can retrieve older messages when necessary.&lt;/p&gt;
&lt;h2 id=&#34;message-groups&#34;&gt;Message groups&lt;/h2&gt;
&lt;p&gt;The Message Center groups messages and notifications as &lt;strong&gt;Recent Messages&lt;/strong&gt;, &lt;strong&gt;Threshold Messages&lt;/strong&gt;, and &lt;strong&gt;Archived Messages&lt;/strong&gt;. All message groups use the following priority levels and color codes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Critical (Red)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Warning (Orange)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Notice (Green)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Info (Blue)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;recent-messages-and-threshold-messages&#34;&gt;Recent messages and threshold messages&lt;/h3&gt;
&lt;p&gt;Recent Messages include the most recent messages generated within the previous week within the &lt;code&gt;messageCenter.maxEntries&lt;/code&gt; value. Threshold messages include messages that are generated when the database exceeds a pre-configured, custom, or default alert threshold.&lt;/p&gt;
&lt;p&gt;Recent Messages and Threshold Messages are listed using the message type, database name, a description of the message, and the date and time that the message was generated. Additionally, there are collapsible grid headings that group the alerts by &lt;strong&gt;Today&lt;/strong&gt;, &lt;strong&gt;Yesterday&lt;/strong&gt;, and &lt;strong&gt;This Week&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&#34;archived-messages&#34;&gt;Archived messages&lt;/h3&gt;
&lt;p&gt;Archived messages are messages that you manually saved for later. When you select the check icon for an individual message or select &lt;strong&gt;Archive All&lt;/strong&gt;, MC marks the message as read and archives it. Archived messages do not have the same date or &lt;code&gt;messageCenter.maxEntries&lt;/code&gt; restrictions as &lt;strong&gt;Recent Messages&lt;/strong&gt; or &lt;strong&gt;Threshold Messages&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The &lt;strong&gt;Archived Messages&lt;/strong&gt; tab contains the following tools to refine search result filters:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Use the &lt;strong&gt;From&lt;/strong&gt; and &lt;strong&gt;To&lt;/strong&gt; boxes above the grid to define a time frame for the archived message search. To combine multiple time frames, select the &lt;strong&gt;Do not clear existing search results&lt;/strong&gt; checkbox.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Sort or filter messages even further using the &lt;strong&gt;Type&lt;/strong&gt;, &lt;strong&gt;Database Name&lt;/strong&gt;, &lt;strong&gt;Description&lt;/strong&gt;, and &lt;strong&gt;Date&lt;/strong&gt; columns.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;message-actions&#34;&gt;Message actions&lt;/h2&gt;
&lt;p&gt;Perform actions on all, multiple, or individual messages. To execute actions on all messages at the same time, use the &lt;strong&gt;Select All&lt;/strong&gt; or &lt;strong&gt;Select None&lt;/strong&gt; buttons near the top-right of the screen by the search bar.&lt;/p&gt;
&lt;p&gt;Each message row has a checkbox so that you can perform actions on one or more messages simultaneously. Select the plus (+) icon to expand the message row and display the following message details:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Summary&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Host IP&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Time of occurrence&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Number occurrences of this message&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Description&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For additional information about each message, query &lt;a href=&#34;../../../../en/sql-reference/system-tables/v-monitor-schema/event-configs/#&#34;&gt;EVENT_CONFIGURATIONS&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;When you select the &lt;strong&gt;X&lt;/strong&gt; icon or select multiple messages and click the &lt;strong&gt;Delete Msgs&lt;/strong&gt; or &lt;strong&gt;Delete all&lt;/strong&gt; buttons, the message is permanently deleted.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Mc: Alert configuration</title>
      <link>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/alert-config/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/alert-config/</guid>
      <description>
        
        
        &lt;p&gt;Enable and customize settings for pre-configured or custom alerts for each database. For example, you can set the &lt;strong&gt;Threshold Value&lt;/strong&gt; for &lt;strong&gt;Node Disk Usage&lt;/strong&gt; to a 20% minimum or 80% maximum. If any node exceeds either of those thresholds, the MC generates a message and you receive a notification. Take action on alerts in the &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/message-center/#&#34;&gt;Message center&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To access the &lt;strong&gt;Alerts&lt;/strong&gt; tab, log in to the Management Console, then select &lt;strong&gt;Go to database&lt;/strong&gt; &amp;gt; &lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;Alerts&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;Configur&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;configurable-settings&#34;&gt;Configurable settings&lt;/h2&gt;
&lt;p&gt;To configure any alert, you must toggle the switch on the left of the row to the on position. &lt;strong&gt;Node State Change&lt;/strong&gt; is the only pre-configured alert turned on by default. By default, custom alerts are toggled off.&lt;/p&gt;
&lt;p&gt;Pre-configued and custom alerts have the following settings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Query variables&lt;/strong&gt;: Custom alerts only. Query variables are the variables that you added when you &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/custom-alerts/&#34;&gt;created the alert&lt;/a&gt;. You must provide a value for each variable. The query variable is not validated after you create the alert. If you update the variable to a value that results in an invalid query, the alert is silently disabled during the next execution.&lt;br /&gt;To view the original SQL query, hover the mouse over the alert name to display the alert in a tooltip.&lt;br /&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Threshold Value&lt;/strong&gt;: Pre-configured alerts only. You can add a lower and upper limit on acceptable operating values for the component.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Check Interval&lt;/strong&gt;: This value determines how often OpenText™ Analytics Database executes the underlying SQL for the alert.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Alert Priority&lt;/strong&gt;: You can assign one of the following priority labels to determine how the alert is distributed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Alert&lt;/strong&gt; and &lt;strong&gt;Critical&lt;/strong&gt;: Displays the message using the &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/&#34;&gt;message alert notification&lt;/a&gt; mechanisms on the &lt;strong&gt;Overview&lt;/strong&gt; page and creates a message in the &lt;strong&gt;Message Center&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Warning&lt;/strong&gt;: Creates a message in the &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/message-center/#&#34;&gt;Message center&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Alert Email Recipients&lt;/strong&gt;: Configure email notifications for any alert priority when the alert is triggered. You must have &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/setting-up-smtp-email-alerts/&#34;&gt;SMPT configured&lt;/a&gt;. For details about adding email recipients to alerts, see &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/custom-alerts/#&#34;&gt;Custom alerts&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Vertical ellipses&lt;/strong&gt;: For custom alerts and new resource pool alerts, click the vertical ellipses to delete the alert. You must have &lt;a href=&#34;../../../../en/mc/users-roles-and-privileges/config-privileges/&#34;&gt;MC ADMIN role&lt;/a&gt; privileges to delete an alert.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;configuring-resource-pool-alerts&#34;&gt;Configuring resource pool alerts&lt;/h2&gt;
&lt;p&gt;Resource pool alerts use the same configurable settings as the other alerts, but you can set alerts per resource pool. By default, pre-configured alerts are set for the &lt;a href=&#34;../../../../en/admin/managing-db/managing-workloads/resource-pool-architecture/built-pools/&#34;&gt;GENERAL&lt;/a&gt; pool only.

&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;

Only users with &lt;a href=&#34;../../../../en/mc/users-roles-and-privileges/config-privileges/&#34;&gt;MC ADMIN role&lt;/a&gt; privileges can add alerts for resource pools other than the GENERAL pool.

&lt;/div&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Log in to the Management Console and select &lt;strong&gt;Databases&lt;/strong&gt; &amp;gt; &lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;Alerts&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the top row labeled &lt;strong&gt;Resource Pool&lt;/strong&gt;, select the blue box with a plus (+) symbol on the far right of the row. When you hover over the button, the button expands and displays &lt;strong&gt;Add Resource Pool Alert +&lt;/strong&gt;.&lt;br /&gt;The &lt;strong&gt;New Resource Pool Alert&lt;/strong&gt; window opens.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In &lt;strong&gt;Alert Name&lt;/strong&gt;, choose the alert that you want to add to a resource pool.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In &lt;strong&gt;Resource Pool&lt;/strong&gt;, choose the resource pool that you want to add this alert to.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;When you are finished configuring the remaining settings, select &lt;strong&gt;Create Alert&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Edit &lt;strong&gt;Check Interval&lt;/strong&gt;, &lt;strong&gt;Alert Priority&lt;/strong&gt;, and Alert Email Recipients as you would other alerts. For guidance, see &lt;a href=&#34;#Configur&#34;&gt;Configurable Settings&lt;/a&gt; or &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/custom-alerts/#&#34;&gt;Custom alerts&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To delete the alert, select the vertical ellipses at the right of the row, and select &lt;strong&gt;Delete&lt;/strong&gt;. You must have &lt;a href=&#34;../../../../en/mc/users-roles-and-privileges/config-privileges/&#34;&gt;MC ADMIN role&lt;/a&gt; privileges to delete an alert.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Mc: Setting up SMTP for email alerts</title>
      <link>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/setting-up-smtp-email-alerts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/setting-up-smtp-email-alerts/</guid>
      <description>
        
        
        &lt;p&gt;Management Console can generate &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/alert-config/&#34;&gt;email notifications&lt;/a&gt; when your database exceeds high-priority alert thresholds. To receive email alerts, you must configure your SMTP settings in MC.&lt;/p&gt;
&lt;p&gt;You must be an administrator to provide SMTP settings. To set up MC to send email:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Select the &lt;strong&gt;Email Gateway&lt;/strong&gt; tab on the MC Settings page.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select the &lt;strong&gt;Email&lt;/strong&gt; tab.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Provide the following information about your SMTP server:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;From&lt;/strong&gt;: The email address used in the SMTP header.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;From display name&lt;/strong&gt;: Allows you to configure a user-friendly alias for the email address. If a display name is not specified, the email address entered in &lt;strong&gt;From&lt;/strong&gt; is displayed in the email clients.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Reply to&lt;/strong&gt; (optional): The email address used to reply to the SMTP header. If not set, the &lt;strong&gt;From&lt;/strong&gt; email address will be used.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Reply to display name&lt;/strong&gt; (optional): Allows you to configure a user-friendly alias for the email address. If a display name is not specified, the email address entered in &lt;strong&gt;Reply to&lt;/strong&gt; is displayed in the email clients.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Envelope from&lt;/strong&gt; (optional): The bounce address used in the return path of the SMTP header for the emails that are sent.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Host&lt;/strong&gt;: The hostname or IP of the SMTP server.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Port&lt;/strong&gt;: The port of the SMTP server.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Encryption&lt;/strong&gt;: Select the &lt;strong&gt;Enable SSL&lt;/strong&gt; and &lt;strong&gt;Enable StartTLS&lt;/strong&gt; checkboxes to support sending emails for recovering usernames and passwords, especially if the SMTP server is on an external network. Change the &lt;strong&gt;Port&lt;/strong&gt; to 465, the default port for SSL/TLS.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Authentication&lt;/strong&gt;: Turn on if your SMTP server requires authentication.&lt;/p&gt;

&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 Username and Password fields display only when you turn on Authentication.
&lt;/code&gt;&lt;/pre&gt;


&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Username&lt;/strong&gt;: The username for connecting to the server.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Password&lt;/strong&gt;: The password for connecting to the server. The password can refer a value from an external vault.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click &lt;strong&gt;Test Connection&lt;/strong&gt;. MC validates your SMTP settings and sends a test email to the inbox of the email you provided.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Verify that you have successfully received the test email.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click &lt;strong&gt;Save&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;After you set up SMTP for email, you can configure MC to send high-priority threshold alerts through email. For details, see &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/alert-config/#&#34;&gt;Alert configuration&lt;/a&gt; or &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/custom-alerts/#&#34;&gt;Custom alerts&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Mc: Custom alerts</title>
      <link>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/custom-alerts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/custom-alerts/</guid>
      <description>
        
        
        &lt;p&gt;Create custom events-based alerts to track abnormalities and performance fluctuations for node health, 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, and can take action in the &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/message-center/#&#34;&gt;Message center&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;creating-a-custom-alert&#34;&gt;Creating a custom alert&lt;/h2&gt;
&lt;p&gt;You must have &lt;a href=&#34;../../../../en/mc/users-roles-and-privileges/config-privileges/&#34;&gt;MC ADMIN role&lt;/a&gt; privileges to create a custom alert.&lt;/p&gt;
&lt;p&gt;The following steps create a custom alert named &lt;strong&gt;Failed logins within a X time period&lt;/strong&gt; to track the number of failed logins in the previous two hours, per user. This alert might indicate a possible distributed denial-of-service (DDoS) attack, or an application behaving inappropriately. The underlying SQL query uses a variable to create a dynamic threshold value that you can fine-tune after you create the alert.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Log in to the Management Console, then select &lt;strong&gt;Go to database&lt;/strong&gt; &amp;gt; &lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;Alerts&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the &lt;strong&gt;Custom Alerts&lt;/strong&gt; row at the top of the page, click the blue box with a plus (+) symbol on the far right of the row. When you hover over the button, the button expands and displays &lt;strong&gt;Create Custom Alert +&lt;/strong&gt;.&lt;br /&gt;The &lt;strong&gt;Create custom alert&lt;/strong&gt; window displays.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In &lt;strong&gt;Alert Name&lt;/strong&gt;, enter &lt;strong&gt;Failed logins within X time period&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In &lt;strong&gt;SQL Query&lt;/strong&gt;, enter the following SQL query:&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. Use the formatting or full screen buttons above and to the right of the &lt;strong&gt;SQL Query&lt;/strong&gt; box as needed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A box displays below the &lt;strong&gt;SQL Query&lt;/strong&gt; box containing placeholder text that corresponds to each variable name. To test the alert, enter &lt;strong&gt;2 Hours&lt;/strong&gt; in this box.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select &lt;strong&gt;Run Query&lt;/strong&gt;. The &lt;strong&gt;Query Results&lt;/strong&gt; section displays any rows returned from your query. Alternatively, you might encounter one of the following issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;If you use invalid SQL syntax, you receive an error.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;If the query returns more than 5 columns or 100 rows, you receive a warning. Because every query result set is saved to disk, it is important to be aware of the size of your result set. For more information, see &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/#&#34;&gt;Monitoring database messages and alerts with MC&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A long-running query runs until it succeeds or returns a Query Error that indicates that there are insufficient resources to continue. To stop a long-running query, select &lt;strong&gt;Cancel Query&lt;/strong&gt;.&lt;/p&gt;

&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;When you are satisfied with the query results, select &lt;strong&gt;Create Alert&lt;/strong&gt;.&lt;br /&gt;The &lt;strong&gt;Create custom alert&lt;/strong&gt; window closes and the alert you just created is listed in the &lt;strong&gt;Custom Alerts&lt;/strong&gt; section on the &lt;strong&gt;Alerts&lt;/strong&gt; page. When you point the mouse on the query name, the query is displayed in a tooltip. Under the query name, there are editable boxes that correspond to the variables you added when creating the alert.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the &lt;strong&gt;Time_Interval&lt;/strong&gt; variable box, enter &lt;strong&gt;2 Hours&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select a value for &lt;strong&gt;Check Interval&lt;/strong&gt;. The default setting is &lt;strong&gt;10 minutes&lt;/strong&gt;. This value determines how often the query is executed.

&lt;div class=&#34;admonition important&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Important&lt;/h4&gt;
&lt;p&gt;To prevent the scheduled query from impacting system performance, each query has a default runtime threshold of 30 seconds. If the query runtime exceeds this threshold once, the alert is automatically disabled.&lt;/p&gt;
&lt;p&gt;To adjust the timeout threshold, edit the &lt;code&gt;threshold_query.disable_time_out&lt;/code&gt; setting in the &lt;code&gt;/opt/vconsole/config/console.properties&lt;/code&gt; file.&lt;/p&gt;

&lt;/div&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select a value for &lt;strong&gt;Alert Priority&lt;/strong&gt;. By default, the alert is assigned the &lt;strong&gt;Critical&lt;/strong&gt; value priority.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Optionally, select the &lt;strong&gt;Manage Emails&lt;/strong&gt; icon under &lt;strong&gt;Alert Email Recipients&lt;/strong&gt; to send an email alert to specific users when the alert is triggered. To register a user to receive email alerts, complete the steps in &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/setting-up-smtp-email-alerts/#&#34;&gt;Setting up SMTP for email alerts&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Complete the following steps in the &lt;strong&gt;Manage Email Recipient&lt;/strong&gt; window:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;To add an existing user to an alert, click the checkbox beside the existing MC user, or select the box at the top to add all. For non-existing MC users, enter their email address at the bottom of the window.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In &lt;strong&gt;Email Interval&lt;/strong&gt;, select how often the email is sent:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Immediately&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;One hour: The hour starts when you make the alert.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;One day&lt;/strong&gt;: Users receive the alert 24 hours after you create the alert.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For example, if you select &lt;strong&gt;One hour&lt;/strong&gt;, an email is sent every hour, even if the alert is triggered multiple times within the hour.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click &lt;strong&gt;Save&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;After you create the alert, toggle it on or off using switch at the far left of the alert row.&lt;/p&gt;
&lt;h2 id=&#34;editing-a-custom-alert&#34;&gt;Editing a custom alert&lt;/h2&gt;
&lt;p&gt;You must have &lt;a href=&#34;../../../../en/mc/users-roles-and-privileges/config-privileges/&#34;&gt;MC ADMIN role&lt;/a&gt; privileges to edit a custom alert.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Log in to the Management Console, then select &lt;strong&gt;Go to database&lt;/strong&gt; &amp;gt; &lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;Alerts&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the &lt;strong&gt;Custom Alerts&lt;/strong&gt; row at the top of the page, locate the custom alert that you want to edit.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select the vertical ellipses, and select &lt;strong&gt;Edit&lt;/strong&gt;.&lt;br /&gt;The &lt;strong&gt;Edit custom alert&lt;/strong&gt; window opens and displays the previously saved values for the custom alert.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Edit the alert. You can edit any of the following alert properties:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Alert Name&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;SQL Query&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Any variable values&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select &lt;strong&gt;Run Query&lt;/strong&gt;. The &lt;strong&gt;Query Results&lt;/strong&gt; section displays any rows returned from your query. Alternatively, you might encounter one of the following issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;If you use invalid SQL syntax, you receive an error.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;If the query returns more than 5 columns or 100 rows, you receive a warning. Because every query result set is saved to disk, it is important to be aware of the size of your result set. For more information, see &lt;a href=&#34;../../../../en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/#&#34;&gt;Monitoring database messages and alerts with MC&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A long-running query runs until it succeeds or returns a Query Error that indicates that there are insufficient resources to continue. To stop a long-running query, select &lt;strong&gt;Cancel Query&lt;/strong&gt;.&lt;/p&gt;

&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;When you are satisfied with the query results, select &lt;strong&gt;Update Alert&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;deleting-an-alert&#34;&gt;Deleting an alert&lt;/h2&gt;
&lt;p&gt;To delete a custom alert, select the vertical ellipses at the right of the row, and select &lt;strong&gt;Delete&lt;/strong&gt;. You must have &lt;a href=&#34;../../../../en/mc/users-roles-and-privileges/config-privileges/&#34;&gt;MC ADMIN role&lt;/a&gt; privileges to delete an alert.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Mc: Exporting MC-managed database messages and logs</title>
      <link>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/exporting-mc-managed-db-messages-and-logs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/mc/monitoring-using-mc/monitoring-db-messages-and-alerts-mc/exporting-mc-managed-db-messages-and-logs/</guid>
      <description>
        
        
        &lt;p&gt;You can export the contents of database messages, log details, query details, and MC user activity to a file.&lt;/p&gt;
&lt;p&gt;Information comes directly from the MC interface. This means that if the last five minutes of &lt;code&gt;vertica.log&lt;/code&gt; information displays on the interface, you can save that five minutes of data to a file, not the entire log. When you filter messages or logs, MC exports only the filtered results.&lt;/p&gt;
&lt;p&gt;Depending on how you set your browser preferences, when you export messages you can view the output immediately or specify a location to save the file. System-generated file names include a timestamp for uniqueness.&lt;/p&gt;
&lt;p&gt;The following table shows, by record type, the MC pages that contain content you can export, the name of the system-generated file, and what that file&#39;s output contains:

&lt;table class=&#34;table table-bordered&#34; &gt;



&lt;tr&gt; 

&lt;th &gt;
Message type&lt;/th&gt; 

&lt;th &gt;
Where you can export on MC&lt;/th&gt; 

&lt;th &gt;
System-generated filename&lt;/th&gt; 

&lt;th &gt;
Contents of exported file&lt;/th&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


All db-related message types&lt;/td&gt; 

&lt;td &gt;


&lt;strong&gt;Message Center&lt;/strong&gt; page&lt;/td&gt; 

&lt;td &gt;


&lt;code&gt;vertica-alerts-&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;timestamp&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;sv&lt;/code&gt;&lt;/td&gt; 

&lt;td &gt;












&lt;p&gt;Exports messages in the Message Center to a &lt;code&gt;.csv&lt;/code&gt; file. Message contents are saved under the following headings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Create time&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Severity&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Database&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Summary (of message)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Description (more details)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


MC log files&lt;/td&gt; 

&lt;td &gt;


&lt;strong&gt;Diagnostics&lt;/strong&gt; page&lt;/td&gt; 

&lt;td &gt;


&lt;code&gt;mconsole-&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;timestamp&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;.log&lt;/code&gt;&lt;/td&gt; 

&lt;td &gt;










&lt;p&gt;Exports MC log search results from MC to a ** &lt;code&gt;.log&lt;/code&gt; file under the following headings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Time&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Type (message severity)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Component (such as TM, Txn, Recover, and so on)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Message&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


Vertica logs&lt;/td&gt; 

&lt;td &gt;




&lt;p&gt;&lt;strong&gt;Manage&lt;/strong&gt; page&lt;/p&gt;
&lt;p&gt;Double-click any node to get to the details and then click the VerticaLog tab&lt;/p&gt;
&lt;/td&gt; 

&lt;td &gt;


&lt;code&gt;vertica-vertica-&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;db&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;-&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;timestamp&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;.log&lt;/code&gt;&lt;/td&gt; 

&lt;td &gt;










&lt;p&gt;Exports log search results from MC to a &lt;code&gt;.log&lt;/code&gt; file under the following headings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Time&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Type (message severity)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Component (such as TM, Txn, Recover, and so on)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Message&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


Agent logs&lt;/td&gt; 

&lt;td &gt;




&lt;p&gt;&lt;strong&gt;Manage&lt;/strong&gt; page&lt;/p&gt;
&lt;p&gt;Click any node to get to the details and then click the AgentTools Log tab.&lt;/p&gt;
&lt;/td&gt; 

&lt;td &gt;


&lt;code&gt;vertica-agent-&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;db&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;-&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;timestamp&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;.log&lt;/code&gt;&lt;/td&gt; 

&lt;td &gt;










&lt;p&gt;Exports agent log search results from MC to a &lt;code&gt;.log&lt;/code&gt; file under the following headings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Time&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Type (message severity)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Component (such as TM, Txn, Recover, and so on)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Message&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


Query details&lt;/td&gt; 

&lt;td &gt;




&lt;p&gt;&lt;strong&gt;Activity&lt;/strong&gt; page&lt;/p&gt;
&lt;p&gt;Click any query spike in the Queries graph to get to the Detail page.&lt;/p&gt;
&lt;/td&gt; 

&lt;td &gt;


&lt;code&gt;vertica-querydetails-&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;db&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;-&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;timestamp&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;.dat&lt;/code&gt;&lt;/td&gt; 

&lt;td &gt;
















&lt;p&gt;Exports query details for the database between &amp;lt;&lt;em&gt;timestamp&lt;/em&gt;&amp;gt; and &amp;lt;&lt;em&gt;timestamp&lt;/em&gt;&amp;gt; as a tab-delimited &lt;em&gt;.dat&lt;/em&gt; file. Content is saved under the following headings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Query type&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Session ID&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Node name&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Started&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Elapsed&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;User name&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Request/Query&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;&lt;/tr&gt;

&lt;tr&gt; 

&lt;td &gt;


MC user activity&lt;/td&gt; 

&lt;td &gt;




&lt;p&gt;&lt;strong&gt;Diagnostics&lt;/strong&gt; page&lt;/p&gt;
&lt;p&gt;Click the Audit Log task&lt;/p&gt;
&lt;/td&gt; 

&lt;td &gt;


&lt;code&gt;vertica_audit&amp;lt;&lt;/code&gt;&lt;em&gt;&lt;code&gt;timestamp&lt;/code&gt;&lt;/em&gt;&lt;code&gt;&amp;gt;.csv&lt;/code&gt;&lt;/td&gt; 

&lt;td &gt;














&lt;p&gt;Exports MC user-activity results to a &lt;code&gt;.csv&lt;/code&gt; file. Content is saved under the following headings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Time&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;MC User&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Resource&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Target User&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Client IP&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Activity&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/p&gt;

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