Athento has traceability systems at different levels to dump system execution and deployment information. This trace is written in the form of logs that are dumped in real time in files within the file system and by subscribing to notification services. Depending on the trace level to be represented (and depending on the established environment), debugging actions, information, warnings and errors can be displayed.
Location of logs and log system used
The log files are written to the following path:
athentose_general.log: output of the application with execution information.
athentose_error.log: output with Athento error output.
The log files of the third party tools used by Athento are also located in /var/log and are actively monitored by the Athento team in order to control their status.
Athento relies on the Django logger service (Python Logging) where trace levels are set for each of the output files.
Monitoring services for errors and other incidents
Athento also uses external monitoring and notification services, which report all the trace context at a given time. One of these services is Sentry, where each and every one of the trace lines foreseen in each environment is exploited, having all the information and context of the client and the server at a given time.
In addition, Athento has the Site24x7 tool that monitors in real time any defined alert that observes the content of the log files to be able to act quickly and effectively.
Access control logs
Network component level traces
The traces collected by Athento at the network component level are established at 3 levels:
Network level: where the entire network flow is traced at a low level. This type of trace is obtained from the network or infrastructure provider's data from their respective management panels.
Firewall level: where the accepted and rejected communication is displayed. This trace also depends on the infrastructure providers used and can be displayed directly in the configuration of the installed software firewall.
Proxy level: where the requests are displayed when they are sent to the service. The proxy trace is established directly in filesystem as we do with the Athento ones. We also exploit it using cloud services to monitor and notify in case of possible warning situations.