-
Notifications
You must be signed in to change notification settings - Fork 96
Proposal #3: adding auditing capabilities
The goal of this proposal is to add auditing capabilities to Geostore. The terms auditing, monitoring and logging are often used interchangeably but they have different goals:
- auditing: allow us to understand how the external world interact with our application;
- monitoring: give us information related to the internal execution of our application;
- logging: produces very widespread information that can be very detailed about the whole execution;
That say, if we want to known which is the user that spend more time on a certain map, we will look a the auditing information. If we want to track some performance issue, we will look at the monitoring information. If I want to understand a crash or an unexpected behavior, we will look at the logging information.
In a typical system, auditing information is produced intercepting externals requests to the system. The auditing information is composed of the information contained in the request itself and the information produced during is execution, for example the result code for an HTTP request is only available after the request execution.
Auditing information is typically consumed by third-party applications that will produces reports or provide a user friend visualization of the data.