CN116846782B - Business anomaly observation method and device for mobile terminal of SAAS CRM system - Google Patents

Abstract

The invention provides a business anomaly observation method and a business anomaly observation device for a mobile terminal of an SAAS CRM system, which belong to the technical field of state monitoring and comprise the following steps: aiming at the real situation of thousands of tenants and thousands of faces faced by the SAAS CRM system, collecting page context information when each user authorized by each tenant of the SAAS CRM system requests to access a page to a mobile terminal of the SAAS CRM system but fails in a certain time; based on the page context information, the SAAS CRM system is observed for business anomalies. The invention designs page context information category covering business attribute information, and utilizes the page context information to conduct abnormal observation of business dimension when a user fails to access a page at a mobile terminal, thereby improving the accuracy of abnormal observation at the mobile terminal of the SAAS CRM system, really focusing on the abnormality affecting the use of the tenant, and providing help for the tenant to eliminate the abnormality rapidly.

Description

Business anomaly observation method and device for mobile terminal of SAAS CRM system

Technical field

The present invention relates to the technical field of status monitoring, and in particular to a method and device for observing business anomalies on the mobile terminal of a SAAS CRM system.

Background technique

CRM (customer relationship management) refers to the use of corresponding information technology and Internet technology by enterprises to coordinate the interaction between enterprises and customers in sales, marketing and services in order to improve their core competitiveness, thereby improving their management methods and providing innovative services to customers. Personalized customer interaction and service process. Deploying a self-used CRM system by an enterprise can not only effectively improve customer relations, but also meet many other needs. However, deployment not only requires a large investment of time, money and human resources, but also requires the establishment of an IT team for operation and maintenance, making the CRM system It has become the exclusive domain of large enterprises, and small and medium-sized enterprises simply cannot afford it. For this reason, the SaaS CRM system came into being. It is built on a large cloud server. Enterprises only need to rent an account and log in through the Internet to use all system functions online.

In order to continue to provide high-quality services to tenants who log in to the SAAS CRM system through mobile terminals, SAAS CRM vendors need to monitor the access pages of tenants accessed through mobile terminals in real time to quickly and intuitively observe abnormalities. However, since the SAAS CRM system is oriented to multi-tenants, in order to adapt to the actual business scenarios of different tenants, on the basis of the ready-to-use standard functions provided by the SAAS CRM vendors, tenants are supported by extending the standard functions and customizing new functions. To meet the actual business needs of tenants, the phenomenon of thousands of tenants with different aspects has formed, making monitoring difficult. Moreover, currently SAAS CRM vendors (such as Tingyun, Borui, etc.) can only monitor tenant access pages, Javascript scripts running in the pages, and requested back-end interfaces from a purely technical level. They focus on the analysis of technical performance and have no business dimension. The analysis capability does not support the observation of anomalies from the abstract level of business entities, nor does it support the differentiation of the impact of anomalies on tenants' experience, resulting in low efficiency in observing business anomalies. In addition, for tenants who log in to the SAAS CRM system through mobile terminals, although SAAS CRM vendors can monitor lags and crashes on the mobile terminal, due to the lack of more detailed information, it is difficult to diagnose the root cause of abnormalities on the mobile terminal.

Therefore, there is an urgent need to provide a business anomaly observation method that can overcome the difficulty of business anomaly observation on the mobile terminal of the SaaS CRM system in a multi-tenant scenario.

Contents of the invention

In order to solve the above problems, the present invention provides a business anomaly observation method and device for the mobile terminal of the SAAS CRM system, designs page context information categories covering business attribute information, and uses the page context information to perform business dimensions when the user fails to access the page on the mobile terminal. The anomaly observation improves the accuracy of anomaly observation on the mobile terminal of the SAAS CRM system, and truly focuses on the anomalies that affect tenant use, helping tenants to quickly eliminate anomalies.

In a first aspect, the present invention provides a method for observing business anomalies on the mobile terminal of a SAAS CRM system. The method includes:

In view of the reality that the SAAS CRM system faces thousands of tenants, collect the page context information of each user authorized by each tenant of the SAAS CRM system within a certain period of time when requesting access to the page from the SAAS CRM system mobile terminal but failing;

Based on the page context information, conduct business abnormality observation on the SAAS CRM system;

The page context information includes business attribute information corresponding to the page access and device information of the mobile device used.

According to the business abnormality observation method of the SAAS CRM system mobile terminal provided by the present invention, the page context of each user authorized by each tenant of the SAAS CRM system within a certain period of time when requesting access to the page from the SAAS CRM system mobile terminal fails. information, including:

Within a certain period of time, monitor the page access requests issued by each user authorized by each tenant of the SAAS CRM system to the mobile terminal of the SAAS CRM system, and write the page context information when the page access request response fails as an exception log. into local;

Control the local area to regularly upload the stored exception logs to the exception reporting terminal of the SAAS CRM system, so that the exception reporting terminal can aggregate and report.

According to the business abnormality observation method for the mobile terminal of the SAAS CRM system provided by the present invention, the generation process of the page context information when the page access request response fails includes:

When the mobile terminal of the SAAS CRM system receives the page access request, initialize the page context information;

Request a business interface from the backend of the SAAS CRM system;

If the request to the business interface fails, the exception details are added to the initialized page context information to generate the page context information when the page access request response fails.

According to the business anomaly observation method for the mobile terminal of the SAAS CRM system provided by the present invention, the initialized page context information includes but is not limited to: the initialized page context information includes but is not limited to: the user ID corresponding to the page access, the tenant ID, occurrence time, business attribute information and device information of the mobile device used;

The device information includes but is not limited to operating system, version, network status and resource usage;

The business attribute information includes but is not limited to: the business module to which it belongs and the business operation type;

The exception details include but are not limited to: error codes, error logs, and error interface address errors.

According to the business abnormality observation method for the mobile terminal of the SAAS CRM system provided by the present invention, before the abnormality reporting terminal summarizes and reports, it also includes:

Encrypt and compress aggregated page context information.

According to the business abnormality observation method of the SAAS CRM system mobile terminal provided by the present invention, the business abnormality observation of the SAAS CRM system based on the page context information includes:

Preprocess the page context information; wherein the preprocessing includes but is not limited to decryption, decompression and data cleaning;

In the preset multi-dimensions, perform indicator quantification statistics, timestamp annotation and time type annotation on the preprocessed page context information to obtain quantitative results;

Store the quantified results to facilitate observers to observe business anomalies;

Wherein, the indicator is the total number of errors.

According to the business abnormality observation method for the mobile terminal of the SAAS CRM system provided by the present invention, the multi-dimensional dimensions include but are not limited to: user ID, tenant ID, occurrence time, terminal device used for access, accessed page, interface requested for page access, The business module to which it belongs, business operation type and error code.

In a second aspect, the present invention provides a business anomaly observation device for the mobile terminal of the SAAS CRM system. The device includes:

The monitoring module is used to collect the reality that the SAAS CRM system faces thousands of tenants and collect every user authorized by each tenant of the SAAS CRM system within a certain period of time who failed to request access to the page from the SAAS CRM system mobile terminal. The page context information at the time;

A business anomaly observation module, configured to observe business anomalies in the SAAS CRM system based on the page context information;

The page context information includes business attribute information corresponding to the page access and device information of the mobile device used.

In a third aspect, the present invention provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the first The business anomaly observation method for the mobile terminal of the SAAS CRM system is described in this aspect.

In a fourth aspect, the present invention provides a non-transitory computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the business anomaly observation method of the mobile terminal of the SAAS CRM system as described in the first aspect is implemented. .

The present invention provides a method and device for observing business anomalies on the mobile terminal of the SAAS CRM system, which includes: in view of the reality of thousands of tenants faced by the SAAS CRM system, collecting data authorized by each tenant of the SAAS CRM system within a certain period of time. The page context information when each user requests to access the page from the SAAS CRM system mobile terminal but fails; based on the page context information, the SAAS CRM system is observed for business anomalies; wherein the page context information covers all page accesses Corresponding business attribute information. The present invention designs page context information categories covering business attribute information, and uses page context information to conduct abnormal observation of business dimensions when users fail to access the page on the mobile terminal, which improves the accuracy of abnormal observation of the mobile terminal of the SAAS CRM system and truly focuses on For exceptions that affect tenant usage, it helps tenants to quickly eliminate exceptions.

Description of drawings

In order to explain the present invention or the technical solutions in the prior art more clearly, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are of the present invention. For some embodiments of the invention, those of ordinary skill in the art can also obtain other drawings based on these drawings without exerting creative efforts.

Figure 1 is a simplified use case diagram of the SAAS CRM system provided by the present invention;

Figure 2 is a schematic flow chart of the business abnormality observation method on the mobile terminal of the SAAS CRM system provided by the present invention;

Figure 3 is an exception reporting timing diagram provided by the present invention;

Figure 4 is a schematic diagram of the execution framework of the business abnormality observation method on the mobile terminal of the SAAS CRM system provided by the present invention;

Figure 5 is a schematic structural diagram of the business abnormality observation device on the mobile terminal of the SAAS CRM system provided by the present invention;

Figure 6 is a schematic structural diagram of the electronic device provided by the present invention;

Reference signs:

610: processor; 620: communication interface; 630: memory; 640: communication bus.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present invention more clear, the technical solutions in the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention. , not all examples. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without making creative efforts fall within the scope of protection of the present invention.

Terminology explanation:

CRM: Customer Relationship Management.

SaaS: Software-as-a-Service, that is, software and services, provided through the Internet.

Business entity: refers to a business object. A business module may contain more than 1 business entity. A business entity contains more than 1 function, such as creating entities, deleting entities, querying entity data, etc.

Tenant: For customers who have purchased SAAS CRM products, all tenant services are provided in the SAAS CRM model.

The following describes a business anomaly observation method and device for the mobile terminal of the SAAS CRM system of the present invention with reference to Figures 1-6.

SaaS CRM products provide many out-of-the-box functions (standard functions) and allow tenants to customize functions according to their own business characteristics. The first type of customization is an extension of the standard functions provided by SaaS CRM; the second type of customization is completely customized and is not within the scope of standard functions. Therefore, the SaaS CRM multi-tenant model will form a phenomenon of thousands of tenants and thousands of faces. Figure 1 is a simplified use case diagram of the SAAS CRM system. As shown in Figure 1, this model will bring three problems to vendor monitoring. (1) When extending functions, even if the original clue function is used, it is different. Depending on the tenant's logic, the monitoring methods will be different. (2) Through customization, functions beyond the standard function range can be infinitely generated, and the monitoring objects also increase; (3) By configuring components, the effect of thousands of tenants and thousands of homepages is achieved, and the difficulty of monitoring increases. Moreover, current monitoring can only be limited to a purely technical level (such as the number of failed calls to a certain interface). As a result, SAAS CRM vendors can only passively analyze abnormalities from a purely technical level, and it is difficult to accurately observe the quality of online operations at the first time. Only when tenants make errors during use can they contact the SAAS CRM vendor and rely on the information provided by the tenants. When conducting anomaly analysis, the inability to restore the accident scene may lead to inefficient analysis and affect tenant experience.

Therefore, in order to continue to provide high-quality SAAS CRM services to tenants who log in to the SAAS CRM system through mobile terminals, it is necessary to quickly and intuitively observe their usage experience to help discover and locate problems.

The present invention believes that abnormal observation of business dimensions is the most intuitive way to understand the usage experience of tenants who log in to the SAAS CRM system through mobile terminals. However, it is obvious that there is currently no solution for business abnormal observation in the SAAS CRM multi-tenant scenario on the market. Its creation has the following features: difficulty:

(1): Unable to obtain tenant usage information in the business dimension;

(2): Lack of observation methods from macro to micro, unable to grasp the key points, and low efficiency; specifically: 2.1): It is impossible to determine whether tenants use standard functions too much or custom functions too much; 2.2): It is impossible to judge from The business level determines which entity functions generate more exceptions; 2.3): It is impossible to determine from the business entity abstract level which type of business operation (query, modification, etc.) generates more exceptions;

(3): Abnormalities that affect tenant experience cannot be gathered, causing too much interference and low efficiency; there are many kinds of anomalies generated by the SAAS CRM system, and the corresponding impacts are also different. Without distinction, it will be difficult to find the anomalies that really need attention. .

(4) When the user’s mobile terminal access freezes or crashes, there is a lack of detailed diagnostic information (such as whether it is a weak network state, the resource usage of the mobile terminal, what business function module is being accessed), and it is difficult to diagnose whether there is a service issue on the mobile terminal. abnormal.

These difficulties prevent SAAS CRM vendors from quickly detecting potential problems on the mobile side from hundreds or thousands of SAAS CRM systems that are dynamically adding functions. They also prevent SAAS CRM vendors from detecting tenant usage abnormalities at the first time, which is not conducive to customers. maintain.

In view of this, the present invention provides a business abnormality observation method for the mobile terminal of the SAAS CRM system, as shown in Figure 1. The method includes:

S11: In view of the reality that the SAAS CRM system faces thousands of tenants, collect the pages when each user authorized by each tenant of the SAAS CRM system within a certain period of time fails to request access to the page from the SAAS CRM system mobile terminal. Context information; the page context information covers the business attribute information corresponding to the page access and the device information of the mobile device used;

The page context information here covers business attribute information and device information of the mobile device used (such as network status, resource status information, etc.). Among them, the network status can be used to determine whether it is a user network problem, and the resource status information can be used to determine whether it is a user network problem. It belongs to user terminal restrictions, and business attributes can be used to quickly locate affected product functions. In addition to business attribute information and device information of the mobile device used, page context information also includes some other information to enrich abnormal site information and thereby improve the efficiency of analysis.

The SAAS CRM system classifies and abstracts functions; classification refers to dividing functions into entity-related or non-entity-related, factory functions or custom functions; abstraction refers to abstracting business objects into entities and entity operations into entities Query, create new entities, edit entities, open entity details, sort entities, delete entities, customize scenarios, etc. In view of this situation and the existing technology, it is to observe the pages visited by users, running JavaScript, and request interface exceptions from the technical level, and does not have the ability to analyze at the business level (for example, an interface may be called by three different business modules, and a single interface may be called by three different business modules. From the interface dimension analysis, it is difficult to determine which business among the three business modules is affected). The present invention sets business attribute information (business module, business entity, business operation type) for each function. When a user accesses a page (which can be regarded as executing a certain function), the business attribute information corresponding to the accessed page is written into the page context information as an identifier. If the user fails to access the page, the corresponding page context information will be used as exception analysis data. , thereby supporting abnormal observation from the business dimension and accurately determining which businesses are affected. In addition, the present invention only collects the page context information when the user fails to access the page as exception analysis data, which can focus on effective exceptions, truly achieve user experience-centered exception observation, and avoid the inefficiency of finding a needle in a haystack from a massive amount of error information.

S12: Based on the page context information, conduct business abnormality observation on the SAAS CRM system;

Existing technology does not have the capability of drill-down and drill-down analysis at the business level. For example, there are more than 400 standard functions shipped from the factory, and the existing technology needs to monitor at least 400 pages, which is inefficient. In addition, tenants dynamically add functions through custom functions, which will cause the number of monitored pages to continue to increase, and ultimately lead to increased monitoring costs. Find problems with low efficiency. On the basis of the page context information, the present invention supports drilling down from macro to micro to find the abnormal business with the greatest impact, thereby improving the efficiency of problem discovery.

The present invention designs page context information categories covering business attribute information, and uses page context information to conduct abnormal observation of business dimensions when users fail to access the page on the mobile terminal, which improves the accuracy of abnormal observation of the mobile terminal of the SAAS CRM system and truly focuses on For exceptions that affect tenant usage, it helps tenants to quickly eliminate exceptions.

Specifically, the S11 includes:

S11.1: Within a certain period of time, monitor the page access requests issued by each user authorized by each tenant of the SAAS CRM system to the mobile terminal of the SAAS CRM system, and provide the page context information when the page access request response fails. Written locally as an exception log;

S11.2: Control the local area to regularly upload the stored exception logs to the exception reporting terminal of the SAAS CRM system, so that the exception reporting terminal can aggregate and report.

The present invention solves the problem of being unable to report when there is no network or weak network by recording the abnormal log into a local file; and achieves the purpose of not affecting the user's normal use of the product through regular asynchronous reporting.

Further, Figure 3 illustrates an exception reporting sequence diagram. As shown in Figure 3, the generation process of page context information when the page access request response fails includes:

When the mobile terminal of the SAAS CRM system receives the page access request, initialize the page context information;

Request a business interface from the backend of the SAAS CRM system;

If the request to the business interface fails, the exception details are added to the initialized page context information to generate the page context information when the page access request response fails.

Preferably, Table 1 defines the specific categories included in the page context information. Except for the ErrorCode and ErrorMessage fields, other information in this table can be obtained during initialization and is stored in a dedicated memory.

Table 1

Therefore, there is: the initialized page context information includes: the user ID, tenant ID, occurrence time, business attribute information and device information of the mobile device used corresponding to the page access;

The device information includes but is not limited to operating system, version, network status and resource usage;

The business attribute information includes but is not limited to: the business module to which it belongs and the business operation type;

The exception details include but are not limited to: error codes, error logs, and error interface address errors.

The error log in the above table refers to the request failure exception prompt information.

When an exception occurs and blocks user operations (such as a pop-up window notifying failure), exception reporting will be triggered. The advantages of this mechanism are:

A: The logic of reporting exceptions is decoupled from the business logic;

The contextual information that needs to be reported is uniformly loaded during page initialization without affecting the original business logic.

B: The reported anomalies are concentrated at the level that affects the user's use.

Some exceptions affect the user's use, and some exceptions do not affect the user's use. If no distinction is made, the analysis will result in a large amount of data and low efficiency. For this reason, only exceptions that block user operations are the most valuable.

Specifically, before the exception reporting end summarizes and reports in S11.2, it also includes:

Encrypt and compress aggregated page context information.

The present invention needs to encrypt and report the page context information to prevent some malicious competitors from disrupting and affecting the tenant's experience.

Specifically, the S12 includes:

S12.1: Preprocess the page context information; wherein the preprocessing includes but is not limited to decryption, decompression and data cleaning;

S12.2: In the preset multi-dimensions, perform indicator quantification statistics, timestamp annotation and time type annotation on the preprocessed page context information to obtain quantitative results;

S12.3 Store the quantified results to facilitate observers to observe business anomalies;

Wherein, the indicator is the total number of errors.

Table 2 illustrates the business anomaly indicator model, as follows:

Table 2

Therefore: the multiple dimensions include but are not limited to: user ID, tenant ID, mobile operating system, mobile version, interface requested by the user, business module to which it belongs, business operation type and error code.

In fact, the present invention quantifies and stores the page context information at the finest granularity (multiple dimensions), and discovers the scope of the abnormal impact, such as which tenants, which users, what equipment, what time period, and factory delivery. Function or custom function, data query or data modification scenario.

The present invention can also add an abnormality analysis service on the basis of S12.2, and do some coarse-grained statistics and analysis based on the fine-grained quantitative results.

Figure 4 illustrates a schematic diagram of the execution framework of the business anomaly observation method for the SAAS CRM system. As shown in Figure 4, the present invention enables observers to Observe business anomalies to discover which tenants and which business anomalies have the highest number, identify the stumbling blocks that most affect tenant experience, promote optimization, and solve tenant experience problems.

In the second aspect, the invention provides a description of the business anomaly observation device on the mobile terminal of the SAAS CRM system. The business anomaly observation on the mobile terminal of the SAAS CRM system described below and the business abnormality observation method on the mobile terminal of the SAAS CRM system described above can correspond to each other. Figure 5 illustrates the structural diagram of business anomaly observation on the mobile terminal of the SAAS CRM system. As shown in Figure 5, the device includes:

The monitoring module 21 is used to collect the results of each user authorized by each tenant of the SAAS CRM system within a certain period of time to request access to the page from the SAAS CRM system mobile terminal in response to the reality that the SAAS CRM system faces thousands of tenants. Page context information on failure;

The business anomaly observation module 22 is used to observe business anomalies in the SAAS CRM system based on the page context information;

The page context information includes business attribute information corresponding to the page access and device information of the mobile device used.

The business abnormality observation device for the mobile terminal of the SAAS CRM system provided by the present invention designs page context information categories covering business attribute information, and uses the page context information to observe abnormality in the business dimension when the user fails to access the page on the mobile terminal, thereby improving SAAS CRM. The accuracy of abnormality observation on the mobile side of the system and its real focus on the anomalies that affect tenant usage can help tenants to quickly eliminate anomalies.

Based on the above embodiments, as an optional embodiment, the collection module includes:

A monitoring unit configured to monitor page access requests issued by each user authorized by each tenant of the SAAS CRM system to the mobile terminal of the SAAS CRM system within a certain period of time, and to provide the page context when the page access request response fails. The information is written locally as an exception log;

The reporting unit is used to control the local to regularly upload the stored exception logs to the exception reporting end of the SAAS CRM system, so that the exception reporting end can aggregate and report.

Based on the above embodiments, as an optional embodiment, the generation process of page context information when the page access request response fails includes:

When the mobile terminal of the SAAS CRM system receives the page access request, initialize the page context information;

Request a business interface from the backend of the SAAS CRM system;

If the request to the business interface fails, the exception details are added to the initialized page context information to generate the page context information when the page access request response fails.

Based on the above embodiments, as an optional embodiment, the initialized page context information includes but is not limited to: user ID, tenant ID, occurrence time, business attribute information and usage corresponding to the page access. The device information of the mobile device;

The device information includes but is not limited to operating system, version, network status and resource usage;

The business attribute information includes but is not limited to: the business module to which it belongs and the business operation type;

The exception details include but are not limited to: error codes, error logs, and error interface address errors.

Based on the above embodiments, as an optional embodiment, before the exception reporting terminal summarizes and reports, it also includes:

Encrypt and compress aggregated page context information.

Based on the above embodiments, as an optional embodiment, the business anomaly observation module includes:

A preprocessing unit, configured to preprocess the page context information; wherein the preprocessing includes but is not limited to decryption, decompression, and data cleaning;

The quantification unit is used to perform indicator quantification statistics, timestamp annotation and time type annotation on the preprocessed page context information in preset multi-dimensions to obtain quantitative results;

A storage unit used to store the quantified results to facilitate observers to conduct business abnormality observations;

Wherein, the indicator is the total number of errors.

Based on the above embodiments, as an optional embodiment, the multi-dimensions include but are not limited to: user ID, tenant ID, occurrence time, terminal device used for access, accessed page, page access request interface, business module to which it belongs, business operation type and error code.

In the third aspect, Figure 6 illustrates a schematic diagram of the physical structure of an electronic device. As shown in Figure 6, the electronic device may include: a processor (processor) 610, a communications interface (Communications Interface) 620, a memory (memory) 630 and Communication bus 640, in which the processor 610, the communication interface 620, and the memory 630 complete communication with each other through the communication bus 640. The processor 610 can call the logical instructions in the memory 630 to execute a business anomaly observation method on the mobile terminal of the SAAS CRM system. The method includes: in view of the reality of thousands of tenants faced by the SAAS CRM system, collect the above mentioned data within a certain period of time. Page context information when each user authorized by each tenant of the SAAS CRM system requests access to the page from the mobile terminal of the SAAS CRM system but fails; based on the page context information, conduct business abnormality observation on the SAAS CRM system; wherein, the The page context information includes the business attribute information corresponding to the page access and the device information of the mobile device used.

In addition, the above-mentioned logical instructions in the memory 630 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present invention essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .

In a fourth aspect, the present invention also provides a computer program product. The computer program product includes a computer program. The computer program can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can Execute the business anomaly observation method on the mobile terminal of the SAAS CRM system provided by the above methods. The method includes: in view of the reality of thousands of tenants faced by the SAAS CRM system, collect the authorization of each tenant of the SAAS CRM system within a certain period of time. Page context information when each user of the SAAS CRM system fails to request page access from the mobile terminal of the SAAS CRM system; based on the page context information, business abnormality observation is performed on the SAAS CRM system; wherein, the page context information covers page access The corresponding service attribute information and the device information of the mobile device used.

In a fifth aspect, the present invention also provides a non-transitory computer-readable storage medium on which a computer program is stored. The computer program is implemented when executed by the processor to perform business abnormality observation on the mobile terminal of the SAAS CRM system provided by the above methods. Method, the method includes: in view of the reality that the SAAS CRM system faces thousands of tenants, collect the results of each user authorized by each tenant of the SAAS CRM system within a certain period of time to request access to the page from the SAAS CRM system mobile terminal. The page context information at the time of failure; based on the page context information, conduct business abnormality observation on the SAAS CRM system; wherein the page context information covers the business attribute information corresponding to the page access and the mobile device used Device Information.

The device embodiments described above are only illustrative. The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they may be located in One location, or it can be distributed across multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. Persons of ordinary skill in the art can understand and implement the method without any creative effort.

Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the part of the above technical solution that essentially contributes to the existing technology can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disc, optical disk, etc., including a number of instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that it can still be used Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent substitutions are made to some of the technical features; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (8)

1. A business abnormality observation method for the mobile terminal of the SAAS CRM system, characterized in that the method includes: In view of the reality that the SAAS CRM system faces thousands of tenants, collect the page context information of each user authorized by each tenant of the SAAS CRM system within a certain period of time when requesting access to the page from the SAAS CRM system mobile terminal but failing. ; Based on the page context information, conduct business abnormality observation on the SAAS CRM system; Among them, the collection of page context information when each user authorized by each tenant of the SAAS CRM system within a certain period of time fails to request access to the page from the SAAS CRM system mobile terminal includes: Within a certain period of time, monitor the page access requests issued by each user authorized by each tenant of the SAAS CRM system to the mobile terminal of the SAAS CRM system, and use the page context information when the page access request response fails as an exception log Write to local; Control the local area to regularly upload the stored exception logs to the exception reporting terminal of the SAAS CRM system, so that the exception reporting terminal can aggregate and report; The generation process of page context information when the page access request response fails includes: When the mobile terminal of the SAAS CRM system receives the page access request, initialize the page context information; Request a business interface from the backend of the SAAS CRM system; If the request to the business interface fails, the exception details are added to the initialized page context information to generate the page context information when the page access request response fails; The initialized page context information includes: business attribute information corresponding to page access and device information of the mobile device used; The business attribute information includes but is not limited to: the business module to which it belongs and the business operation type; The exception details include but are not limited to: error codes, error logs, and error interface address errors. 2. The business abnormality observation method for the mobile terminal of the SAAS CRM system according to claim 1, characterized in that the initialized page context information also includes: the user ID, tenant ID and occurrence time corresponding to the page access. The device information includes but is not limited to operating system, version, network status and resource usage. 3. The business abnormality observation method of the SAAS CRM system mobile terminal according to claim 1, characterized in that before the abnormality reporting terminal summarizes and reports, it also includes: Encrypt and compress aggregated page context information. 4. The business abnormality observation method of the mobile terminal of the SAAS CRM system according to claim 3, characterized in that, based on the page context information, the business abnormality observation of the SAAS CRM system includes: Preprocess the page context information; wherein the preprocessing includes but is not limited to decryption, decompression and data cleaning; In the preset multi-dimensions, perform indicator quantification statistics, timestamp annotation and time type annotation on the preprocessed page context information to obtain quantitative results; Store the quantified results to facilitate observers to observe business anomalies; Wherein, the indicator is the total number of errors. 5. The business abnormality observation method for the mobile terminal of the SAAS CRM system according to claim 4, characterized in that the multi-dimensional dimensions include but are not limited to: user ID, tenant ID, mobile terminal operating system, mobile terminal version, user requested Interface, associated business module, business operation type and error code. 6. A business abnormality observation device for the mobile terminal of the SAAS CRM system, characterized in that the device includes: The monitoring module is used to collect the reality that the SAAS CRM system faces thousands of tenants and collect every user authorized by each tenant of the SAAS CRM system within a certain period of time who failed to request access to the page from the SAAS CRM system mobile terminal. The page context information at the time; A business anomaly observation module, configured to observe business anomalies in the SAAS CRM system based on the page context information; Among them, the collection of page context information when each user authorized by each tenant of the SAAS CRM system within a certain period of time fails to request access to the page from the SAAS CRM system mobile terminal includes: Within a certain period of time, monitor the page access requests issued by each user authorized by each tenant of the SAAS CRM system to the mobile terminal of the SAAS CRM system, and use the page context information when the page access request response fails as an exception log Write to local; Control the local area to regularly upload the stored exception logs to the exception reporting terminal of the SAAS CRM system, so that the exception reporting terminal can aggregate and report; The generation process of page context information when the page access request response fails includes: When the mobile terminal of the SAAS CRM system receives the page access request, initialize the page context information; Request a business interface from the backend of the SAAS CRM system; If the request to the business interface fails, the exception details are added to the initialized page context information to generate the page context information when the page access request response fails; The initialized page context information includes: business attribute information corresponding to page access and device information of the mobile device used; The business attribute information includes but is not limited to: the business module to which it belongs and the business operation type; The exception details include but are not limited to: error codes, error logs, and error interface address errors. 7. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that when the processor executes the program, it implements claim 1 The business anomaly observation method for the mobile terminal of the SAAS CRM system described in any one of 5 to 5. 8. A non-transitory computer-readable storage medium with a computer program stored thereon, characterized in that when the computer program is executed by a processor, the SAAS CRM system mobile terminal as described in any one of claims 1 to 5 is implemented. Business anomaly observation methods.