GB2553784A - Management of log data in electronic devices - Google Patents
Management of log data in electronic devices Download PDFInfo
- Publication number
- GB2553784A GB2553784A GB1615528.5A GB201615528A GB2553784A GB 2553784 A GB2553784 A GB 2553784A GB 201615528 A GB201615528 A GB 201615528A GB 2553784 A GB2553784 A GB 2553784A
- Authority
- GB
- United Kingdom
- Prior art keywords
- network
- computing device
- service
- machine
- implemented method
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2268—Logging of test results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0745—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in an input/output transactions management context
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/349—Performance evaluation by tracing or monitoring for interfaces, buses
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3636—Software debugging by tracing the execution of the program
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0772—Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
Abstract
The disclosed method comprises receiving operating environment data, such as resource availability data, from connected computing devices and services, analysing the data to create one or more policies governing log data storage and upload parameters, and sending the policies to the connected devices to enable them to limit resource consumption in the management of log data.
Description
„2,UK Patent Application „S,GB ,,,,2553784 | (13) A 21.03.2018 | |
(43) Date of A Publication | ||
(21) Application No: 1615528.5 (22) Date of Filing: 13.09.2016 | (51) INT CL: H04L 29/08 (2006.01) (56) Documents Cited: | |
(71) Applicant(s): ARM Limited (Incorporated in the United Kingdom) 110 Fulbourn Road, Cherry Hinton, CAMBRIDGE, CB1 9NJ, United Kingdom | WO 2004/091149 A2 CN 102984280 A (58) Field of Search: INT CL H04L, H04W Other: WPI EPODOC TXTE | |
(72) Inventor(s): John Eugene Neystadt Ethan Pogrebizsky Erez Landau | ||
(74) Agent and/or Address for Service: TUP Ltd Leeds Innovation Centre, 103 Clarendon Road, LEEDS, LS2 9DF, United Kingdom |
Title of the Invention: Management of log data in electronic devices Abstract Title: Management of log data in electronic systems
The disclosed method comprises receiving operating environment data, such as resource availability data, from connected computing devices and services, analysing the data to create one or more policies governing log data storage and upload parameters, and sending the policies to the connected devices to enable them to limit resource consumption in the management of log data.
Logging arrangement 100
of 3
Logging arrangement 100
FIGURE 1 of 3
Method 200
FIGURE 2 of 3
Network-connected service 300
Network-connected computing device 302 | ||
Device environment component 304 |
I/O interface component 320
FIGURE 3
Application No. GB1615528.5
RTM
Date :7 March 2017
Intellectual
Property
Office
The following terms are registered trade marks and should be read as such wherever they occur in this document:
WiFi (page 5)
Intellectual Property Office is an operating name of the Patent Office www.gov.uk/ipo
MANAGEMENT OF LOG DATA IN ELECTRONIC SYSTEMS
The present technology relates to methods and apparatus for operating electronic systems to manage log data, particularly for networks of connected computing devices and associated network-connected services. Such associated network-connected services may comprise software components running on one or more hardware devices.
Engineers often need to troubleshoot malfunctioning, malevolently interfered-with or erroneously misconfigured computing devices in a network, and to perform many other debugging activities (software- or hardware-related). Typical operations include retrieving logs from the device, which requires electronic connectivity, such as a direct connection like a Universal Serial Bus cable or a network connection; retrieving logs from a network-connected service that computing devices communicate with; and then manually searching for matching log entries to diagnose the problem. The computing devices and the service may be limited by software and hardware or software operating costs, such as shortages of required resources like power memory space and communications availability, which can cause performance problems and excessive memory consumption for storing logs. After they have been collected, the log entries must then be correlated with corresponding log entries from other devices and services by an administrator or system programmer, typically based on matching up internet protocol IP addresses, task identifiers, timestamps or similar parameters. Such correlation is manual, slow and especially difficult in the case of multiple devices connected via a network address translation (NAT) device, or where devices perform multiple transactions at the same time.
In a first approach to the many difficulties encountered in logging, the described technology provides a machine-implemented method of operating a network-connected service comprising: establishing communication with a network-connected computing device; acquiring, by the network-connected service from the network-connected computing device at least one indication of availability to the network-connected computing device of at least one resource; acquiring, by the network-connected service at least one indication of availability to the network-connected service of at least one resource; analysing a plurality of the indications to determine at least one of an optimal time and an optimal communication configuration for transmission of log data from the networkconnected computing device to the network-connected service, where the optimal time and the optimal communication configuration are determined by resource availability to at least one of the network-connected computing device and the network-connected service; and sending, to the network-connected computing device, log transmission policy data to enable the network-connected computing device to select at least one of a transmission time and a communication configuration for transmission of the log data network-connected service in compliance with the policy data.
Implementations of the disclosed technology will now be described, by way of example only, with reference to the accompanying drawings, in which:
Figure 1 shows a logging arrangement within which the presently described technology may be implemented;
Figure 2 shows an example of a method of operation according to the presently described technology; and
Figure 3 shows an example of an electronic device operable according to the presently described technology.
In Figure 1, there is shown a logging arrangement 100 within which the presently described technology may be implemented. Logging arrangement 100 comprises one or more computing devices 102 operatively connected to one or more services 110. Service 110 may comprise, for example, one or more software components running on single server computers, one or more software components running on a network of server computers, or one or more software components running on virtualised devices arranged in a network, such as, for example, a grid or cloud computing arrangement. Computing devices 102 may include, for example, Internet of Things (IoT) devices, such as networked sensors, consumer devices, intelligent home systems, automotive systems or the like, which may have intermittent network connectivity or power supply availability (being typically battery-powered, they may suffer from reduced battery charge levels at times). Computing device 102 comprises, typically, one or more client applications 104, which generate device logs 106, and, as such devices are typically resource-constrained (in memory space, processing power, power availability and communications connectivity, for example) they cannot themselves perform complex analyses of log data, and thus the log data needs to be limited in size and to be uploaded to a typically less-constrained service for analysis. Further, computing devices 102 are typically constrained in memory space or attached storage available for the storage of logs, and thus need to clear log data at frequent intervals, in order not to impact their performance and the availability of up-to-date log information when it is needed. Computing devices 102 are thus equipped with upload component 108, operable to upload the log data to one or more services 110. Service 110 typically performs transactions or tasks in conjunction with computing devices 102, and is provided with service applications 112, which themselves generate service log data stored in service log 114. Service 110 is equipped with log service component 116, which comprises a device log collection component 118 and a service log collection component 120. Log server component 122 may be provided with the means to make available the service logs 114 and the device logs 106 via I/O interface component 124.
In Figure 2 is shown machine-implemented method 200, which commences at Start step 202. At step 204, communication is established between the service 110 of Figure 1 and one or more computing devices 102 of Figure 1. At step 206, the service acquires operating environment data, such as resource availability data (either for service 110 of Figure 1 or for the one or more computing devices 102 of Figure 1). At step 208, the service analyses the operating environment data, and at step 210, determines the log data upload policy for the one or more computing devices 102 of Figure 1. At step 212 the service transmits the log data upload policy to the one or more computing devices 102 of Figure 1. The process then either loops back to acquire more up-to-date operating environment data at step 206 or ends at End step 214.
In Figure 3 is shown an electronic system according to one implementation of the present technology within a logging arrangement like that shown in Figure 1 and according to the method of Figure 2. In Figure 3 are shown a network service 300 operatively connected to network connected computing device 302 and to I/O interface component 320. Network computing device 302 comprises a device resource availability component, responsive to interrogation by network service 300 to report on its resource availability to data acquisition component 312 via communications component 318. Network service 300 is equipped with a service resource availability component 306, operable to provide service operating environment data to data acquisition component 312. Data acquisition component 312 is operable to pass the data to analysis component 308, which analyses the operating environment data from at least one of network service 300 and network connected computing device 302 as input to policy generator 310. Policy generator 310 communicates the generated policy to network-connected computing device 302 to enable network-connected computing device 302 to select the time and means by which to transmit logs to network service 300. Optionally, data acquisition component 312 is further operable to cooperate with flow identifier generator 314 to generate flow identifiers to enable correlation of log records by log flow correlator 316 for output via communications component 318 to I/O interface component 320 as an aid to diagnostics. In one alternative, network-connected computing device 302 may itself comprise a flow identifier generator 314 to generate flow identifiers to transmit to network service 300.
A typical flow correlation activity occurs when a network-connected computing device shares workload, either with other network-connected computing devices or with one or more services. A Flow-ID is generated, for example when a new execution flow to be logged starts (e.g. when a device is powered-on, or when a new transaction begins). The Flow-ID is inserted in all log records at any of the devices that are participating in the logged execution flow. Then, when the logs for an execution flow need to be analysed, log records from the participating devices can be correlated by matching Flow-IDs belonging to the same flow. Once the log for the flow is reassembled from multiple log records, all having matching Flow-IDs, it can be used to analyse malfunctions, performance, reliability and various other analytical uses known in the art.
The present technology is thus operable to collect logs from computing devices according to a configuration policy sent to the devices from a service. The policy may be based on resource availability at one or more of the networkconnected computing device, the service, and the communication channels. The policy assists the computing device in determining when to upload logs and on what kind of network connection type (e.g. Wi-Fi or 3G). The policy may include, for example, a time of day (e.g. 2:00AM), a range of permitted times, one or more excluded times, an interval (e.g. every 4h), or a piggyback parameter (e.g. when other communication with the device occurs) to conserve resources, such as device battery and connectivity fees, or to avoid conflict with higher-priority or very resource-intensive workloads. Other resources, such as bandwidth of communications channels or memory and external storage space at either the service or the computing device, may also be taken into account in the creation of the policy. The technology may operate by interrogating devices to acquire upto-date individual or generalizable information about their resources -- for example, one device or all devices in class X may tend to be low on power at certain times of day, or network Y is busiest when the east coast of the USA wakes up and many of its inhabitants log-in to check emails, or device memory is more likely to be heavily used when a device is processing an end-of-day database reorganisation or downloading and installing new firmware - this applies both on the network-connected computing device and on the service. Further, diagnostic log receipt and analysis at a service must often be given a lower priority than normal user transaction workloads, and thus the service itself may be constrained. When the resource information is received, the service can analyse the accumulated data and create, for example, a device or device class policy that helps the device select a time or communications means to send log data to the service.
In one implementation, the device configuration may be performed by the network service or by other means, for example, by a system administrator or a device manufacturer at production time. Device configuration may incorporate, among other things, keys for log encryption into the network-connected computing device. Device configuration may further include parameters governing, for example, the log size permitted on the device and the compression means for the network-connected computing device to use to compress log data to further reduce the resource cost associated with its storage and transmission. Compression means may include, for example, true compression by such methods as Lempel-Ziv-Welch encoding, or may involve encoding by means of a fixed lookup table shared by the network-connected computing device and the service.
Device configuration may also include parameters governing a log filtering arrangement to allow the device to minimize storage, network bandwidth and battery consumption on the network-connected computing device where these resources are often extremely scarce. Such a log filter may include, for example, the component name and the logged event severity level, so that only a subset of relevant logs will be kept on the device or transmitted over the communications channel.
In a refinement, the service may be operable to accept an opt-in signal from the network-connected computing device to indicate acceptance of control in compliance with said policy data. The opt-in may be for all customer devices, a specified device, according to device ID or network address, or for a group of devices, according to device attributes, such as a firmware version or a class property configured on the device.
In implementations of the presently-described technique, at least one resource at the network-connected computing device or at the service may comprise, for example, memory or external storage space availability, power level (such as battery charge level), processor availability and communications capacity and availability. The service may be operable to send configuration data to cause the network-connected computing device to filter log data according to a log filter policy. Such a log filter policy may be based on, for example, the component name and the logged event severity level (e.g., critical, error, info, debug), so that only a subset of relevant logs will be kept on the device or transmitted over the communications channel.
In a refinement, the network-connected service may be arranged to generate at least one flow identifier to be associated with at least one execution flow of the network-connected computing device, the network-connected computing device and the service being operable to identify at least one subset of the log data by associating log records from the execution flow with the at least one flow identifier, to receive an upload of log data from the network-connected computing device and to correlate the log data according to the at least one flow identifier.
The network-connected service may be operable to accept an opt-in signal from the at least one network-connected computing device to indicate acceptance of control in compliance with said policy data.
The present technique may be implemented such that the networkconnected service may comprises a virtual device, which may be, for example, a local partition of a multi-partition system, or which may be distributed for operation, for example, in a grid environment, a cloud environment, or any other distributed processing environment.
As will be appreciated by one skilled in the art, the present technique may be embodied as a system, method or computer program product. Accordingly, the present technique may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware.
Furthermore, the present technique may take the form of a computer program product embodied in a computer readable medium having computer readable program code embodied thereon. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
Computer program code for carrying out operations of the present techniques may be written in any combination of one or more programming languages, including object oriented programming languages and conventional procedural programming languages.
For example, program code for carrying out operations of the present techniques may comprise source, object or executable code in a conventional programming language (interpreted or compiled) such as C, or assembly code, code for setting up or controlling an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array), or code for a hardware description language such as Verilog™ or VHDL (Very high speed integrated circuit Hardware Description Language).
The program code may execute entirely on the user's computer, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network. Code components may be embodied as procedures, methods or the like, and may comprise subcomponents which may take the form of instructions or sequences of instructions at any of the levels of abstraction, from the direct machine instructions of a native instruction-set to high-level compiled or interpreted language constructs.
It will also be clear to one of skill in the art that all or part of a logical method according to embodiments of the present techniques may suitably be embodied in a logic apparatus comprising logic elements to perform the steps of the method, and that such logic elements may comprise components such as logic gates in, for example a programmable logic array or application-specific integrated circuit. Such a logic arrangement may further be embodied in enabling elements for temporarily or permanently establishing logic structures in such an array or circuit using, for example, a virtual hardware descriptor language, which may be stored and transmitted using fixed or transmittable carrier media.
In one alternative, an embodiment of the present techniques may be realized in the form of a computer implemented method of deploying a service comprising steps of deploying computer program code operable to, when deployed into a computer infrastructure or network and executed thereon, cause said computer system or network to perform all the steps of the method.
In a further alternative, an embodiment of the present technique may be realized in the form of a data carrier having functional data thereon, said functional data comprising functional computer data structures to, when loaded into a computer system or network and operated upon thereby, enable said computer system to perform all the steps of the method.
It will be clear to one skilled in the art that many improvements and modifications can be made to the foregoing exemplary embodiments without departing from the scope of the present technique.
Claims (11)
1. A machine-implemented method of operating a networkconnected service comprising:
5 establishing communication with a network-connected computing device;
acquiring, by said network-connected service from a said networkconnected computing device at least one indication of availability to said network-connected computing device of at least one first resource;
acquiring, by said network-connected service at least one indication of availability to said network-connected service of at least one further resource;
15 analysing a plurality of said indications to determine at least one of a time and a communication configuration for transmission of log data from said network-connected computing device to said network-connected service, where said time and said communication configuration are determined by resource availability to at least one of said network20 connected computing device and said network-connected service; and sending, to said network-connected computing device, log transmission policy data to enable said network-connected computing device to select at least one of a transmission time and a communication configuration for
25 transmission of said log data to said network-connected service in compliance with said policy data.
2. The machine-implemented method of claim 1, wherein said at least one said first resource comprises at least one of a memory space, a power level
30 and a communications capacity.
3. The machine-implemented method of claim 1 or claim 2, wherein said at least one said second resource comprises at least one of a memory space, a power level and a communications capacity.
26 04 17
4. The machine-implemented method of any preceding claim, further comprising sending configuration data to cause said network-connected computing device to filter log data according to a log filter policy.
5 5. The machine-implemented method of claim 4, wherein said log filter policy comprises at least one of a component identifier and a severity indicator.
6. The machine-implemented method of any preceding claim, said
10 network-connected service being further operable to:
generate at least one flow identifier to be associated with at least one execution flow of said network-connected computing device, said network-connected computing device being operable to identify at least one 15 subset of said log data by associating log records from said execution flow with said at least one flow identifier;
receive an upload of said log data from said network-connected computing device; and correlate said log data at said network-connected service according to said at least one flow identifier.
7. The machine-implemented method of any preceding claim, said
25 network-connected service being further operable to accept an opt-in signal from said at least one said network-connected computing device to indicate acceptance of control in compliance with said policy data.
8. The machine-implemented method of any preceding claim, said
30 network-connected service comprising a virtual device.
9. The machine-implemented method of claim 8, said network-connected service comprising a virtual device operable in at least one of a grid environment and a cloud environment.
10. An electronic control device comprising logic apparatus operable to perform all the steps of the method of any preceding claim.
11. A computer program comprising computer program code to, when
5 loaded into a computer system, cause said system to perform all the steps of the method of any of claims 1 to 9.
26 04 17
Intellectual
Property
Office
Application No: Claims searched:
GB1615528.5
1-11
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1615528.5A GB2553784B (en) | 2016-09-13 | 2016-09-13 | Management of log data in electronic systems |
US15/689,409 US20180074933A1 (en) | 2016-09-13 | 2017-08-29 | Management of log data in electronic systems |
KR1020170115156A KR102328938B1 (en) | 2016-09-13 | 2017-09-08 | Management of log data in electronic systems |
CN201710814636.3A CN107818039A (en) | 2016-09-13 | 2017-09-12 | The management of daily record data in electronic system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1615528.5A GB2553784B (en) | 2016-09-13 | 2016-09-13 | Management of log data in electronic systems |
Publications (3)
Publication Number | Publication Date |
---|---|
GB201615528D0 GB201615528D0 (en) | 2016-10-26 |
GB2553784A true GB2553784A (en) | 2018-03-21 |
GB2553784B GB2553784B (en) | 2019-02-06 |
Family
ID=57234411
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
GB1615528.5A Expired - Fee Related GB2553784B (en) | 2016-09-13 | 2016-09-13 | Management of log data in electronic systems |
Country Status (4)
Country | Link |
---|---|
US (1) | US20180074933A1 (en) |
KR (1) | KR102328938B1 (en) |
CN (1) | CN107818039A (en) |
GB (1) | GB2553784B (en) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2564396B (en) * | 2017-07-06 | 2020-12-02 | Advanced Risc Mach Ltd | Light animation service |
US11157442B2 (en) * | 2017-07-14 | 2021-10-26 | Ricoh Company, Ltd. | Information processing apparatus, information processing system, and information processing method |
JP6926953B2 (en) * | 2017-10-31 | 2021-08-25 | 富士通株式会社 | Information processing equipment, information processing methods and programs |
CN109582568A (en) * | 2018-11-13 | 2019-04-05 | 武汉风行在线技术有限公司 | A kind of data report automated testing method |
KR20200098847A (en) * | 2019-02-13 | 2020-08-21 | 삼성전자주식회사 | Electronic apparatus and control method thereof |
KR20210127095A (en) * | 2020-04-13 | 2021-10-21 | 현대자동차주식회사 | Method and apparatus for managing log information in machine to machine system |
CN111865674B (en) * | 2020-07-09 | 2024-01-09 | 腾讯科技(深圳)有限公司 | Log processing method, device and medium |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2004091149A2 (en) * | 2003-04-09 | 2004-10-21 | International Business Machines Corporation | Method and apparatus for data logging |
CN102984280A (en) * | 2012-12-18 | 2013-03-20 | 北京工业大学 | Data backup system and method for social cloud storage network application |
Family Cites Families (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7373410B2 (en) * | 2002-10-23 | 2008-05-13 | Genesys Telecommunications Laboratories, Inc. | Method and system for providing adaptive and proactive interaction management for multiple types of business interactions occurring in a multimedia communications environment |
CN100461710C (en) * | 2007-03-15 | 2009-02-11 | 华为技术有限公司 | Distributed system journal collecting method and system |
US20100223446A1 (en) * | 2009-02-27 | 2010-09-02 | Microsoft Corporation | Contextual tracing |
US8825843B2 (en) * | 2010-08-02 | 2014-09-02 | Vestra Resources, Inc. | System and methods for monitoring a geographic information system |
WO2012020829A1 (en) * | 2010-08-12 | 2012-02-16 | 京セラ株式会社 | Wireless measurement collection method and wireless terminal |
US8600575B2 (en) * | 2010-09-24 | 2013-12-03 | Synapsense Corporation | Apparatus and method for collecting and distributing power usage data from rack power distribution units (RPDUs) using a wireless sensor network |
US9047074B2 (en) * | 2010-08-30 | 2015-06-02 | Synapsense Corporation | Apparatus and method for managing power capacity in data centers using a wireless sensor network |
US20120102543A1 (en) * | 2010-10-26 | 2012-04-26 | 360 GRC, Inc. | Audit Management System |
KR101425107B1 (en) * | 2010-10-29 | 2014-08-01 | 한국전자통신연구원 | Apparatus for sharing security information among network domains and method for the same |
US20120311575A1 (en) * | 2011-06-02 | 2012-12-06 | Fujitsu Limited | System and method for enforcing policies for virtual machines |
US20130227352A1 (en) * | 2012-02-24 | 2013-08-29 | Commvault Systems, Inc. | Log monitoring |
US9692827B2 (en) * | 2012-03-28 | 2017-06-27 | International Business Machines Corporation | Systems and methods for provisioning sensing resources for mobile sensor networks |
US9342537B2 (en) * | 2012-04-23 | 2016-05-17 | Commvault Systems, Inc. | Integrated snapshot interface for a data storage system |
US9743246B2 (en) * | 2012-07-17 | 2017-08-22 | Intertrust Technologies Corporation | Portable resource management systems and methods |
US8655307B1 (en) | 2012-10-26 | 2014-02-18 | Lookout, Inc. | System and method for developing, updating, and using user device behavioral context models to modify user, device, and application state, settings and behavior for enhanced user security |
US9432916B2 (en) * | 2012-12-27 | 2016-08-30 | Intel Corporation | Situation aware sensor power management |
US10034144B2 (en) * | 2013-02-22 | 2018-07-24 | International Business Machines Corporation | Application and situation-aware community sensing |
US9846721B2 (en) * | 2013-03-13 | 2017-12-19 | Genesys Telecommunications Laboratories, Inc. | Log file management tool |
US9495378B2 (en) * | 2013-08-27 | 2016-11-15 | Purdue Research Foundation | Tracing message transmissions between communications network devices |
US10133741B2 (en) * | 2014-02-13 | 2018-11-20 | Amazon Technologies, Inc. | Log data service in a virtual environment |
US9798596B2 (en) * | 2014-02-27 | 2017-10-24 | Commvault Systems, Inc. | Automatic alert escalation for an information management system |
US9396089B2 (en) * | 2014-05-30 | 2016-07-19 | Apple Inc. | Activity tracing diagnostic systems and methods |
US10445166B2 (en) * | 2014-06-24 | 2019-10-15 | International Business Machines Corporation | System verification of interactive screenshots and log files between client systems and server systems within a network computing environment |
US11575673B2 (en) * | 2014-09-30 | 2023-02-07 | Baxter Corporation Englewood | Central user management in a distributed healthcare information management system |
US10536353B2 (en) * | 2014-10-09 | 2020-01-14 | Splunk Inc. | Control interface for dynamic substitution of service monitoring dashboard source data |
CN105512148A (en) * | 2014-10-14 | 2016-04-20 | 西安三维通信有限责任公司 | Method for information uploading |
WO2016072002A1 (en) * | 2014-11-07 | 2016-05-12 | 株式会社日立製作所 | Electricity storage management system |
CN105703932B (en) * | 2014-11-28 | 2019-03-01 | 广州华多网络科技有限公司 | Log recording method for uploading, log recording method of reseptance, terminal and server |
US10042697B2 (en) * | 2015-05-28 | 2018-08-07 | Oracle International Corporation | Automatic anomaly detection and resolution system |
CN104935601B (en) * | 2015-06-19 | 2018-11-09 | 北京奇安信科技有限公司 | Web log file safety analytical method based on cloud, apparatus and system |
US20160380856A1 (en) * | 2015-06-25 | 2016-12-29 | Qatar University Qstp-B | Systems and methods for tracking devices status and malfunctions in machine-to-machine networks |
US20170004012A1 (en) * | 2015-06-30 | 2017-01-05 | Vmware, Inc. | Methods and apparatus to manage operations situations in computing environments using presence protocols |
WO2017011794A1 (en) * | 2015-07-16 | 2017-01-19 | T-Mobile Usa, Inc. | User device power consumption monitoring and analysis |
US9804913B2 (en) * | 2015-09-25 | 2017-10-31 | Intel Corporation | Management of a fault condition in a computing system |
US10374872B2 (en) * | 2016-05-24 | 2019-08-06 | Apstra, Inc. | Configuring system resources for different reference architectures |
-
2016
- 2016-09-13 GB GB1615528.5A patent/GB2553784B/en not_active Expired - Fee Related
-
2017
- 2017-08-29 US US15/689,409 patent/US20180074933A1/en not_active Abandoned
- 2017-09-08 KR KR1020170115156A patent/KR102328938B1/en active IP Right Grant
- 2017-09-12 CN CN201710814636.3A patent/CN107818039A/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2004091149A2 (en) * | 2003-04-09 | 2004-10-21 | International Business Machines Corporation | Method and apparatus for data logging |
CN102984280A (en) * | 2012-12-18 | 2013-03-20 | 北京工业大学 | Data backup system and method for social cloud storage network application |
Also Published As
Publication number | Publication date |
---|---|
CN107818039A (en) | 2018-03-20 |
KR102328938B1 (en) | 2021-11-22 |
KR20180029900A (en) | 2018-03-21 |
US20180074933A1 (en) | 2018-03-15 |
GB201615528D0 (en) | 2016-10-26 |
GB2553784B (en) | 2019-02-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20180074933A1 (en) | Management of log data in electronic systems | |
CN112714193B (en) | Community data processing system, method, device and equipment based on Internet of things platform | |
CN107210928B (en) | Distributed and adaptive computer network analysis | |
US10644961B2 (en) | Self-adjusting data processing system | |
EP3841730B1 (en) | Identifying device types based on behavior attributes | |
US9705745B2 (en) | System and method for virtualizing software defined network (SDN)-based network monitoring | |
RU2636112C1 (en) | Object of interface management service, function service object and method of control of elements | |
US20130227349A1 (en) | Cloud brokering method and apparatus in heterogeneous cloud environment | |
US10848839B2 (en) | Out-of-band telemetry data collection | |
CN102752770B (en) | Method and device for polling service system | |
CN107211014B (en) | System and method for an event response tool and computer readable medium | |
CN108810042B (en) | Task processing method, related equipment and system | |
US11451443B2 (en) | Communications network performance | |
CN105530137A (en) | Traffic data analysis method and traffic data analysis system | |
US7783752B2 (en) | Automated role based usage determination for software system | |
Fernández et al. | Application of multi-pronged monitoring and intent-based networking to verticals in self-organising networks | |
EP3756310B1 (en) | Method and first node for managing transmission of probe messages | |
CN107924358B (en) | Method and computer-readable medium for probabilistic processor monitoring | |
CN103944777A (en) | Distributed monitoring system information processing method and system | |
KR101545687B1 (en) | packet analysis apparatus based on application | |
Khoudali et al. | EMMCS: An edge monitoring framework for multi-cloud environments using SNMP | |
Brunner | Optimizing the Collection and Processing of Wi-Fi Probe Requests | |
CN114860384A (en) | Data processing method and device and server | |
CN111522642A (en) | Method for acquiring state monitoring data of wind turbine generator, query method and electronic equipment | |
CN104202210B (en) | User customizable protocol capabilities test system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PCNP | Patent ceased through non-payment of renewal fee |
Effective date: 20220913 |