Register Alfabet Components as Microsoft Event Log Source

To write log information of an Alfabet component to the Windows Event log, configure the following in the server alias configuration of the component:

Open the Alfabet Administrator.
Click the Alfabet Aliases node in the Administrator explorer. The right pane displays a list of all available alias configurations.
Click the server alias in the list and click the Edit button.
In the editor that opens, go to the Server Settings > Logging tab.
Activate the Activate Logging checkbox.
Specify the following in the Windows Event Logging box:
- Event Source Name: Optionally alter the name that is used as Source in the Windows Event Log. By default the Event Source Name parameter is the server alias name.
- Event Base ID: If this attribute is defined, an event ID will be written into all entries in the Windows Event Log. The event ID is calculated from the event base ID defined in this attribute plus the logging level number. The logging level number is 2 for Error , 4 for Warning , 8 for Information and 16 for Debug.The event base ID must be an integer between 30000 and 65535.
Go to the Server Settings > Logging Details tab.

The log levels can be fine-tuned individually for different processes such as Alfabet RESTful services or event management. The table lists the following logging details for separate activation:

System: Activates logging of the basic functionalities of the Alfabet component. In addition, the following information is logged:
- Information about the execution of jobs scheduled in the Job Schedule functionality is written to the log file if the log level Information is selected.
- Information about JSON responses for ADIF sessions executed in the scope of the ARIS - Alfabet Interoperability Interface are written to the log file if the log level Debug is selected.

UserLogon: Activates writing of the following information to the Windows® Event Log: the registration in the event log, shutdown of the Alfabet Web Application and the reason for shutdown, and user log in and log out. If user authentication and authorization is done via synchronization with an external LDAP server, each LDAP authentication, LDAP authorization and search for a user in LDAP is also logged. The respective messages all start with LDAP.

Please note the following:

Logging to file or Seq server is not supported for this log subject.
If multiple Alfabet components are involved in a login action and both are configured to write messages to the Windows Event Log, both components will write a separate message for the action. Management of authentication via data synchronization with an external LDAP server may also result in multiple entries per login.
When a user logs in or out of the Alfabet components, the user name and the information whether login or logout was successful will be logged. This does not only include login/logout to the Alfabet user interface but all processes that require a login such as sending requests to the Alfabet RESTful API.
If the Server Settings > General > Update History User Name attribute of the server alias is set to TECH_NAME , the Technical Name defined for the user will be used in the Windows Event Log instead of the user's name. It is essential to define the Technical Name attribute for all users if this setting is used. The Technical Name can only be used in the Windows Event Log if authentication is performed via the user data in the Alfabet database.

Workflow: Activates logging for the Alfabet workflow functionality.
ADIF: Activates logging of ADIF execution. The log information written to the log file for ADIF processes includes information about commit actions as information and about rollback actions as warnings. To include logging for the Job Schedule functionality, the ADIF log level must be Debug.
ADIF execution cannot be logged via the Windows® Event Log.
Report: Activates logging for the execution of configured reports.
REST: Activates logging of the Alfabet RESTful API functionality. If the Alfabet RESTful services are used, it is recommended to activate central logging of REST functionalities because the return values for the RESTful services do not cover all error details for security reasons. For example if the Alfabet Server is required to execute an ADIF job that shall be executed via a RESTful service call, the RESTful services will inform about forbidden access only and the information about the component that could not be accessed is only provided via central logging.
SSO: Activates logging of activity related to a configured SAML authentication. This setting is only relevant if the Alfabet Web Application is configured to use SAML for user authentication.
Event: Activates logging of the execution of events configured via the Event Management functionality.
Log messages for event execution is also written to the ALFA_EVENT_BUS table in the Alfabet database.
Conditions: Activates logging for the execution of conditions. Conditions are defined in Alfabet Expand to hinge visibility of elements of the Alfabet user interface on the availability of defined preconditions.
License: Activates logging for the Alfabet license manager functionality.
MonitoringEvents: Activates logging for the monitoring of database availability. This option must be activated to test the database availability via the mechanism described in the section Checking the Accessibility of the Database below.
WebApplication: Activates logging of web based functions of the Alfabet Web Application. Please note that activation of this log option is increasing the amount of messages written to the log file considerably. It is recommended to activate this option only if the cause of issues cannot be detected via the logging provided by the other log options.
Email: Activates logging of automatic sending of emails.

Set the following in the rows of all the logging details that you would like to activate:
- In the Level column, define the log level. The following log levels are available:
  - None: no log output.
  - Error: only messages about errors are logged.
  - Warning: error messages and warning messages are logged.
  - Information: error messages, warning messages, and informational messages are logged.
  - Debug: error messages, warning messages, informational messages and all debugging and tracing messages are logged.
  For the options Workflow , Report and Conditions , only error and warning messages are available. The log levels Information and Debug should not be selected for these options.
- Click in the cell in the Event column to activate writing of the log messages to the Windows® Event Log with the component name defined in the Server Settings > Logging tab with the Event Source Name attribute. An x will be displayed in the cell after activation.
Click OK to save your changes.

After having performed the configuration, you can register the server alias as source to the Windows event log via the AlfaAdministratorConsole.exe.

Run the AlfabetAdministratorConsole.exe as administrator with the command line:

AlfaAdministratorConsole.exe -msalias AliasName -enablewindowseventlog

where AliasName must be substituted with the name of the server alias.