Viewing Endpoints Database Information
In the Endpoints Stats tab of the Configuration > Storage page, you can view detailed information about ObserveIT endpoints.
To view details about endpoints that were recorded in the SQL database
-
Navigate to Configuration > Storage Management > Storage.
-
Click the Endpoint Stats tab to view a list of the endpoints that were recorded in the database.
The number of endpoints on the page out of the total number of endpoints is displayed. By default, the page can show up to 20 endpoints; you can change the default by selecting 50 or 100 from the Items per page drop-down list above the table.
The following information is displayed for each endpoint in the list:
-
Name of the recorded server.
-
Size of the server's recorded data (number of slides).
-
Total number of sessions in the server.
-
Dates of the first and last session recorded for the server.
The date of the first sessions in the database may be later than what you would expect from the database actual age. For example, if the ObserveIT database was installed on the 1st of January 2014, and an archiving job was run on the 1st of October, archiving all sessions older than the past month, the "First Session" parameter will show the 1st of September. To find these sessions, navigate to the Configuration > Archive > Diary tab.
-
Important Notes:
-
The more sessions recorded on an endpoint, the more data is used. Considerations must be taken when dealing with very large database sizes, and proper SQL tuning needs to be performed in order not to reduce the overall server performance.
-
SQL Express is not recommended for use in a production environment as it is limited in database size. It is recommended for use only in a testing environment.
-
By default, ObserveIT never deletes data from the database, however, you can use the Archive tab to remove or archive old server data. See Archiving ObserveIT Data.
-
When archiving is used, the database size may not shrink in actual physical size. To reduce the overall size of the database, use proper SQL server maintenance procedures.