API Traffic Log Settings

Incoming and outgoing message information to API Proxy defined on Apinizer is logged in Elasticsearch database according to message elements (header, parameter, body).

The regions where these logs are kept;

• Request from Client
• Request to Target
• Response from Target
• Response to Client

By default, logging of fields in all message zones of the project is active.

Logged fields can be restricted as needed or based on the resource consumption of the log server.

Project and environment based log setting is managed on this screen.

For the production environment, it is recommended to disable the logging of items belonging to the following environments.

• Request to Target
• Response from Target

If an API Proxy is running in a production environment, it means that all policies in API Proxy have been setup and tested and will no longer be developed.

Therefore, it is important not to write header, parameter and body data in order not to overgrow the data in the database.

Even all logging fields are closed if there is an error in the request, all log fields are recorded in the database.

Formdata requests are not logged in any way.

The picture below shows the log settings:

On this screen, API Proxy based log settings can be set.

In addition, if the integration settings are enabled, it can be adjusted which API Proxies' traffic records can be sent to these integration targets.

The picture below shows the dialog that opens when the Edit button is clicked:

The fields used for log settings are shown in the table below.