Ana içeriğe geç

Application Logs

Application Logs Tab

The fields used for operations and filtering on Application Logs are shown in the table below.

FieldDescription
StartEnables recording of application logs on API Proxy basis.
Environment FilterEnables filtering of application logs for the specified environment.
Time FilterEnables filtering of application logs for the specified date range.
Log LevelEnables filtering of records at the specified log level in application logs.
Search by Correlation IDEnables detailed search in application logs with the correlation ID defined by Apinizer for requests coming to API Proxy. Application logs for only the relevant request can be accessed with the correlation ID obtained from API Proxy Traffic logs.
Search by DetailEnables search in text fields of application logs.
Search by Stack TraceEnables search on exception text if an exception has occurred in application logs.
DownloadEnables downloading application logs as a single file. All logs belonging to the API Proxy can be downloaded with the "All" option, filtered logs can be downloaded with the "Search Results" option.
DeleteEnables deletion of application log records belonging to this API Proxy.
Note

This page can be used when a software error is suspected or when you want to investigate how the application behaves in the background.

Log Levels

The Log Levels tab lets you configure the logging verbosity of each Apinizer component on a class or package basis.

FieldDescription
Class/Package NameThe fully qualified class or package name the level applies to; the level is applied to every logger whose name starts with this value. The seeded ROOT and com.apinizer entries (which cannot be removed) provide the baseline levels for the whole application and the Apinizer codebase respectively.
Manager / Gateway Engine / Cache / Integration LevelThe log level (ALL, TRACE, DEBUG, INFO, WARN, ERROR, OFF) applied to the corresponding component for the given class or package.
Update AllApplies the selected levels to every existing entry at once.
Update / RemoveUpdates or removes a single existing entry.

A level change is delivered to the running Manager, Gateway Engine, and Cache components immediately, and each component also reloads its log level settings from the database when it restarts.

Note

For the Integration level to take effect, the API Integration (Task Flow) Module URL must be configured under General Settings. If it is not set, the level change for Integration is skipped while the other components are still updated.