Reporting best practices
Create reports to maximize server performance and save time!
This guide explains how data is processed for reports. It also gives you some tips on how to create them to maximize account performance.
Generating an instance of a report
Every time we enable a new report and then save it in the application, we can select default parameters like Period, Users, or Event Rules in order to speed up the report generation process.
This is not just to make it easier for the user when generating the report, but also to avoid data processing when they generate the report. So it is quite important that we pay attention to this step.
Here are some tips on parameters:
- Try not to leave blank fields. If you don´t select any parameters, the system will not prepare the data for the report. This means the user will have to wait for it to be processed.
- Select the proper Tags and Event Rules. If you select more users or event rules than needed, then when the system processes the data it will be including information that you don't need. This isn't efficient and data processing will take longer.
- Time periods that include the current day will take longer since new data will have to be processed.
- Hide parameters that the user doesn't need to change. It will avoid unnecessarily “testing” that might end up queuing reports.
- Scheduling larger reports to send via email helps improve performance.
Whenever we generate a report, the data related to that report must be processed. When we save a new report template on an application, the data related to that report (for the specific parameters we have selected) will be processed automatically every night. This lets the report be generated immediately.
For example, if we save an Event Rule report with parameters for the speeding event rule and Fleet A, then the data for the users that belong to Fleet A will be processed overnight for the Speeding event rule. When we generate the report, it will take less time to be delivered.
The data also will be ready for other reports using the same information - for example, Event Rule Total report EV1001.
It must be taken into account that when a report is saved, the data will be processed from the next day onwards. So if we generate a report requesting information that includes earlier dates than today, that data will need to be processed.
Summarizing, it is very important to select the right parameters in order to save time and avoid performance issues.
Scheduling reports at midnight might sound like a good idea, but not for GPS tracking. When you schedule reports for 00:00, remember that some data is still coming in from the previous day. For that reason, the batch processing of already saved reports usually starts at 2:00 am. We recommend a later scheduled report time than midnight to allow all of the previous day's data to get to the server.