I. Overview
1.Feature Introduction
Cloud operation maintenance relies on the treasures data package. The specific CSV table structure of this data package will be described in detail below.
II. Get Treasure Data Package
Enter the Decision-making Platform and select "Management > Intelligent Operations > Cloud Operation and Maintenance", and click "Download Log" to download the data package.
III. Data Package Structure
1. Monthly data package
After unzip, you can see several days data package and one month data package information.
2. Daily data package
After unzip the daily data package have 11 CSV tables.
3. Export Log
The server log will be saved in the treasures.zip data package in the form of a compressed package. There are two kinds of files in the data package：
1) The log file of the selected month (treasxxxxxx.zip)
2) Monthly data package file (package.json)
The information in the package.json file is the application name, application ID, the month that the data package belongs to, and the number of daily data packages contained in the month's data package.
The content of the json file in the treasure compressed package for multi-months：
The content of the json file in the treasure compressed package for single months：
IV. Table and Field Introduction
1. package
Packet information table：basic information of the application, each data packet contains this, used to identify the source of the data packet.
| Field | Explanation |
|---|---|
| appname | Application Name |
| appid | Application ID |
| time | package time，for example：2018-11-01 （In the case of automatic export: the package of the previous day is exported at 4:00 am every day, and it is recorded as the day before the export date） |
| version | Cloud Operation and Maintenance version |
2. execute
Template usage table： record the execution details of the template.
| Field | Explanation |
|---|---|
| id | Primary key |
| tname | Template name ( the full path of reportlet folder) |
| displayName | The name of the directory mounted to the platform (full path) |
| time | Record time |
| memory | Project memory |
| type | Template access type |
| consume | The background time-consuming |
| sqlTime | SQL run time-consuming |
| userId | User ID |
| complete | calculate finished or not |
| source | weblink access/platform access |
| reportId | Template ID |
| brower | Browser |
| sessionID | Session ID |
3. executeSql
SQL execution table： record the execution details of SQL.
| Field | Explanation |
|---|---|
| executeid | Excute ID |
| dsname | Dataset name |
| sqltime | SQL run time-consuming，unit is milliseconds |
| rows | Size of dataset，row |
| columns | Size of dataset，column |
| time | Run time-consuming，format is timestamp |
| connection | Database connection name |
| connectionID | Database connection tag ID |
4. realTime
Application real-time status table：The real-time status of the application is recorded every minute.
| Field | Explanation |
|---|---|
| node | Node name |
| time | Record time，One per minute |
| memory | Memory status of current JVM |
| cpu | CPU usage |
| sessionnum | Live session number |
| onlinenum | System online number of people |
| pid | Progress ID |
| templateRequest | The request number of calculating template |
| httpRequest | Total number of HTTP requests being processed |
| sessionRequest | Number of SessionID requests being processed |
5. consumePoint
Performance burying point collection table：The performance of the template is recorded once a day.
| Field | Explanation |
|---|---|
| id | Buried point ID |
| source | 1 --- the current system 0 --- the embedded point of the plugin -1--- no source is defined |
| time | Start Time |
| username | Username ID |
| finish | End Time |
| consume | Time-consuming， unit (ms) |
| memory | Memory size，unit （byte） |
| title | Template name ( the full path of reportlet folder) |
| text | sessionID |
| type | Operate type |
| comment | More specific information |
| body | json data structure, storing different information according to different buried points |
6. focusPoint
Feature usage table：record the usage of function points and various buried point information
| Field | Explanation | Example |
|---|---|---|
| id | Buried point ID | For example：FR-F4001 |
| source | Buried point source | embed --- the current system plugin --- the embedded point of the plugin undefined --- no source is defined |
| time | time | Time to use this function |
| username | username | Username ID |
| title | title | Major Information |
| text | content | Features major information |
| body | Buried point specific information | json data structure, storing different information according to different buried points |
7. errorRecord
Error log record table： record the error log that occurred in the system.
| Field | Explanation |
|---|---|
| tname | Error template name（the full path of reportlet folder） |
| time | Error record time |
| displayName | The name of the directory mounted to the platform (full path) |
| platformDisplay | Whether to display in the platform（1--yes，0--no） The recording rule is: there is an error log recorded to this table, this field is recorded as 1, otherwise this field is recorded as 0 |
| username | User ID |
| msg | Error information |
| errorcode | Error code |
| trace | Error path |
8. gcRecord
GC log record table： record the GC information of the system.
| Field | Data Type & Unit | Explanation |
|---|---|---|
| gcStartTime | long timestamp | GC start time |
| gcType | String | GC type |
| gcCause | String | GC cause |
| pid | String | progress pid |
| node | String | The node name named by the user, the stand-alone environment record is empty |
| duration | long ms | GC time of duration |
| youngBeforeUsed | long KB | Used memory before young generation GC |
| youngBeforeCommitted | long KB | Committed memory before young generation GC |
| youngAfterUsed | long KB | Used memory after young generation GC |
| youngAfterCommitted | long KB | Committed memory after young generation GC |
| oldBeforeUsed | long KB | Used memory before GC in the old age |
| oldBeforeCommitted | long KB | Committed memory before GC in the old age |
| oldAfterUsed | long KB | Used memory after GC in the old age |
| oldAfterCommitted | long KB | Committed memory after GC in the old age |
| metaspaceBeforeUsed | long KB | Used memory before metaspace GC |
| metaspaceBeforeCommitted | long KB | Committed memory before metaspace GC |
| metaspaceAfterUsed | long KB | Used memory after metaspace GC |
| metaspaceAfterCommitted | long KB | Committed memory after metaspace GC |
| heapBeforeUsed | long KB | Heap memory usage before GC |
| heapBeforeCommitted | long KB | Committed memory for heap before GC |
| heapAfterUsed | long KB | Heap memory usage after GC |
| heapAfterCommitted | long KB | Committed memory for heap after GC |
| balancePromoterScore | int | Abort calculation score |
| releasePromoterScore | int | Free session score |
| loadScore | int | Overall load score |
9. processLog
Record logs related to cloud operation and maintenance tasks.
| Field | Explanation |
|---|---|
| time | Time |
| node | Node |
| process | Process |
10. recordOperate
Management log table： When the user operates the module, a record will be added to the table and the corresponding information record will be filled in the corresponding field.
| Field | Explanation |
|---|---|
| type | Record Type |
| item | Setting Item |
| operate | Operate Type |
| username | Username |
| ip | IP |
| time | User Operate Time |
11. recordWrite
Date Entry the log record table： record the execution details of the date entry operation.
| Field | Explanation |
|---|---|
| username | Data entry username |
| tname | Template name |
| time | Data entry time |
| result | filling successful or not |
| ip | Data entry IP address |
| displayName | The directory path where the template is mounted on the platform |
| browser | Browser version |
| consume | Time spent of data entry |
Previous：Time Zone Exception Prompt During Task Schedule
