In Nepton, it is possible to view service log information. The service log stores information about, for example, single sign-on logins and information imported and exported to/from the service. The following information is stored in the service log:
- Person import
- Person export
- Person status -integration (for example Elisa Ring)
- LoginetsService (customer specific, not in general use)
- Salary integration
- System administration
- PaymentGroupExportUsingAPI
- Basic activities import (BaseActivityImport)
- Project import
- Settings history
- SSO
- Locations import
- WebService
Information stored in the service log is always kept for at least nine months.
The time of the service log's log entry is the time on the server when logging of the event has started. The content of the service log message may have a different time depending on how long it took to complete the operation.
The service log can be found in Employees > Administration.
General view of Service Log:
Succeeded operation is shown with green magnifying glass icon.
Warning is shown with yellow magnifying glass icon. For example if the import was succeeded, but there was something exceptional/to be noted, is warning shown.
Failed operation is shown with red magnifying glass.
Further details can be viewed by clicking on the magnifying glass.
It is possible to filter the service log results. The following filters are in use:
Start date and end date: Date filters can be used to define a time period for the search
Type, with the following options:
- Failed
- Notification
- Succeeded
- Warning
Area, with the following options:
- Base event import
- Export of payment groups
- Export of persons
- General notifications
- Import of persons
- Location import
- LoginetsService
- Person status integrations
- Project import integration
- Salary data integration
- Settings
- SSO
- System administration
- WebService
Source tells in more detail whether it is an import/export and from/to which system the information has been transferred.
Summary briefly tells whether the function succeeded/failed and the reason for the failure. Information can be retrieved from the field, which is stored in the summary field. For example, a personal identification number might be such information.
For example, it is possible to directly search the log data of failed imports of basic events for a certain day using the search criteria:
Failed transmission is shown with red maginifying, and succeeded with green magnifying glass. Further details can be viewed by clicking on the magnifying glass.
The log details tell you which incorrect data caused the transfer to fail. The reason for the failure of the transfer can be, for example, that there is no data to be imported. In this case, you have to check in the service that creates the imported file, why the material has not been created.
The details of the service log can be opened in its own tab by pressing the magnifying glass with the right mouse button. This allows the search results to be kept in their own tab even when viewing the log details.
In the example below the transfer has failed because of access problems to the server. In this case you would need to check the server access details.
The details of the log can also contain the data transmitted in the transfer in a file-storable format. In problem situations, the data may also contain error information, which is useful when solving the problem. The data can be downloaded in its original form by pressing the Download button:
Please note that scheduled integrations may appear in the service logs with a slight delay. Although the integration is triggered at the configured time (for example at 04:00), processing and updating the logs may take a few minutes. As a result, the integration may appear in the user interface at 04:01 or 04:02. This is normal behaviour. If it is important for the integration to appear as close as possible to a specific time in the UI, you can schedule it slightly earlier (for example at 03:58 or 03:59).