Intelligent business logging for cloud applications
AssigneeSap SE
InventorsSivaram Subbiah, Ranjit Alapati
Life of this patent
Estimating the term…
Abstract
Disclosed herein are system, method, and computer program product embodiments for operations related to intelligent action logging for cloud applications. An embodiment operates by identifying an event associated with an application executing on the processor. The event is compared to criteria for logging the event in one or more of a plurality of logs. The log includes its own unique criteria for logging the event. If it is determined that the event satisfies the criteria of the action log, then detail about the event are written onto an action log using a log format associated with the action log, which is different from a log format of a technical log.
Claims12
A computer implemented method, comprising:
- identifying, by a processor, an event associated with an application executing on the processor;
- tagging the event with one or more metadata tags based on criteria for logging the event in a plurality of logs, wherein each log comprises unique criteria for logging;
- comparing the event to criteria for logging the event in a plurality of logs;
- determining that the event satisfies the criteria for logging the event to a first log in the plurality of logs in a format different from a second log in the plurality of logs;
- writing details relating to the event into both the first log and the second log, wherein the details further comprises the one or more metadata tags;
- tagging the details written to the first log and the second log with a security tag;
- receiving a request associated with a particular user identifier to view from the first or the second log the details relating to the event associated with the one or more metadata tags;
- determining that the user identifier does include a clearance necessary to view details written to the first log or the second log associated with the security tag;
- and
- providing access to the first or the second log including the details about the event, wherein the first or the second log includes an indicator indicating that details relating to the event exist in a different log in the plurality of logs.
A system, comprising:
- a memory;
- and
- at least one processor coupled to the memory and configured to:
- identify an event associated with an application executing on the processor;
- tag the event with one or more metadata tags based on criteria for logging the event in a plurality of logs, wherein each log comprises unique criteria for logging;
- compare the event to criteria for logging the event in a plurality of logs;
- determine that the event satisfies the criteria for logging the event to a first log in the plurality of logs in a format different from a second log in the plurality of logs;
- write details relating to the event into both the first log and the second log, wherein the details further comprises the one or more metadata tags;
- tag the details written to the first log and the second log with a security tag;
- receive a request associated with a particular user identifier to view from the first or the second log the details relating to the event associated with the one or more metadata tags;
- determining that the user identifier does include a clearance necessary to view details written to the first log or the second log associated with the security tag;
- and
- provide access to the first or the second log including the details about the event, wherein the first or the second log includes an indicator indicating that details relating to the event exist in a different log in the plurality of logs.
A non-transitory computer-readable device having instructions stored on a memory thereon that when executed by at least one processor of the device, causes the at least one processor to perform operations comprising:
- identifying, by a processor, an event associated with an application executing on the processor;
- tagging the event with one or more metadata tags based on criteria for logging the event in a plurality of logs, wherein each log comprises unique criteria for logging;
- comparing the event to criteria for logging the event in a plurality of logs;
- determining that the event satisfies the criteria for logging the event to a first log in the plurality of logs in a format different from a second log in the plurality of logs;
- writing details relating to the event into both the first log and the second log, wherein the details further comprises the one or more metadata tags;
- tagging the details written to the first log and the second log with a security tag;
- receiving a request associated with a particular user identifier to view from the first or the second log the details relating to the event associated with the one or more metadata tags;
- determining that the user identifier does include a clearance necessary to view details written to the first log or the second log associated with the security tag;
- and
- providing access to the first or the second log including the details about the event, wherein the first or the second log includes an indicator indicating that details relating to the event exist in a different log in the plurality of logs.
Dependencies are inferred from the claim text.