System Events

SelectSystem Configuration>System Events.

FME Flowpublishes messages about significant events, such as when a repository is created, or a system backup is performed. To see all events and their descriptions, selectSystem Events>Configurations. For more information about the events, seeEvent Descriptions(below).

所有事件默认发送消息。你可以disable and enable which events are enabled as desired. On the Configuration page, select the events you want to configure, and clickActions>EnableorDisable.

Some events are configurable. For example, you can adjust when the License Expiry event begins sending messages. On the Configurations page, click on the License Expiry event. On the Configuration: License Expiry page, adjust theDays Before License Expiryfield, and clickSave.

Monitoring System Events

您可以监视系统事件在以下方式s:

• Send email notificationswhenever an event occurs. To configure:
  1. Ensure thatSystem Emailsettings are configured.
  2. Click on an event type you want to monitor. On the Configuration page for that event, make sureEnable ConfigurationandSend Email Notificationsare both enabled.
  3. Where applicable, configure any Notification Schedule settings specific to the event. For example, the Low Credit event requires you to configureCredit Hours Remaining.
  4. Complete the fields under Email Settings, where applicable:
     • Email To, Email Cc, Email Bcc- Corresponds to the "To", "CC", and "BCC" fields, respectively, in standard email messages. Separate multiple recipients with commas. For example:recipientOne@example.com,recipientTwo@example.com,recipientThree@example.com
     • Email Subject: Corresponds to the "Subject" field in standard email messages.
     • Email Format: The format of the email, either plainTextorHTML.
     • Email Template: The message body to use for delivery. This is a template that allows the use of various tags that are replaced with dynamic information before delivery. For more information, seeEmail Template Language.
  5. ClickSave.
• In an Automations workflowthat is initiated by one or moreFME Flow System Eventtriggers. For example, this workflow notifies an Amazon SQS queue every time a repository is created:



For more information, seeAutomations.

• On the System Events History page. SelectHistoryunder System Events to see a history of all enabled events.

When viewing the System Events History page, keep in mind the following:

• Use theTypefield to filter by event type.
• By default, this page displays events from the previous one week. To change, configureSystem Event HistoryunderSystem Cleanup>Scheduled Cleanup.
• If yourDistributed/Fault Tolerant InstallationofFME Flowdoes not use a PostgreSQL database server for theFME Flow Database, the Date column may not reflect millisecond precision. As a result, event Id's may appear in random or reverse order.

Event Descriptions