Memory System With Error Detection And Retry Modes Of Operation
US-2015378817-A1 · Dec 31, 2015 · US
US9940373B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9940373-B2 |
| Application number | US-201715689232-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 29, 2017 |
| Priority date | Apr 3, 2015 |
| Publication date | Apr 10, 2018 |
| Grant date | Apr 10, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed is a system, method, and computer program product for implementing a log analytics method and system that can configure, collect, and analyze log records in an efficient manner. An improved approach is provided for identifying log files that have undergone a change in status that would require retrieve of its log data, by including a module directly into the operating system that allows the log collection component to be reactively notified of any changes to pertinent log files.
Opening claim text (preview).
What is claimed is: 1. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising: identifying a target subset of OS calls from a plurality of OS calls; intercepting a plurality of invocations of one or more OS calls in the target subset of OS calls; identifying a plurality of log file changes corresponding respectively to the plurality of invocations; identifying a plurality of events corresponding to the plurality log file changes; filtering the plurality of events, based on one or more event filtering criteria, to obtain a subset of events corresponding to a subset from the plurality of log file changes; and writing the subset of events to an event list. 2. The medium of claim 1 , the operations further comprising: refraining from intercepting invocations of one or more other OS calls, from the plurality of OS calls, that are not in the target subset from the plurality of OS calls. 3. The medium of claim 1 , wherein intercepting the plurality of invocations of the one or more OS calls is performed by a module loaded in the OS. 4. The medium of claim 3 , wherein filtering the plurality of events corresponding to the plurality of log file changes is performed by the module loaded in the OS. 5. The medium of claim 3 , wherein writing the subset of events to the event list is performed by the module loaded in the OS. 6. The medium of claim 1 , the operations further comprising: for each particular invocation in the plurality of invocations, forwarding the particular invocation to the OS for execution after intercepting the particular invocation. 7. The medium of claim 1 , wherein intercepting the plurality of invocations comprises replacing one or more memory addresses associated with the one or more OS calls. 8. The medium of claim 1 , the operations further comprising: monitoring, by a log analytics agent, the event list for changes. 9. The medium of claim 1 , wherein the one or more event filtering criteria comprise one or more file location criteria. 10. The medium of claim 1 , the operations further comprising: determining whether a particular invocation in the plurality of invocations was successful, wherein writing an event to the event list, for the particular invocation, is performed only if the particular invocation was successful. 11. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising: identifying a target subset of OS calls from a plurality of OS calls; intercepting a plurality of invocations of one or more OS calls in the target subset of OS calls; identifying a plurality of log file changes corresponding respectively to the plurality of invocations; writing, to an event list, a plurality of events corresponding to the plurality of log file changes; and filtering the event list, based on one or more event filtering criteria, to obtain a filtered event list comprising events corresponding to a subset of the plurality of log file changes. 12. The medium of claim 11 , the operations further comprising: refraining from intercepting invocations of one or more other OS calls, from the plurality of OS calls, that are not in the target subset of the plurality of OS calls. 13. The medium of claim 11 , wherein intercepting the plurality of invocations of the one or more OS calls is performed by a module loaded in the OS. 14. The medium of claim 13 , wherein filtering the event list is performed by the module loaded in the OS. 15. The medium of claim 13 , wherein writing the plurality of events to the event list is performed by the module loaded in the OS. 16. The medium of claim 11 , the operations further comprising: for each particular invocation in the plurality of invocations, forwarding the particular invocation to the OS for execution after intercepting the particular invocation. 17. The medium of claim 11 , wherein intercepting the plurality of invocations comprises replacing one or more memory addresses associated with the one or more OS calls. 18. The medium of claim 11 , the operations further comprising: monitoring, by a log analytics agent, the filtered event list for changes. 19. The medium of claim 11 , wherein the one or more event filtering criteria comprise one or more file location criteria. 20. The medium of claim 11 , the operations further comprising: determining whether a particular invocation in the plurality of invocations was successful, wherein writing an event to the event list, for the particular invocation, is performed only if the particular invocation was successful.
where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title
Configuring for program initiating, e.g. using registry, configuration files · CPC title
Content or structure details of the error report, e.g. specific table structure, specific error fields · CPC title
Handling of user complaints or trouble tickets · CPC title
Parsing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.