Track Unifying Add In

Through this solution you will be able to record audit trails and log your applications. It does not matter where you have your applications, whether in the Azure cloud or on an On Premise platform, you can add the component that will be in charge of carrying out these operations, the process that is required to successfully implement this solution is the next.

Analysis.

An analysis of the architecture is required in order to carry out the correct implementation of the component.

The following will be validated in this phase:

• Your applications are in the Azure cloud?
• Your applications are on premise infrastructure?
• Your application is in both?
• What sections of your code are you looking to audit?

Once your infrastructure has been analyzed, it is necessary to know where you want to persist the data obtained from the audit trail record and/or event logging of your applications. This can be on a SQL Azure database, Maria DB, ProstgreSQL, My SQL.

With this information, the destination database is configured within the component.

Implementation

The component which will allow the sending of the information to the destination DB is implemented in your code.

This implementation will be applied in the sections that were located in the analysis phase.

Reports

By default, reports that show the following characteristics will be displayed

• IP of the machine from where the request was made
• Request token
• Date and time of the request
• Name of the executed method

Additionally, you can implement more reports, depending on the code sections you want to track, such as:

Monitoring of critical processes

• Start of a process
• Execution of a process
• End of a process

Error tracking and alerts

When an error occurs, it will be registered in the database and additionally you can configure the notifications by email alerting a failure in the process.

Track Unifying Add In

作者 Teia Consultoría en Sistemas SA de CV