Set up email alert process in Connect CDC Director - Connect_CDC - connect_cdc_mimix_share - 5 - 5.8

Connect CDC Advanced User Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
5.8
Language
English
Product name
Connect CDC
Title
Connect CDC Advanced User Guide
Copyright
2023
First publish date
2003
ft:lastEdition
2023-09-27
ft:lastPublication
2023-09-27T18:12:55.651884

To generate email alerts, right-click the model or the Hosts, Servers, Tables branch, and select Alert Action.

  1. Select Send email to [one address per line, Enter].

    The parameters become available to update the information:

  2. In the Define alert for message levels box, you can opt for messages of certain level or greater: FATAL, ERROR, WARN, INFO, DEBUG, ANY. Messages are buffered until something (for example, a number of messages or time limit since the last one was added to the buffer or a if a particular message level arrives) causes the message to be sent.

  3. Enter email addresses in the To box, pressing Enter to start a new line after each name in a series of names.

    Note: It is recommended that you use a group alias whose members are managed on the email server rather than the model.
  4. Enter the subject line information in Subj (for example, Connect CDC error alert or <model name> data movement problem).

  5. Select Send email immediately if alert is_________ or above to specify a level of email alert to send without any waiting period then select a level (FATAL, ERROR, WARN, INFO, DEBUG, ANY).

  6. Set Max alerts per email. This specifies the maximum number of logging events collected before email is sent and limits message size. (100 is recommended.)

  7. Set Timeout (secs), which specifies the number of seconds of inactivity before a pending email is sent. (300s [5 minutes] is recommended.)

    Note: Send email immediately, Max alerts per email, and Timeout work together: An email with the pending alerts is sent out whenever any of the three criteria is met.

    To be notified quickly, choose a low timeout not a low number of alerts per email. Use the number of alerts per email to keep emails to a reasonable size. Setting it too low can degrade system performance in case of a surge in alert frequency. Similarly, choosing a trigger level in the Send email immediately field at or below INFO can cause a flood of email messages and slow down the system.

    We recommend the following default values:

    • Number of messages per email: 100

    • Timeout: 300s (5 minutes) - lower for quick notification

    • Threshold level: INFO - higher for fewer alerts reported

    • Trigger level (Send email immediately): ERROR.

  8. In the From box, enter the email address to which you want to respond, (for example, a system administrator). This address also serves as a return address for emails that cannot be delivered. This is optional but recommended if you are sending email outside your local domain.

    This must at least contain an @ sign in the format of a valid address although the address does not have to be real (for example, “no_reply @xxx.com”).

  9. In SMTP server, enter the host name or IP address of the Connect CDC Director host machine’s local SMTP server. This entry must be reachable from the host and must accept messages from the sender address to the recipient address. This is required.

  10. Click Test to verify that the message is sent in the correct format. Test email attempts to send the message (without replacing the Text: parameters) to each address on the To: list, and writes details of the operation to the Connect CDC Director log.

  11. Click OK when you are satisfied with your specifications.

  12. Commit the model.

  13. In Connect CDC MonCon, load the new model version (or do Model Update) to get the alert notification from the XML.

  14. Start email notification in Connect CDC MonCon.