| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Introduction
...
Basically, we use the log framework log4net for all components. With this framework, different appenders can be defined per component. By default, these are configured as follows:
...
The CoreOne Suite uses a Log-Framework for all it’s components that allows you to configure multiple appenders. Those appender range from simple file logs to custom implementations where you can integrate the messages into your custom build monitoring solution. By default all applications come with a certain set of appenders configured. This document list those appenders and where the appropriate output can be found.
CoreOne Suite Application Service
DB Appender -->
...
Table log_
...
log
File Appender --> C:\ProgramData\itsense\LOG\
Event Log Appender --> Windows Event Log (Errors only
...
All IAM processes are logged here (create account, enter person, etc.)
For examplel:
...
)
...
CoreOne Suite System Connector
File Appender --
...
> C:\ProgramData\itsense\LOG\
...
CoreOne Suite Routing Service
File Appender --
...
> C:\ProgramData\itsense\LOG\
...
CoreOne Suite Workflow Designer
File Appender --
...
> C:\ProgramData\itsense\LOG\
...
| Code Block |
|---|
19.06.2017 17:19:32: WARN - Try load assembly System.Activities.Presentation.AeroLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 with resolver MovingAssemblyLoader: null
19.06.2017 17:19:32: WARN - Unable to load assembly System.Activities.Presentation.AeroLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
19.06.2017 17:19:32: WARN - Try load assembly System.Activities.Presentation.AeroLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 with resolver MovingAssemblyLoader: null
19.06.2017 17:19:32: WARN - Unable to load assembly System.Activities.Presentation.AeroLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
19.06.2017 19:33:51: WARN - Try load assembly System.Activities.Presentation.AeroLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 with resolver MovingAssemblyLoader: null
19.06.2017 19:33:51: WARN - Unable to load assembly System.Activities.Presentation.AeroLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
19.06.2017 19:33:52: WARN - Try load assembly System.Activities.Presentation.AeroLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 with resolver MovingAssemblyLoader: null
19.06.2017 19:33:52: WARN - Unable to load assembly System.Activities.Presentation.AeroLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
19.06.2017 19:33:57: DEBUG - GetXaml : Begin
19.06.2017 19:33:57: DEBUG - GetXaml : End
|
CoreOne Suite Authentication Service
File Appender --
...
> C:\ProgramData\itsense\AuthenticationService_900000\logs
...
The file logs are not protected separately, as they are only directly accessible on the server.
The retention period is limited to the size by default. Default value is 10MB. DPK specific values you would have to check on the system. Via Windows backup you would have to clarify via hoster.
This info is related to the system logs. Audit Trail, Login History etc. is not considered here.
How-to article
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
Related article
...
How-To change path of the log-files: How-To configure Logs (Authentication Service)
CoreOne Suite Admin UI
CoreOne Suite Admin UI (Web) is not enabled by default. However, it can be enabled with the following instructions: How-to enable a log file for the Admin UI
CoreOne Self-Service Portal
CoreOne Self-Service Portal is not enabled by default. However, it can be enabled in the following way: How-To enable a log file for the Self-Service Portal