Successfully!

Error!

Cloud Operation Maintenance Dashboard

  • Last update:  2022-09-09
  • I. Overview

    1. Version

    Report Server Version
    JAR VersionSupport Function
    10.0--template performance risk analysis
    10.02019-06-13downtime analysis
    10.02019-09-27system test


    2. Scenarios

    • Users can understand the overall system usage based on the cloud operation maintenance dashboard.

    • Users can understand the system performance status based on the highest data of the day of memory and the highest data of the day of CPU in the cloud operation maintenance dashboard.

    • Users can troubleshoot the cause of the downtime based on the downtime analysis in the cloud operation maintenance dashboard.

    • Users can quickly understand report system data based on cloud operation maintenance indicators.

    • Users can view the number of system freezes and memory load based on memory load analysis.

    • In the IT department, the person in charge of the FineReport system needs to understand the usage of the system and templates through a series of data when promoting the system, updating new templates, and optimizing old templates.

    3. Feature Introduction

    Cloud Operation Maintenance means that FanRuan provides customers with a cloud center analysis and calculation engine. Customers only need to provide the log files of the report system operation to the cloud center calculation engine to obtain operation and maintenance analysis results reports, find operation and maintenance problems, and obtain solution.

    The cloud operation maintenance analysis dashboard includes four tabs:Overview, Report Project Analysis, Function Recommendation and System Operation Analysis,as shown follow:

    Note:For details of the cloud operation maintenance analysis dashboard, please refer to: Cloud Operation Maintenance Log Package Table Structure Description.

    Note 2: If Finereport integrated into FineBi, a BI engineering analysis tab page will be added to the cloud operation and maintenance report. Please refer to: Bi engineering analysis for details of the "Bi engineering analysis" tab page.

    II. Advantages of Cloud

    1) Advantages of Cloud

    • High Volume Computation - With added accuracy and comprehensiveness, smarter operation advice based on big data analysis, comparison and fitting can be given. This is achieved via sophisticated calculation over a high volume of models.

    • Zero Cost - No consumption of local computation resources. The computing part is done by FanRuan at its cloud hub.

    • Easy to Start - There's no need to put resources into maintaining this operation tool because it is deployed on the cloud and maintained by FanRuan engineers.

    • High Growth - A growing and continuously updated operation platform. The functional update is fully autonomous without adding any workload for users.

    2) Data Security

    • Data Safety - The feature only analyzes application operational data required to improve the experience. No business data will be accessed.

    • Data Transparency - Users are free to view the uploaded data at any time.

    • Confidentiality Agreement - It can be signed when needed (e-signature options available)

    III.Overview

    Data such as access status, memory peak, and CPU ratio peak in the「Overview」 tab can reflect whether the system can be used normally.

    1. System Overview

    1)The overall situation of the system displays information on the Total Visits, Total Visitors, and Downtime, highlights the current month's data, and displays the historical data of the past three months, which is convenient for users to directly compare, observe the fluctuations of the three indicators, and expose problems early. As shown below:

    2)Click the links under 「Total Visits」and 「Total Visitors」 to view detailed data of each template. According to two measurement methods, the popularity of templates is visually displayed, and there is no limit to the number. All template conditions can be seen in this link, supplemented with the previous month's data for comparison. As shown below:



    2. Downtime Analysis

    Analyze downtime, problem templates, data volume, elapse time, problem datasets, possible problems, etc., so that users can find out the reasons for downtime problems. As shown below:


    3. Execution data

    The user can judge whether the memory is overflowing and the risk of stable operation when the system pressure is maximum through the memory trend and CPU trend.

    As shown below:

    Click 「Click to view more」botton,you can view operation and maintenance indicators to obtain basic information about the system.

    As shown below:


    4. Access Status

    You can use the cloud operation maintenance dashboard to check how many users have accessed the reporting system, the frequency of access, and the number of templates visited everyday. As shown below:

    Click 「Click to view more」botton,you can view business indicators.

    As shown below:


    5. Memory Load Analysis

    Including the number of stalls this month and the memory load score, and the number of stalls is linked with the memory load score, which can dynamically display the memory load. As shown below:


    IV. Report Project Analysis

    1. Template execution status

    Give the reasons for the template problems, count the proportions of various reasons, and compare the monthly stability fluctuations of the system horizontally. As shown below:


    2. Templates need optimization

    Based on the system usage, list the templates that have performance problems, so that customers can find the templates that affect business use in their own systems.

    As shown below:

    Click 「Click to view more」botton,you can search and view the running status of the template by time and template name. As shown below:

    Click template hyperlink, you can view the loading status of a single template. As shown below:


    3. Top 10 templates with highest execution time

    The cloud operation maintenance analysis dashboard lists the top 10 templates with highest execution time, which is convenient for users to find and find problems.

    As shown below:

    Click template hyperlink, you can view the loading status of a single template.

    As shown below:


    V. Function Recommendation

    Recommend a function in the cloud operation and maintenance report function every month to help users solve product use problems and improve product use quality. As shown in the figure below:

    Note: the functions already recommended will not be recommended.

    4MMBRWGT17I34RE%9G}P (1).png

    Requirements for the appearance of this tab page:

    The month of uploading the data package is the previous month of the current month, and the "function recommendation" tab page will appear for the data package with the data package version of 3.0 and above.

    For example, log data is uploaded in August 2020 (the current month), and the data package version is 3.0 or above. The cloud operation and maintenance report in July 2020 has a "function recommendation" tab page. The data package version can be displayed in the log data package JSON file, as shown in the following figure:

    1598857061421054 (1).png

    VI. System Operation Analysis

    Accessing data through users and templates can more accurately measure the use of the system and its changes, such as the distribution of user access days, template access days, etc. to help IT department system leaders perceive system operations.


    1. Access analysis of visitors

    Use a column chart and an area chart to show the distribution of the number of users and the distribution of user ratios respectively. As shown below:

    Calculation rules:

    1) Number of users:

    The meaning is explained as follows:

    Note: users > 25 days are basically accessing the system every day.

    • Number of users in the current month for 1-5 days: one user visited the system for 1-5 days in the current month (possibly for 3 days).

    • Number of users in the current month for 21-25 days: one user visited the system for 21-25 days (possibly 22 days) in the previous month, which is a regular user.

    2) User ratio:

    The proportion of users in the corresponding dimension in all users who have visited the system.

    As shown in the figure below, it can be seen that the proportion of users who have visited the system for 1-5 days this month is 25%, and the number of users who use the system less is increasing (from 14.88% to 25%), but it is much less than the average number of all cloud customers (50.28%).

    1638843275rF8W.png


    2. Access analysis of templates

    Display template access data.  As shown below:

    Calculation rules:

    1) Number of templates:

    It can be seen from the figure that half of the templates will be accessed only 1-5 days a month. Click classification to drill down to view the templates corresponding to the number of days visited in the current month. It is recommended that users reconsider the value of these templates to avoid unnecessary human maintenance costs.

    The meaning is explained as follows:

    Note: templates > 25 days are accessed almost every day.

    • Number of templates in the current month for 1-5 days: 75 templates have been accessed for 1-5 days this month (maybe 3 days).

    • Number of templates in the current month of 16-20 days: three templates have been accessed 16-20 days this month (maybe 19 days), which are frequently accessed templates.

    2) Template ratio:

    Proportion of templates of corresponding dimensions in all templates.

    As shown in the figure below, it can be seen that the number of templates accessed for 1-5 days this month accounts for 63.56% of all the templates accessed this month.

    1600163041470538 (1).png

    3. Top 10 templates for increasing/decreasing access numbers

    Show the top ten templates for the increase/decrease in the number of visitors in the current month. As shown below:

    Attachment List


    Theme: Decision-making Platform
    Already the First
    Already the Last
    • Helpful
    • Not helpful
    • Only read

    Doc Feedback