Page History
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
Summary: In this video, COO Henning Kunz will show you how to get a session up and running after you’ve had a collection pause in iDNA Applications.
...
- A network issue (e.g. downtime).
- The log.nsf was not accessible: If the ID file has no access to log.nsf, no session data can be collected.
- Insufficient access rights: If the ID file does not have access to the server, no session data can be collected.
- The most common issue is that the disk is full. If the appliance runs out of disk space, no session data can be stored.
Fixing These Issues (in Two Steps)
- Firstly, restore the access to the server or fix the disk full problem. Afterwards, data can be collected again.
Secondly, set cutoff dates (e.g.: today minus 7 days). If your logs are configured to store history for longer, set the date to today minus the number of days.
Info By default, the log stores the history for up to seven days.
Setting the Cut-Off Dates on the Appliance
- On the IFA (iDNA for Applications) appliance's dashboard, click on Settings > System configuration. You will be taken to a new page.
- On this System configuration page, click on Session data statistics. All your servers and their respective cutoff dates will be displayed.
- Click on Show/hide advanced controls. Here, you will see your sessions and their pre-configured cutoff dates.
- Click on a cutoff date to change it and click on Update older cutoff dates.
...