Date & time format, Queue size, Queue ratio for archive and Login banner are accessible under Settings > General after successful login.
Core instance alias
The instance alias functions as a nickname to help distinguish between different MetaDefender Core instances, particularly in environments with multiple deployments. Please note that the instance alias is separate from the instance name and serves a different purpose.
By default, the alias is an empty string. Users may choose to leave it empty to opt out of including it in email notifications.
The alias must comply with the following requirements:
- Maximum length of 64 characters
- Must not contain trailing spaces
- Must not include Unicode control characters
- Must be unique (it cannot duplicate an existing alias in the database)
The instance alias is not included in export packages and is therefore unaffected by export/import operations or upgrade processes.
Date & time format
There are 2 supported formats
- AM/PM format
- 24 hours format
Queue size
This setting will help to adjust the overall queue size (scan queue) of Metadefender Core service.
Setting this configuration too high could affected Metadefender Core itself and other services on the server.
Queue ratio for archive
This setting will help to adjust the percentage of queue size spent on processing archive files. The default value is 25% and can be set to 75% for maximum.
The higher the value of queue ratio set for archive, the fewer slots are available for processing new client requests, which may cause Metadefender Core to easily respond with HTTP code 503 and message Server is too busy. Try again later.
During the processing of nested archives, the number of queue slots allocated to extracted files may temporarily exceed the configured ratio. This behavior is by design. Enforcing the ratio as a hard limit could prevent child files from acquiring queue slots while the parent archive is holding one and waiting for them to finish, which would result in a deadlock.
Track Rejected Requests
By default, rejected requests (such as those exceeding file size limits or when local scan is disabled) are not stored in the processing history. Administrators can enable the option to store these rejected requests due to the following reasons for future tracing and analysis.
All requests rejected will receive a verdict of "Rejected" in the Processing History.
Note: This feature has not supported for multipart uploading yet.
Rejection reasons
- File Size Limitations: Exceeding maximum file size and maximum download size limits
- Feature Availability: Local scan functionality is disabled
- Workflow Constraints: Workflow rule is not within its active time period
- Engine Readiness:
- Insufficient mandatory engines available
- Insufficient active antivirus engines
- Insufficient up-to-date engines
Login banner
Enable this option to show login banner when user in the login page.
The message will be shown in the end of login page.
System Banner
Remind when Core version is out of support
This setting allows you to enable or disable notifications when the MetaDefender Core version reaches end of support. It also provides the option to configure the reminder timing for such notifications.
