Logging and monitoring
The services log to std:out. Monitoring solutions such as Elasticsearch and Kibana elk can be attached.
The logging can be enabled as described for the individual containers in Setup and configuration.
Security logging
The following security related events according the NEXEED logging guidelines are logged: - INPUT_VALIDATION_FAILED - ENDPOINT_DOES_NOT_EXIST - UNAUTHORIZED_ACCESS - UNAUTHENTICATED_ACCESS - TLS_DISABLED* - INVALID_SCOPE - GRANT_UNSUPPORTED
*The TLS_DISABLED event is logged when the Web Portal itself is not configured to listen on HTTPS or does not use a secured communication to the database and message broker
Database migration logging
Database migration logs are now managed through lifecycle logging, ensuring structured and consistent tracking of migration events. These logs provide visibility into the migration process, helping to confirm successful updates or diagnose failures. The following lifecycle log events are recorded:
DATA_MIGRATION_STARTED: Logged at the start of the migration process. DATA_MIGRATION_SUCCESSFUL: Logged upon successful completion of the migration. DATA_MIGRATION_FAILED: Logged when a migration fails, including error details.
IAS logging guidelines configuration
The Web Portal follows IAS logging guidelines with the following logger level configuration:
-
Default -> Warning (guideline level: WARN)
-
SECURITY -> Information (guideline level: INFO)
-
LIFE-CYCLE -> Information (guideline level: INFO)
The SECURITY and LIFE-CYCLE logger levels are required to be set at Information level as per IAS logging guidelines.