LogoLogo
  • LIBSAFE Advanced Pro - System Administrator Manual
  • Introduction
    • Basic concepts
    • General considerations
  • System configuration
    • Storage
      • Storage groups
      • Disks
        • Different storage system types and their integration in LIBSAFE
      • Datamover
    • Digital signature profiles
      • Certificates for the digital signature service
    • Access
      • Users
        • Two-Factor Authentication (2FA)
      • Groups
      • User permissions
    • Alarms and Notifications
      • Alarm definition
      • Configured alarms
        • Configuring an alarm: example 1
        • Configuring an alarm: example 2
      • Notifications panel
    • Extras and tools
      • Programmed tasks
      • Logs manager
      • File management
      • Database management
      • Database management (read-only mode)
      • Web interface configuration variables
      • Configuration variables
      • API system services
      • Server cluster - Parallelization
        • Details of activity in one node
        • Editing or creating a node and its associated services
        • Node deactivation
        • Deleting nodes
        • Processing Cluster customization
      • SAML integration as a SSO (Single Sign On) when login in LIBSAFE
    • License
  • Preservation configuration
    • Ingestion sanitizers
      • Ingestion sanitizers detail
      • Ingestion sanitizer editing
    • Preprocessors
      • Preprocessor details
      • Creation of the preprocessor
      • Preprocessor editing
    • Ingestion checks
      • Ingestion check details
      • Creation of the ingestion check
      • Ingestion check editing
      • Main ingestion checks
    • Metadata filters
      • Metadata filter detail
      • Creation of metadata filter
      • Metadata filter editing
    • Dissemination Information Package (DIP) profiles
      • DIP profile detail
      • Creation of DIP profiles
      • DIP profile edition
    • Connectors
      • Connector Detail
      • Create a new connector
      • Edit a connector
    • 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
  • Frequently Asked Questions (FAQ) and additional notes
Powered by GitBook
On this page

Was this helpful?

  1. System configuration
  2. Extras and tools

Logs manager

PreviousProgrammed tasksNextFile management

Last updated 3 years ago

Was this helpful?

LIBSAFE has a log manager for the actions in the web interface. It is possible to access and check the different messages generated when carrying out tasks through the web interface.

Each message will show date, the actual message, key words, user name (who generated the action), type of action, the message status code and the code level.

A series of filters can be applied to search for the log messages generated:

  • Message

  • Keywords

  • Date of creation. By range of dates (from / to)

  • Action (Activate, Search, Session Close, Create, Deactivate, Edit, Eliminate, Session Start, Other).

  • Code (Ok, Warning, Error).

  • User name. Name of the user who carried out the action generating the message.

Additionally, it is possible to access the logs generated by the different processes in the system. These log files provide relevant information to these execution processes, resulting in very helpful guidelines.

In the same section, after the actions log, the system shows the log file section, from which it is possible to access:

  • The web interface log files (libsafe.webinterface).

  • The log files of the different execution modules in LIBSAFE (libsafe.webinterface.net).

  • The execution files’ log files related to sharing and stop sharing folders (libsafe.webinterface.cmd).

The files are available for query from the web interface, or to be downloaded.

Likewise, and in case of jobs ended in error (ingestion, retrieval, etc.), if the user has the Advanced Configuration permission, the system will show the contents of the log file of the particular failed process in the job detail.