LogoLogo
  • LIBSAFE Advanced Pro - Preservation Administrator Manual
  • System configuration
  • Preservation configuration, basic sections
    • Ingestion sanitizers
      • Ingestion sanitizers detail
      • Ingestion sanitizer editing
    • Preprocessors
      • Preprocessor detail
      • Creation of the preprocessor
      • Preprocessor editing
    • Ingestion checks
      • Ingestion check detail
      • Creation of the ingestion check
      • Ingestion check editing
      • Main ingestion checks
    • Metadata filters
      • Metadata filter detail
      • Metadata filter creation
      • Metadata filter editing
    • Dissemination Information Package (DIP) profiles
      • DIP profile detail
      • Creation of DIP profiles
      • DIP profile edition
    • Connectors
      • Connector Activation
      • Connector details
    • File formats
      • File format detail
    • File format characterizers
      • File format characterizer detail
    • File format validators
      • File format validator detail
    • File format evolvers
      • File format evolver detail
    • Automatic audit schemas
      • Automatic audit schema detail
      • Automatic audit schema editing
  • Metadata collision groups
    • Unicity metadata collision groups
      • Unicity metadata collision group detail
      • Creation of a unicity metadata collision group
      • Unicity metadata collision group editing
    • Versioning metadata collision groups
      • Versioning metadata collision group detail
      • Creation of a versioning metadata collision group
      • Versioning metadata collision group editing
  • Metadata schemas
    • Metadata schema detail
    • Creation of a metadata schema
    • Metadata schema editing
  • Collection tree
  • Dissemination Information Package (DIP) configured profiles
    • Detail of the DIP profile configured for preservation plans
    • Configuring a new DIP profile for preservation plans
    • Editing DIP profiles configured for preservation plans
  • Preservation areas
    • Preservation area detail
    • Create a preservation area
    • Preservation area editing
  • Preservation plans
    • Preservation plan detail
    • Preservation plan creation
      • Preservation area and plan parameters
      • Metadata
      • Associated thumbnail
      • Storage
      • Sanitizers
      • Preprocessors
      • Checks
      • File format characterizers
      • File format validators
      • File format transformers
      • Digital signature
      • Rollback
      • Data Integrity
  • Alarms and notifications
    • Alarm definition
    • Configured alarms
      • Configuring an alarm: example 1
      • Configuring an alarm: example 2
    • Notifications panel
  • Glossary of Terms
  • Frequently asked Questions and additional considerations
    • About ingestion and retrieval
    • About audit
    • Miscellaneous
  • Annexes
    • Automatic ingestion and retrieval processes
      • Automatic ingestion
      • Automatic retrieval
    • Regex expressions – User reference
    • List of error messages found in audits (log)
Powered by GitBook
On this page

Was this helpful?

  1. Alarms and notifications
  2. Configured alarms

Configuring an alarm: example 2

With the available alarms, we configure an instance that will notify us of all ingestion jobs finished successfully, for the area ‘ObjectName Area’. This is for routine purposes, so a daily notification or a notification for as many as 25 jobs will suffice.

There is the preparameterized and easy to use alarm Ingestion job finished successfully, so we make good use of it.

The parameters to configure are:

  1. General:

    1. Criticality = Normal.

    2. Importance = Normal.

    3. Check period: every hour. We want a daily notification, but by checking every hour we allow for several notifications in case of a lot of finished ingestion jobs.

    4. User comment: something in the line of ‘Ingestion jobs finished successfully in area ObjectName Area’.

  2. Alarm (these parameters are specific of this alarm)

    1. Achieved state: we can see it is fixed to FinishedOK. As it is fixed, we know it is only for information purposes, and we can forget about setting it.

    2. Preservation area. We select the area ‘ObjectName Area’.

    3. Minimum size. We do not use it, so it is not considered.

  3. Notification:

    1. Message building rule. As the text from several jobs may be added, we set it to Add the notification text under new execution.

    2. Maximum number of messages without sending e-mail. We set it to 25, meaning that if 25 or more messages are generated before the maximum time without sending e-mail (which will be configured to 1 day), the notification will be sent without the wait.

    3. Maximum time without sending e-mail. 1 day, that is the periodicity with which we want -in principle- to receive the notification about these jobs.

    4. Receiver (user). Whoever we want.

    5. Receiver (group). Whichever we want; a preservation administrator being most suitable, as this reports on usual preservation activities in an area.

    6. Can deactivate notification. Checked, as it has no sense for these individual notifications to be persistent.

    7. E-mail sending deactivates notifications. Checked, as this alarm is mostly for routine information purposes, and should not call our attention when accessing the notifications panel.

PreviousConfiguring an alarm: example 1NextNotifications panel

Last updated 3 years ago

Was this helpful?