WO2019000895A1 - 一种Flash播放器异常日志管理方法及系统 - Google Patents

一种Flash播放器异常日志管理方法及系统 Download PDF

Info

Publication number
WO2019000895A1
WO2019000895A1 PCT/CN2017/120170 CN2017120170W WO2019000895A1 WO 2019000895 A1 WO2019000895 A1 WO 2019000895A1 CN 2017120170 W CN2017120170 W CN 2017120170W WO 2019000895 A1 WO2019000895 A1 WO 2019000895A1
Authority
WO
WIPO (PCT)
Prior art keywords
abnormal
flash player
data
abnormal data
node
Prior art date
Application number
PCT/CN2017/120170
Other languages
English (en)
French (fr)
Inventor
潘龙
张文明
陈少杰
Original Assignee
武汉斗鱼网络科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 武汉斗鱼网络科技有限公司 filed Critical 武汉斗鱼网络科技有限公司
Publication of WO2019000895A1 publication Critical patent/WO2019000895A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/18File system types
    • G06F16/1805Append-only file systems, e.g. using logs or journals to store data
    • G06F16/1815Journaling file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/955Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566URL specific, e.g. using aliases, detecting broken or misspelled links
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11BINFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/10Digital recording or reproducing
    • G11B20/10527Audio or video recording; Data buffering arrangements

Definitions

  • the present invention relates to the field of log management technologies, and in particular, to a method and system for managing an abnormality log of a Flash player.
  • the Falsh player is a client. Unlike other servers, the database can be built to store some abnormal data and export the exception data as needed. The Flash player may encounter some exceptions during the process of being used by the user, so that the user cannot use the Flash player normally.
  • Some users may go to the corresponding technical support staff to solve these problems, so that they can experience the product normally, and some users may be lost.
  • the technical support personnel receives the user's abnormal feedback, it may be due to timeliness or some other reasons, such as the user does not keep the abnormal scene. In this case, the technical support personnel have no data support, and cannot pass the scene according to the abnormal data. Analyze abnormal conditions.
  • the technical support personnel can only simulate the scene multiple times to reproduce the abnormal scene or directly wait for the next time the user uses the Flash player to reproduce the abnormal scene.
  • the passive tracking of abnormalities by technical support personnel is relatively inefficient, and at the same time, the labor cost is greatly increased and the problem cannot be directly solved.
  • the present invention provides a Flash player abnormal log management method and system that overcomes the above problems or at least partially solves the above problems, and can overcome the problem of abnormal positioning during the execution of the Flash player.
  • a Flash player exception log management method including:
  • the abnormal data is exported from the abnormal data manager and displayed according to a preset style.
  • the beneficial effects of the present invention are: constructing a set of abnormal data collection and storage mechanism in the Flash player, and automatically collecting the abnormal data generated during the execution of the Flash player by configuring the abnormal node in the Flash player, and storing the abnormal data.
  • the abnormal data is exported, so that the technical support personnel can reproduce the scene according to the abnormal data, which is convenient for abnormal positioning.
  • the present invention can also be improved as follows.
  • the abnormal node is an input and output abnormal node and a read abnormal node
  • the step S1 further includes:
  • an input and output exception node and multiple read exception nodes are configured at the corresponding critical logical positions.
  • configuring the one input and output abnormal node in the corresponding key logical position further includes:
  • the Flash player loads the resource by calling the resource loading method in the loading resource class, and configures the input and output abnormal node in the resource loading method to capture the input and output exception when the resource is loaded.
  • the configuring the plurality of read abnormal nodes in the corresponding key logical locations further includes:
  • the abnormal node corresponding to the service scenario is configured in the code block corresponding to the different service scenarios to capture the data read exception in the service scenario.
  • step S1 further includes:
  • Each of the abnormal nodes is configured with a unique identifier.
  • each of the abnormal data includes an abnormality occurrence time, an abnormal node unique identifier, and an abnormal data content.
  • step S2 the abnormal data manager is configured in the Flash player by:
  • the exception data manager is configured in the Flash player by writing an exception data management class in the Flash player and instantiating the exception data management class.
  • the abnormal data is displayed according to a preset style:
  • a plurality of abnormal data are displayed by adding a line break between each adjacent two abnormal data.
  • step S2 further includes:
  • the abnormal data in the abnormal data list is written into the buffer one by one to cache the abnormal data.
  • a Flash player abnormal log management system including:
  • a configuration module configured to configure an abnormal node at a different critical logical position during execution logic of the Falsh player
  • a storage module configured to generate corresponding abnormal data when the abnormal node is triggered, and store each abnormal data in the abnormal data manager, where the abnormal data manager is located in the Flash player;
  • a display module for exporting anomalous data from the anomaly data manager and displaying it according to a preset style.
  • a non-transitory computer readable storage medium storing computer instructions that cause the computer to perform the various implementation methods described above.
  • FIG. 1 is a flowchart of a method for managing an abnormality log of a Flash player according to an embodiment of the present invention
  • FIG. 2 is a block diagram showing an overall connection of a Flash player abnormal log management system according to still another embodiment of the present invention.
  • FIG. 3 is a block diagram of an electronic device connection according to an embodiment of the present invention.
  • a method for managing an abnormality log of a Flash player which can automatically collect and store abnormal data during execution of a Flash player, so that technical support personnel can perform analysis and positioning according to abnormal data.
  • the method includes: S1, configuring an abnormal node at a different key logical position during execution logic of the Falsh player; S2, when the abnormal node is triggered, generating corresponding abnormal data, and storing each abnormal data in In the abnormal data manager, wherein the abnormal data manager is located in the Flash player; S3, the abnormal data is exported from the abnormal data manager, and is displayed according to a preset style.
  • an exception node is added at the critical logical position.
  • the abnormal node is triggered, that is, when the Flash player is abnormal, an abnormal data is generated correspondingly.
  • the exception data manager stores the exception data generated at each exception node in the exception data manager.
  • the abnormal data can be exported from the abnormal data manager and displayed according to a certain pattern, so that the technical support personnel can view the abnormal data and perform analysis and positioning.
  • the abnormal node is an input and output abnormal node and a read abnormal node
  • the step S1 further includes: in the execution logic process of the Flash player, The corresponding critical logical location configures an input and output exception node and multiple read exception nodes.
  • the abnormal nodes in this embodiment are mainly input and output abnormal nodes and read abnormal nodes. In this embodiment, only one input and output abnormal node need to be configured, and a plurality of abnormal nodes need to be configured.
  • the configuring an input and output abnormal node in the corresponding key logical position further comprises: based on the Flash player calling the resource loading method in the loading resource class. Load resources, configure input and output exception nodes in the resource loading method to capture the input and output exceptions when loading resources.
  • Input and output exceptions ioError is caused when some objects' input or output operations fail. This kind of exception usually occurs in the Flash player when loading server resources. For example, the resources that need to be loaded do not exist. Because the Flash player loads the resources according to the specific module, in order to facilitate the management status, the Flash player takes the resource loading class assetsManager to load the resources. In the resource loading class assetsManager, a resource loading method loadAsstes is provided to load the resources. The only loading resource entry for the Flash player. Since there is only one loading resource entry when the Flash player loads the resource, the embodiment only needs to place an input and output abnormal node at the entry of the loading resource, that is, the input and output abnormal node is configured in the resource loading method. , it can capture the input and output exceptions when the Flash player loads resources.
  • the IoErrorHandler method is the operation function when the input and output exception occurs.
  • the configuring the plurality of reading abnormal nodes in the corresponding key logical positions further includes: in the code blocks corresponding to different business scenarios, according to different service scenarios Configure an abnormal node corresponding to the service scenario to capture data read exceptions in the service scenario.
  • EOFError is an exception caused by the extent of the data being exceeded when reading certain data.
  • a common scenario is when the client communicates with the server, the client reads the length of the binary data sent by the server over the length of the data sent by the server. Since there are many business scenarios in the process of executing the Flash player, data reading is performed in different business scenarios. Therefore, for each business scenario, an abnormal node needs to be read to capture the business scenario. The data in the reading is abnormal.
  • the abnormal reading node corresponding to the service scenario is configured in the code block corresponding to each service scenario to capture the data reading abnormality in the service scenario.
  • the read exception EOFError is too fragmented, which is not convenient for management. It is only possible to manually add an abnormal node on a critical logical node.
  • the Try function is a comparison operation of two objects, or parsing data operations; the catch function captures the error response inside the Try function, and finally the finally function performs exception handling. In this way, through the function Try..catch..finally, you can create an exception node in the execution logic where an exception is easy to occur or where the exception needs to be checked.
  • the step S1 further includes: configuring a unique identifier for each abnormal node, and correspondingly, each of the abnormal data includes an abnormality occurrence time and an abnormal node. Unique identifier and exception data content.
  • each abnormal node is configured with a unique identifier.
  • the unique identifier of the abnormal node can know the type of each abnormal node. That is, the abnormal node is an input/output abnormal node or an abnormal node, and an abnormal node corresponding to which business scenario.
  • Each of the abnormal data includes an abnormality occurrence time, an abnormal node unique identifier, and an abnormal data content.
  • the input and output exception ioError will execute the IoErrorHandler method
  • the read exception EOFError will execute the finally logic block
  • the exception data errdata object will be generated in the IoErrorHandler method and the finally logic block.
  • the structure of the errdata object is:
  • Errtime is the exception generation time, here is the system time, it is obtained by the system function gettime(); errType is the exception type, the error from the ioError is set to 1, the error from the EOFError is set to 2; the handleData is the abnormal data content. , from the event description when the exception is thrown.
  • the load link URL (Uniform Resource Locator) can be used to assign the url to the handleData as the exception data, and the EOFError description attribute text is obtained and assigned in the finally logic block. Give handleData as exception data.
  • an abnormal data manager in order to facilitate management of abnormal data, is configured in the Flash player, and an abnormal data list is constructed in the abnormal data manager, each of which is The abnormal data is stored in the exception data list in the order in which the abnormal data occurs.
  • an abnormal data corresponding to the abnormal node is generated.
  • the abnormal data includes the time when the abnormality occurs, the local system time when the abnormality occurs is the abnormal occurrence time, the unique identifier of the abnormal node where the abnormality occurs, and the specific abnormal data content, that is, a single abnormality is recorded in each abnormal data. Time, what type of exception the exception belongs to, and specific exception data. Among them, according to the unique identifier of the abnormal node where the abnormality occurs, it can be determined which type the abnormality belongs to.
  • an abnormal data list is constructed in the exception data manager in the Flash player, and the abnormal data generated at each abnormal node is stored in the abnormal data list in the time sequence in which the abnormal data occurs, in preparation for subsequent Supported as data.
  • the exception data manager is configured in the Flash player by writing an exception data management class in the Flash player and instantiating the exception data management class.
  • the step S2 further includes: writing the abnormal data in the abnormal data list one by one to the buffer area according to the preset time interval, to cache the abnormal data. .
  • the abnormal data in the abnormal data list is written into the buffer area one by one according to the preset time interval. For example, the abnormality in the abnormal data list is set every N minutes. The data is written into the buffer area to cache the abnormal data generated during the execution of the Flash player.
  • the maximum number m of abnormal data stored in the buffer In order to control the size of the flash buffer to prevent the Flash cache from affecting browser performance too much, set the maximum number m of abnormal data stored in the buffer. Each time the abnormal data in the abnormal data list is written into the buffer area, the number n of the current abnormal data in the buffer area is determined, and if the number n of the current abnormal data in the buffer area is greater than the maximum size of the abnormal data stored in the set buffer area If the number of bars is m, the nm abnormal data exceeding the maximum number of pieces is cleared, wherein m and n are positive integers.
  • the abnormal data in the buffer area is stored in chronological order.
  • the number of current abnormal data in the buffer area is greater than the maximum number, the abnormal data exceeding the maximum number is cleared in time order. For example, when an abnormal data is written into the buffer area, it is determined that the number of current abnormal data in the buffer area is 25, and the maximum number of abnormal data stored in the set buffer area is 20, and the buffer area is written. The 5 abnormal data of the earliest time is cleared, so that the abnormal data in the buffer area is always within 20, which does not affect the performance of the browser.
  • the abnormal data is displayed according to a preset style: by adding a new line character between each adjacent two abnormal data.
  • the way to display multiple anomalous data is not limited to the foregoing embodiments.
  • the export abnormal data button is also added in the Flash player.
  • the abnormal data panel may be popped up by clicking the abnormal data button, and the abnormal data is displayed in the abnormal data panel, wherein the abnormal data may be derived from the cache.
  • the zone can also be sourced from the list of exception data in the exception data manager.
  • you can add a line break which can be implemented by the following program code:
  • errTxt is the exception error text
  • list is the exception error data
  • a Flash player abnormal log management system including a configuration module 21, a storage module 22, a display module 23, and a cache module 24.
  • the configuration module 21 is configured to configure the abnormal node at different key logical positions during the execution logic of the Falsh player.
  • the storage module 22 is configured to generate corresponding abnormal data when the abnormal node is triggered, and store each abnormal data in the abnormal data manager, wherein the abnormal data manager is located in the Flash player.
  • the display module 23 is configured to export the abnormal data from the abnormal data manager and display it according to a preset style.
  • the abnormal node is an input/output abnormal node and a read abnormal node.
  • the configuration module 21 is further configured to configure an input/output abnormality in a corresponding key logical position during execution logic of the Flash player. Node and multiple read exception nodes.
  • the configuration module 21 is further configured to: according to the Flash player, load the resource by calling a resource loading method in the loading resource class, and configure an input and output abnormal node in the resource loading method, so as to input and output an abnormality when loading the resource.
  • the capture abnormal node corresponding to the service scenario is configured in the code block corresponding to the different service scenarios to capture the data read exception in the service scenario.
  • the configuration module 21 is further configured to configure a unique identifier for each abnormal node.
  • each of the abnormal data includes an abnormality occurrence time, an abnormal node unique identifier, and an abnormal data content.
  • configuration module 21 is further configured to configure the abnormal data manager in the Flash player by writing an exception data management class in the Flash player and instantiating the exception data management class.
  • the display module 23 is further configured to display a plurality of abnormal data by adding a line break between each adjacent two abnormal data.
  • the cache module 24 is configured to write the abnormal data in the abnormal data list one by one into the buffer area according to the preset time interval to cache the abnormal data.
  • an electronic device includes: a processor 301, a memory 302, and a bus 303.
  • the processor 301 and the memory 302 complete communication with each other through the bus 303. .
  • the processor 301 is configured to invoke program instructions in the memory 302 to perform the methods provided by the foregoing method embodiments, for example, including: configuring at a corresponding critical logical position during execution logic of the Falsh player.
  • An abnormal node when the abnormal node is triggered, generates corresponding abnormal data, and stores each abnormal data in the abnormal data manager, wherein the abnormal data manager is located in the Flash player; from the abnormal data manager Export exception data and display it in a preset style.
  • the invention discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, the computer being capable of executing the corresponding implementation when the program instructions are executed by the computer
  • the intelligent filtering control layout method provided by the example includes, for example, configuring an abnormal node at a corresponding key logical position during execution logic of the Falsh player; when the abnormal node is triggered, generating corresponding abnormal data, and Each piece of exception data is stored in the exception data manager, wherein the exception data manager is located in the Flash player; the exception data is exported from the exception data manager and displayed according to a preset style.
  • the present invention also provides a non-transitory computer readable storage medium storing computer instructions for causing a computer to execute the smart layout control method provided by the corresponding embodiment, for example, including During the execution logic of the Falsh player, the abnormal node is configured at the corresponding key logical position; when the abnormal node is triggered, the corresponding abnormal data is generated, and each abnormal data is stored in the abnormal data manager, wherein The abnormal data manager is located in the Flash player; the abnormal data is exported from the abnormal data manager and displayed according to a preset style.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.
  • the invention provides a Flash player abnormal log management method and system, and constructs a set of abnormal data collection and storage mechanism in a Flash player, and automatically collects a Flash player during execution by configuring an abnormal node in the Flash player.
  • the generated abnormal data is stored and used as the later supporting data.
  • the abnormal data is exported, so that the technical support personnel can reproduce the scene according to the abnormal data, which is convenient for abnormal positioning.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Debugging And Monitoring (AREA)

Abstract

本发明提供一种Flash播放器异常日志管理方法及系统,所述的方法包括:在Falsh播放器的执行逻辑过程中,在相应的关键逻辑位置处配置异常节点;当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;从异常数据管理器中导出异常数据,并按照预设的样式进行展示。通过本发明,在Flash播放器中设置异常数据管理器,构建一套异常数据的收集以及存储机制,通过在Flash播放器中配置异常节点,自动收集Flash播放器执行过程中产生的异常数据,并进行存储,作为后期的支持数据,当需要查看异常数据时,将异常数据导出,以便技术支持人员根据异常数据进行场景的重现,方便异常定位。

Description

一种Flash播放器异常日志管理方法及系统
交叉引用
本申请引用于2017年6月29日提交的专利名称为“一种Flash播放器异常日志管理方法及系统”的第201710516147.X号中国专利申请,其通过引用被全部并入本申请。
技术领域
本发明涉及日志管理技术领域,更具体地,涉及一种Flash播放器异常日志管理方法及系统。
背景技术
Falsh播放器是一个客户端,不像其它服务器存在数据库,可以建表来存储一些异常数据,根据需要再导出异常数据。Flash播放器在被用户使用的过程中可能会遇到一些异常,使用户无法正常使用Flash播放器。
有一些用户可能会去找对应的技术支持人员来解决这些问题,让自己可以正常体验产品,也有一些用户可能流失了。当技术支持人员接收到用户异常反馈时,可能又因为时效性或者一些其它原因,比如用户没有保留异常现场,目前这种情况下技术支持人员没有数据支持,也无法根据异常数据通过重现场景来分析异常情况。
如果遇到场景难重现的情况下或者无法重现的情况下,技术支持人员只能采取多次模仿场景来重现异常场景或者直接等待用户下一次使用Flash播放器来重现异常场景。技术支持人员这种被动的追查异常的方式效率比较低,同时大大增加人力成本最后也不能直接解决问题。
发明内容
本发明提供一种克服上述问题或者至少部分地解决上述问题的Flash播放器异常日志管理方法及系统,能够克服Flash播放器执行过程中异常定位难的问题。
根据本发明的第一方面,提供了一种Flash播放器异常日志管理方法,包括:
S1,在Falsh播放器的执行逻辑过程中,在相应的关键逻辑位置处配置异常节点;
S2,当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;
S3,从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
本发明的有益效果为:在Flash播放器中构建一套异常数据的收集以及存储机制,通过在Flash播放器中配置异常节点,自动收集Flash播放器执行过程中产生的异常数据,并进行存储,作为后期的支持数据,当需要查看异常数据时,将异常数据导出,以便技术支持人员根据异常数据进行场景的重现,方便异常定位。
在上述技术方案的基础上,本发明还可以作如下改进。
进一步的,所述异常节点为输入输出异常节点和读取异常节点,所述步骤S1进一步包括:
在Flash播放器的执行逻辑过程中,在相应的关键逻辑位置配置一个输入输出异常节点和多个读取异常节点。
进一步的,所述在相应的关键逻辑位置配置一个输入输出异常节点进一步包括:
基于Flash播放器通过调用加载资源类中的资源加载方法来加载资源,在资源加载方法中配置输入输出异常节点,以对加载资源时的输入输出异常进行捕捉。
进一步的,所述在相应的关键逻辑位置配置多个读取异常节点进一步包括:
根据业务场景的不同,在不同的业务场景对应的代码块中配置与业务场 景对应的读取异常节点,以对业务场景中的数据读取异常进行捕捉。
进一步的,所述步骤S1还包括:
为每一个异常节点配置唯一标识,相应地,每一条所述异常数据包括异常发生时间、异常节点唯一标识以及异常数据内容。
进一步的,所述步骤S2中通过如下方式在Flash播放器中配置异常数据管理器:
通过在Flash播放器中编写异常数据管理类,并实例化所述异常数据管理类,以实现在Flash播放器中配置异常数据管理器。
进一步的,所述步骤S2中,按照预设的样式对异常数据进行展示:
通过在每相邻两条异常数据之间增加换行符的方式对多条异常数据进行展示。
进一步的,步骤S2还包括:
按照预设时间间隔,将异常数据列表中的异常数据逐条写入缓存区,以对异常数据进行缓存。
根据本发明的第二方面,提供了一种Flash播放器异常日志管理系统,包括:
配置模块,用于在Falsh播放器的执行逻辑过程中,在不同的关键逻辑位置处配置异常节点;
存储模块,用于当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;
展示模块,用于从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
根据本发明的第三方面,提供了一种非暂态计算机可读存储介质,所述非暂态计算机可读存储介质存储计算机指令,所述计算机指令使所述计算机执行上述各实施方法。
附图说明
图1为本发明一个实施例的Flash播放器异常日志管理方法流程图;
图2为本发明又一个实施例的Flash播放器异常日志管理系统整体连接框图;
图3为本发明一个实施例的电子设备连接框图。
具体实施方式
下面结合附图和实施例,对本发明的具体实施方式作进一步详细描述。以下实施例用于说明本发明,但不用来限制本发明的范围。
参见图1,提供了本发明一个实施例的Flash播放器异常日志管理方法,能够自动对Flash播放器执行过程中的异常数据进行收集存储,以便技术支持人员根据异常数据进行分析定位。该方法包括:S1,在Falsh播放器的执行逻辑过程中,在不同的关键逻辑位置处配置异常节点;S2,当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;S3,从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
在Flash播放器执行播放过程中,在关键逻辑位置添加异常节点,当异常节点被触发时,也就是Flash播放器发生异常时,对应生成一条异常数据。针对现有的对于Flash播放器的异常没有数据支持,本实施例通过在Flash播放器的执行逻辑中增加多个异常节点,能够对Flash播放器的异常进行捕捉,并在Flash播放器中定义一个异常数据管理器,将每一个异常节点处生成的异常数据存储于异常数据管理器中。当技术支持人员需要导出异常数据时,就能够从异常数据管理器中导出异常数据,按照一定的样式进行展示,以便技术支持人员查看异常数据,进行分析定位。
在上述实施例的基础上,本发明的另一个实施例中,所述异常节点为输入输出异常节点和读取异常节点,所述步骤S1进一步包括:在Flash播放器的执行逻辑过程中,在相应的关键逻辑位置配置一个输入输出异常节点和多个读取异常节点。
在Flash播放器中存在大量的逻辑操作,比如,连接TCP(Transmission  Control Protocol,传输控制协议)服务器、连接弹幕服务器、加载静态资源以及加载视频流等,主要的逻辑异常也存在于这些操作中。逻辑异常主要分为输入输出异常ioError和读取异常EOFError。因此,本实施例中的异常节点主要为输入输出异常节点和读取异常节点。其中,在本实施例中,输入输出异常节点只需要配置一个,而读取异常节点需要配置多个。
在上述各实施例的基础上,本发明的另一个实施例中,所述在相应的关键逻辑位置配置一个输入输出异常节点进一步包括:基于Flash播放器通过调用加载资源类中的资源加载方法来加载资源,在资源加载方法中配置输入输出异常节点,以对加载资源时的输入输出异常进行捕捉。
输入输出异常ioError是指当某些对象的输入或者输出操作失败时引发的,这种异常在Flash播放器中通常会在加载服务器资源时出现,比如,需要加载的资源不存在。由于Flash播放器根据具体的模块加载资源比较零散,为了便于管理现状,Flash播放器采取了资源加载类assetsManager来加载资源,在资源加载类assetsManager中会提供一个资源加载方法loadAsstes来加载资源,这也是Flash播放器唯一的加载资源入口。由于在Flash播放器加载资源时,只存在一个加载资源入口,因此,本实施例只需要在这个加载资源的入口放置一个输入输出异常节点即可,即在在资源加载方法中配置输入输出异常节点,就能够对Flash播放器加载资源时的输入输出异常进行捕捉。
在loadAsstes中创建一个loader对象来加载资源,再监听loader的输入输出异常就能捕获到Flash播放器加载资源时候的ioError,这样ioError的节点就建立起来了。例如:
var loader:Loader=new Loader();
loader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERRO R,IoErrorHandler);
loader.load(new URLRequest(url));
其中,IoErrorHandler方法就是输入输出异常发生时的操作函数。
在上述实施例的基础上,本发明的一个实施例中,所述在相应的关键逻 辑位置配置多个读取异常节点进一步包括:根据业务场景的不同,在不同的业务场景对应的代码块中配置与业务场景对应的读取异常节点,以对业务场景中的数据读取异常进行捕捉。
EOFError是指读取某些数据时,超出了数据的范围引起的异常。常见的场景的是客户端与服务器通讯时,客户端读取服务器发送二进制数据长度超过服务器所发送的数据长度。由于在Flash播放器执行的过程中,会存在很多的有业务场景,不同的业务场景都会存在数据的读取,因此,针对每一个业务场景,都需要有一个读取异常节点来捕捉该业务场景中的数据读取异常。具体实现时,是通过在每一个业务场景对应的代码块中配置与业务场景对应的读取异常节点,以对业务场景中的数据读取异常进行捕捉。
相对于输入输出异常ioError,读取异常EOFError过于零散,不便于管理,只能手动在关键逻辑节点上去添加异常节点。具体的采用Try..catch..finally等函数来实现。Try函数是两个对象的比较操作,或解析数据操作;catch函数是捕获到Try函数里面的错误响应,最后finally函数执行异常处理。这样通过Try..catch..finally等函数就可以在执行逻辑中容易发生异常或者需要检查异常的位置建立异常节点。
在上述各实施例的基础上,本发明的另一个实施例中,所述步骤S1还包括:为每一个异常节点配置唯一标识,相应地,每一条所述异常数据包括异常发生时间、异常节点唯一标识以及异常数据内容。
在Flash播放器的整个逻辑执行过程中配置了一个输入输出异常节点和多个读取异常节点,为每一个异常节点配置唯一标识,通过异常节点的唯一标识就能够知道每一个异常节点的类型,即异常节点是输入输出异常节点还是读取异常节点,以及是哪一个业务场景对应的异常节点。其中,每一条异常数据包括异常发生时间、异常节点唯一标识以及异常数据内容。
需要说明的是,当输入输出异常节点被触发时,输入输出异常ioError会执行IoErrorHandler方法,读取异常EOFError会执行finally逻辑块,在IoErrorHandler方法和finally逻辑块中生成异常数据errdata对象。其中,errdata对象的结构为:
errdata:{time:Errtime,type:errType,data:handleData};
其中,Errtime为异常产生时间,此处为系统时间,才用系统函数gettime()获取;errType为异常类型,来源于ioError的报错设置为1,来源于EOFError报错设置为2;handleData为异常数据内容,来源于异常抛出时的事件描述。
对于异常数据内容,在IoErrorHandler方法中可以根据加载的loader取得加载链接URL(Uniform Resource Locator,统一资源定位符)把url赋值给handleData作为异常数据,而在finally逻辑块中获取EOFError描述属性text并赋值给handleData作为异常数据。
在上述各实施例的基础上,本发明的一个实施例中,为了便于异常数据的管理,在Flash播放器中配置一个异常数据管理器,在异常数据管理器中构建异常数据列表,将每一条异常数据以异常数据发生时间顺序存储于异常数据列表中。
当Flash播放器的关键逻辑位置处添加异常节点,当异常节点被触发时,对应生成该异常节点的一条异常数据。其中,异常数据中包括异常发生时间,以发生异常时本地系统时间为异常发生时间,发生异常的异常节点唯一标识以及具体的异常数据内容,也就是在每条异常数据里面记载了单次异常发生的时间、该异常属于哪种类型的异常以及具体异常数据。其中,根据发生异常的异常节点唯一标识,就能够确定异常属于哪种类型。
在本实施例中,在Flash播放器中的异常数据管理器中构建一异常数据列表,将每一个异常节点处产生的异常数据以异常数据发生的时间顺序存储于异常数据列表中,以备后续作为数据支持。
在Flash播放器中配置异常数据管理器时,通过在Flash播放器中编写异常数据管理类,并实例化所述异常数据管理类,以实现在Flash播放器中配置异常数据管理器。
在上述各实施例的基础上,本发明的另一个实施例中,所述步骤S2还包括:按照预设时间间隔将异常数据列表中的异常数据逐条写入缓存区,以对异常数据进行缓存。
为确保在Flash播放器关闭后,异常数据依然能够追踪到,按照预设时间间隔将异常数据列表中的异常数据逐条写入缓存区,比如,设定每隔N分钟将异常数据列表中的异常数据写入缓存区中,对Flash播放器执行过程中产生的异常数据进行缓存。
为了控制Flash缓存区的大小以免Flash缓存过大影响浏览器性能,设置缓存区存储异常数据的最大条数m。每次将异常数据列表中的异常数据写入缓存区后,判断缓存区中当前异常数据的条数n,若缓存区中当前异常数据的条数n大于设定的缓存区存储异常数据的最大条数m,则将超出最大条数的n-m条异常数据清除,其中,m、n均为正整数。
其中,缓存区中的多条异常数据按照时间顺序存储,当缓存区中当前异常数据的条数大于最大条数,则按照时间顺序将超出最大条数的异常数据清除。比如,当向缓存区中写入一条异常数据后,判断缓存区中当前异常数据的条数为25,而设定的缓存区存储异常数据的最大条数为20,则将缓存区中写入时间最早的5条异常数据清除,使得缓存区中的异常数据一直处于20条以内,这样不会影响浏览器的性能。
在上述各实施例的基础上,本发明的另一个实施例中,所述步骤S2中,按照预设的样式对异常数据进行展示:通过在每相邻两条异常数据之间增加换行符的方式对多条异常数据进行展示。
本实施例还在Flash播放器中添加导出异常数据按钮,当用户需要反馈问题时,可通过点击异常数据按钮弹出异常数据面板,在异常数据面板中展示异常数据,其中,异常数据可来源于缓存区,也可来源于异常数据管理器中的异常数据列表中。为了便于异常数据展示的美观,在每一条异常数据之后,可以添加换行符,可以采用下述的程序代码来实现:
Figure PCTCN2017120170-appb-000001
errTxt为异常错误文本,list为异常错误数据,可以由缓存区中的异常数据和异常数据列表errlist中的异常数据组成,再把errTxt异常错误文本添加到异常数据面板中,用户需要反馈问题时只需要粘贴errTxt中的异常错误文本给技术支持人员。
参见图2,提供了本发明另一个实施例的Flash播放器异常日志管理系统,包括配置模块21、存储模块22、展示模块23和缓存模块24。
配置模块21,用于在Falsh播放器的执行逻辑过程中,在不同的关键逻辑位置处配置异常节点。
存储模块22,用于当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中。
展示模块23,用于从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
其中,所述异常节点为输入输出异常节点和读取异常节点,相应地,所述配置模块21,还用于在Flash播放器的执行逻辑过程中,在相应的关键逻辑位置配置一个输入输出异常节点和多个读取异常节点。
进一步的,所述配置模块21还用于:基于Flash播放器通过调用加载资源类中的资源加载方法来加载资源,在资源加载方法中配置输入输出异常节点,以对加载资源时的输入输出异常进行捕捉;以及,根据业务场景的不同,在不同的业务场景对应的代码块中配置与业务场景对应的读取异常节点,以对业务场景中的数据读取异常进行捕捉。
所述配置模块21,还用于为每一个异常节点配置唯一标识,相应地,每一条所述异常数据包括异常发生时间、异常节点唯一标识以及异常数据内容。
以及,所述配置模块21,还用于通过在Flash播放器中编写异常数据管理类,并实例化所述异常数据管理类,以实现在Flash播放器中配置异常数据管理器。
所述展示模块23,还用于通过在每相邻两条异常数据之间增加换行符的 方式对多条异常数据进行展示。
缓存模块24,用于按照预设时间间隔,将异常数据列表中的异常数据逐条写入缓存区,以对异常数据进行缓存。
参见图3,为本发明一种电子设备,包括:处理器(processor)301、存储器(memory)302和总线303;其中,所述处理器301和存储器302通过所述总线303完成相互间的通信。
所述处理器301用于调用所述存储器302中的程序指令,以执行上述各方法实施例所提供的方法,例如包括:在Falsh播放器的执行逻辑过程中,在相应的关键逻辑位置处配置异常节点;当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
本发明公开一种计算机程序产品,该计算机程序产品包括存储在非暂态计算机可读存储介质上的计算机程序,该计算机程序包括程序指令,当程序指令被计算机执行时,计算机能够执行上述对应实施例所提供的智能过滤的控件布局方法,例如包括:在Falsh播放器的执行逻辑过程中,在相应的关键逻辑位置处配置异常节点;当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
本发明还提供一种非暂态计算机可读存储介质,该非暂态计算机可读存储介质存储计算机指令,该计算机指令使计算机执行上述对应实施例所提供的智能过滤的控件布局方法,例如包括:在Falsh播放器的执行逻辑过程中,在相应的关键逻辑位置处配置异常节点;当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
本领域普通技术人员可以理解:实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成,前述的程序可以存储于一计算机可读取存储介质中,该程序在执行时,执行包括上述方法实施例的步骤;而前述的存储介质包括:ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所描述的实施例仅仅是示意性的,其中作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下,即可以理解并实施。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件。基于这样的理解,上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品可以存储在计算机可读存储介质中,如ROM/RAM、磁碟、光盘等,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行各个实施例或者实施例的某些部分方法。
本发明提供的一种Flash播放器异常日志管理方法及系统,在Flash播放器中构建一套异常数据的收集以及存储机制,通过在Flash播放器中配置异常节点,自动收集Flash播放器执行过程中产生的异常数据,并进行存储,作为后期的支持数据,当需要查看异常数据时,将异常数据导出,以便技术支持人员根据异常数据进行场景的重现,方便异常定位。
最后,本申请的方法仅为较佳的实施方案,并非用于限定本发明的保护范围。凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。

Claims (12)

  1. 一种Flash播放器异常日志管理方法,其特征在于,包括:
    S1,在Falsh播放器的执行逻辑过程中,在相应的关键逻辑位置处配置异常节点;
    S2,当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;
    S3,从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
  2. 如权利要求1所述的Flash播放器异常日志管理方法,其特征在于,所述异常节点为输入输出异常节点和读取异常节点,所述步骤S1进一步包括:
    在Flash播放器的执行逻辑过程中,在相应的关键逻辑位置配置一个输入输出异常节点和多个读取异常节点。
  3. 如权利要求2所述的Flash播放器异常日志管理方法,其特征在于,所述在相应的关键逻辑位置配置一个输入输出异常节点进一步包括:
    基于Flash播放器通过调用加载资源类中的资源加载方法来加载资源,在资源加载方法中配置输入输出异常节点,以对加载资源时的输入输出异常进行捕捉。
  4. 如权利要求2所述的Flash播放器异常日志管理方法,其特征在于,所述在相应的关键逻辑位置配置多个读取异常节点进一步包括:
    根据业务场景的不同,在不同的业务场景对应的代码块中配置与业务场景对应的读取异常节点,以对业务场景中的数据读取异常进行捕捉。
  5. 如权利要求4所述的Flash播放器异常日志管理方法,其特征在于,所述步骤S1还包括:
    为每一个异常节点配置唯一标识,相应地,每一条所述异常数据包括异常发生时间、异常节点唯一标识以及异常数据内容。
  6. 如权利要求1所述的Flash播放器异常日志管理方法,其特征在于,所述步骤S2中通过如下方式在Flash播放器中配置异常数据管理器:
    通过在Flash播放器中编写异常数据管理类,并实例化所述异常数据管理类,以实现在Flash播放器中配置异常数据管理器。
  7. 如权利要求5所述的Flash播放器异常日志管理方法,其特征在于,所述步骤S2中,按照预设的样式对异常数据进行展示:
    通过在每相邻两条异常数据之间增加换行符的方式对多条异常数据进行展示。
  8. 如权利要求7所述的Flash播放器异常日志管理方法,其特征在于,步骤S2还包括:
    按照预设时间间隔,将异常数据列表中的异常数据逐条写入缓存区,以对异常数据进行缓存。
  9. 一种Flash播放器异常日志管理系统,其特征在于,包括:
    配置模块,用于在Falsh播放器的执行逻辑过程中,在不同的关键逻辑位置处配置异常节点;
    存储模块,用于当异常节点被触发时,生成对应的异常数据,并将每一条异常数据存储于异常数据管理器中,其中,所述异常数据管理器位于Flash播放器中;
    展示模块,用于从异常数据管理器中导出异常数据,并按照预设的样式进行展示。
  10. 一种电子设备,其特征在于,包括:
    至少一个处理器、至少一个存储器、通信接口和总线;
    其中,所述处理器、存储器、通信接口通过所述总线完成相互间的通信;
    所述通信接口用于该设备与玩具控制系统的通信设备之间的信息传输;
    所述存储器存储有可被所述处理器执行的程序指令,所述处理器调用所述程序指令能够执行如权利要求1-8任一项所述的方法。
  11. 一种计算机程序产品,其特征在于,所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算机程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,所述计算机指令使所述计算机执行如权利要求1-8任一项所述的方法。
  12. 一种非暂态计算机可读存储介质,其特征在于,所述非暂态计算机可读存储介质存储计算机指令,所述计算机指令使所述计算机执行如权利要求1-8任一项所述的方法。
PCT/CN2017/120170 2017-06-29 2017-12-29 一种Flash播放器异常日志管理方法及系统 WO2019000895A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710516147.XA CN107423090B (zh) 2017-06-29 2017-06-29 一种Flash播放器异常日志管理方法及系统
CN201710516147.X 2017-06-29

Publications (1)

Publication Number Publication Date
WO2019000895A1 true WO2019000895A1 (zh) 2019-01-03

Family

ID=60426380

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/120170 WO2019000895A1 (zh) 2017-06-29 2017-12-29 一种Flash播放器异常日志管理方法及系统

Country Status (2)

Country Link
CN (1) CN107423090B (zh)
WO (1) WO2019000895A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107423090B (zh) * 2017-06-29 2021-02-02 武汉斗鱼网络科技有限公司 一种Flash播放器异常日志管理方法及系统
CN111367750B (zh) * 2018-12-26 2023-06-20 阿里巴巴集团控股有限公司 一种异常处理方法、装置及其设备
CN111427737B (zh) * 2019-01-09 2023-05-05 阿里巴巴集团控股有限公司 一种修改异常日志的方法、装置、及电子设备
CN112988443B (zh) * 2021-03-16 2023-01-10 上海哔哩哔哩科技有限公司 业务异常的处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130060646A1 (en) * 2007-06-12 2013-03-07 Media Forum, Inc. Desktop Extension for Readily-Sharable and Accessible Media Playlist and Media
CN103699483A (zh) * 2013-12-20 2014-04-02 合一网络技术(北京)有限公司 一种flash播放器的播放状态与浏览器兼容测试方法及其装置
CN104883614A (zh) * 2015-05-19 2015-09-02 福建宏天信息产业有限公司 一种基于Adobe FlashPlayer和Jquery框架的WEB视频播放方法
CN104899108A (zh) * 2014-12-26 2015-09-09 北京奇虎科技有限公司 一种浏览器修复方法和浏览器修复系统
CN107423090A (zh) * 2017-06-29 2017-12-01 武汉斗鱼网络科技有限公司 一种Flash播放器异常日志管理方法及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105824754B (zh) * 2016-03-17 2018-11-13 广州多益网络股份有限公司 客户端程序的Python异常捕获和上传的方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130060646A1 (en) * 2007-06-12 2013-03-07 Media Forum, Inc. Desktop Extension for Readily-Sharable and Accessible Media Playlist and Media
CN103699483A (zh) * 2013-12-20 2014-04-02 合一网络技术(北京)有限公司 一种flash播放器的播放状态与浏览器兼容测试方法及其装置
CN104899108A (zh) * 2014-12-26 2015-09-09 北京奇虎科技有限公司 一种浏览器修复方法和浏览器修复系统
CN104883614A (zh) * 2015-05-19 2015-09-02 福建宏天信息产业有限公司 一种基于Adobe FlashPlayer和Jquery框架的WEB视频播放方法
CN107423090A (zh) * 2017-06-29 2017-12-01 武汉斗鱼网络科技有限公司 一种Flash播放器异常日志管理方法及系统

Also Published As

Publication number Publication date
CN107423090B (zh) 2021-02-02
CN107423090A (zh) 2017-12-01

Similar Documents

Publication Publication Date Title
JP7417677B2 (ja) ファイル共有のための技術
US11941017B2 (en) Event driven extract, transform, load (ETL) processing
US11736502B2 (en) Generating meta-notable event summary information
USRE48681E1 (en) System and method for tracking web interactions with real time analytics
US11870795B1 (en) Identifying attack behavior based on scripting language activity
US11238036B2 (en) System performance logging of complex remote query processor query operations
US11422873B2 (en) Efficient message queuing service using multiplexing
US11567959B2 (en) Self-contained files for generating a visualization of query results
WO2019000895A1 (zh) 一种Flash播放器异常日志管理方法及系统
CN106487596A (zh) 分布式服务跟踪实现方法
CN111752799A (zh) 一种业务链路跟踪方法、装置、设备及储存介质
CN105653425A (zh) 基于复杂事件处理引擎的监控系统
CN107807872A (zh) 一种输变电系统运行状态监测方法
US20210136121A1 (en) System and method for creation and implementation of data processing workflows using a distributed computational graph
US11875275B1 (en) Custom time series models in computer analytics systems
CN113254320A (zh) 记录用户网页操作行为的方法及装置
CN111048164A (zh) 一种医学大数据长期保存系统
CN109799981A (zh) 一种基于执行链的集成系统及方法
US12009997B2 (en) Cell-based architecture for an extensibility platform
US20230315580A1 (en) Disaster recovery in a cell model for an extensibility platform
US20230318935A1 (en) Cell-based architecture for an extensibility platform
US11416285B1 (en) Efficient and secure scalable-two-stage data collection
CN117992415A (zh) 跨业务系统的数据融合共享平台、方法、设备及介质
CN113836183A (zh) 将逻辑流表推送到客户端的方法、系统、设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17915499

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17915499

Country of ref document: EP

Kind code of ref document: A1