Configuring Events for Database Destination
You have to configure the database destination so that the event types and performance metrics data can be published to the configured database. You must externally manage the data housekeeping activities of the external databases that you have configured as destinations.
Note:
API Gateway functional alias has to be configured to receive the events in the Integration Server JDBC Pools configuration.
![*](icon_task_xpe.png)
To configure events for Database destination
1. Expand the menu options icon
, in the title bar, and select Administration. 2. Select Destinations.
3. Select Database to configure the event types for this destination.
4. In Event types, select the type of events that you want API Gateway to publish to the database.
The available event types are:
Error: Occurs each time an API invocation results in an error.
Lifecycle: Occurs each time
API Gateway is started or shut down.
Policy violation: Occurs each time an API invocation violates the policy enforcement that was set for the API.
5. Select Report performance data to publish performance metrics data.
6. In the Publish interval box, enter a time interval (in minutes) to specify how often API Gateway must publish performance metrics. Enter a value from 1 through 60. The default is 60 minutes.
7. In the Audit log data section, select the required management area for which the audit logs should be recorded in the Database destination.
Audit logs provide a record of system transactions, events, and occurrences in API Gateway. You can configure audit logging to show the following events:
Access profile management
Alias management
Analytics management
API management
Application management
Approval management
Group management
Package management
Plan management
Policy management
Promotion management
User managementNote:
By default, audit logging is disabled for all of the above-listed management areas in the Database destination.
8. Click Save.
Post-requisites:
After performing the database configurations, select Database as a Destination in the Policy Properties page for each policy, to receive the transaction event logs for the assigned policies.