This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.e_tools:logging [2020/05/07 16:20] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.e_tools:logging [2021/10/03 18:03] (current) 204.48.92.159 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== Tools: Logging Tools ======== | + | ====== Tools: Logging Tools ====== |
| - | [[dido:public:xapend.tools| Return to Tools ]] | + | [[dido:public:ra:xapend:xapend.e_tools:start| Return to Tools Area]] |
| Source: [[https://logging.apache.org/ | Apache Logging Services ]] | Source: [[https://logging.apache.org/ | Apache Logging Services ]] | ||
| - | * //**Apache Chainsaw** is GUI based log viewer and is a companion application to log4j written by members of the log4j development community. Chainsaw can read local and ssh-reachable regular text log files, as well as log files formatted in Log4j's XMLLayout. Chainsaw can also receive events over TCP and UDP, read events from a DB, and can process events generated by java.util.logging. [[ https://logging.apache.org/chainsaw ]].// | + | * //**Apache Chainsaw** is GUI based log viewer and is a companion [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] to log4j written by members of the log4j development community. Chainsaw can read local and ssh-reachable regular text log files, as well as log files formatted in Log4j's XMLLayout. Chainsaw can also receive events over TCP and UDP, read events from a DB, and can process events generated by java.util.logging. [[ https://logging.apache.org/chainsaw ]].// |
| - | * //**Apache Log4j Audit** provides the information to determine what actions have been performed, or attempted to be performed, by whom, when they did it and what the data associated with the action was. Audit log data is most typically used by security teams to monitor for fraud or illegal or otherwise unauthorized activities and to be able to correct changes that were incorrectly made. Audit logs are often used to demonstrate compliance with legal obligations such as [[dido:public:xapend.glossary:s:sarbanes-oxley_act| Sarbanes-Oxley Act]] or [[dido:public:xapend.glossary:h:health_insurance_portability_and_accountability_act| HIPPA]].[[https://logging.apache.org/log4j-audit/latest/]]// | + | * //**Apache Log4j Audit** provides the information to determine what actions have been performed, or attempted to be performed, by whom, when they did it and what the data associated with the action was. Audit log data is most typically used by security teams to monitor for fraud or illegal or otherwise unauthorized activities and to be able to correct changes that were incorrectly made. Audit logs are often used to demonstrate compliance with legal obligations such as [[dido:public:ra:xapend:xapend.a_glossary:s:sarbanes-oxley_act| Sarbanes-Oxley Act]] or [[dido:public:ra:xapend:xapend.a_glossary:h:hippa| HIPPA]].[[https://logging.apache.org/log4j-audit/latest/]]// |