# Report Statistics and Real-time Data
Provide visual data display and statistics functions for daily reporting data, including two modules of reporting statistics and real-time data. The function description of the module is as follows:
- Above report statistics: review data receipt within the last 7 days of project disable / enable management for buried site events
- Real time data: includes real-time storing and error data. Real time entry pages view the real-time entry data; Error data pages are counted and error reportable every 10 minutes.
# I. Function Access and Applicable Roles
Move the mouse into the navigation bar 'Data Management' and click 'Buried Point Management' to enter the buried point management function module.
The default company supervisor and administrator roles can enter the buried point management module for viewing and editing operations, and the analyst role can be assigned permission to use this part in Project Management → Role Management.
| Permissions | Company Supervisor | Administrator | Analyst | Ordinary members |
|---|---|---|---|---|
| View report statistics, live data, and Debug mode | ● | ● | △ | ○ |
| View report statistics, live data, and Debug mode | ● | ● | △ | ○ |
Permission description:
● Role must have
▲ The role has the permission by default, but can revoke
△ The role is not available by default, but can be authorized
○ Role must not have
# II. Report Statistics
Support to view data receipt for the 'Last 7 Days' project and disable/enable management of buried events.
This page consists of the Settings area and the Data Details area.
# 2.1 Query Settings
Query Time Settings: Query time index data storing time. Support customization to view data receipt for any time period in the last 7 days. By default, when the end time is today, click the refresh button on the right to update the end time to the latest time (update the statistics every 10 minutes).
Interval data: Interval data shows the number of received, stored, error stored and stored failures in the set time period.
- **Received **data means data received by a receiver;
- **Stored **includes correct data and wrong data;
- **Error **stored** **refers to data containing attribute level errors such as event attribute name is invalid, attribute type is invalid, etc. This kind of data can be stored normally, and the error attributes in the data will be left blank;
- **Stor**ed** failure **refers to the data that cannot be stored due to the illegality of the reported data such as missing #event_name and exceeding the limited range of #event_time.
# 2.2 Statistical Details and Event Management
The data details area displays the received, stored, error stored and failed data under each event (user feature), and supports operations such as disable/enable settings for the event or viewing the error details of the event.
- Disable and enable events
- Disable events: Click 'Disable' to set the event to a disabled state, and the disabled events will no longer be received into the library. The disabled state takes effect 10 minutes after the setting.
- Enable events: Disable events can be re-enabled. The data reported by the server will take effect 10 minutes after the enabling setting, and data reported by the client will need to be enabled the next time the user opens the application.
- Error Details: Click Error Details to enter the error details page of the event. The content of the error details page is described below.
# 2.3 View Error Details
The Error Details page displays the error details for the corresponding event.
Error messages are expanded by 'Error Type', and 'Error Number' refers to the number of data strips containing the error type. In order to facilitate issue identification, specific 'cause of error' and sampling examples will be given under each type of error, in which specific information such as the name of the error attribute will be provided for the error type at the attribute level.
Example description:
- In the event ta_test the selected time period, there are 2 error warehousing data, involving two error types - "event attribute name is invalid" and "event attribute type is invalid";
- Of the 2 pieces of data in the wrong storage, 2 have the error of "event attribute name is illegal" and 1 has the error of "event attribute type is illegal";
- Under the error type "event attribute type is invalid", there are two attribute type errors of attributes, namely: "attribute [#zone_offset] type is invalid, legal type: [number]", "attribute [count] type is invalid, legal type: [number]".
In the error message bar, move the mouse to the information prompt icon to the right of the error type to view the legal rule description corresponding to the error type so that you can make further adjustments.
In addition, for the convenience of data viewing, each reported data can be formatted for viewing and copied with one click.
# III. Real-time Data
The real-time data module provides two sub-modules, real-time storing and error data, to view real-time data reports.
# 3.1 Real-time Storing
Real-time storing shows the correct data reported in the last 24 hours. When the data import volume is large, only the last 1000 data contents are displayed. Each line of json data can be formatted to view and copy.
Support for formatted view and copy of each data:
# 3.2 Error Data
The Error Data Module counts and displays the error type of the error reported data every 10 minutes, the number of data entries involved in each type of error, and provides specific error causes/error examples for attribute level errors. The maximum display limit for error data is the latest 1000 error statistics.
# IV. Best Applications
# 4.1 Offline Outdated Data in Reporting Statistics
The receipt of event data can be disabled in the reporting statistics and when the data is disabled, the data will not be stored (nor counted as the amount of data). Since the data reporting on the client side may be affected by the version of the client side, i.e. some users are still using the old version. Reporting offline event data only by version update can not completely prohibit all data reporting and cause waste.. Data reporting can be completely prohibited by prohibiting data reception in the background, which is suitable for offline data no longer collected in some new versions.