Edit this page
Report an issueMonitor License Usage
Obtain information about your Kong Gateway database-backed deployment, including license usage and deployment information using the License Report module. Share this information with Kong to perform a health-check analysis of product utilization and overall deployment performance to ensure your organization is optimized with the best license and deployment plan for your needs.
How the license report module works:
- The license report module manually generates a report containing usage and deployment data by sending a request to an endpoint, as defined below.
- Share this report with your Kong representative to perform an analysis of your deployment.
What the license report module does not do:
- The license report module does not automatically generate a report or send any data to any Kong servers.
- The license report module does not track or generate any data other than the data that is returned in the response after you send a request to the endpoint.
Important: The license report functionality cannot be used in a DB-less deployment.
Generate a License Report
Run the license report module and share the output information with your Kong representative for a deployment analysis.
Prerequisites: You must have Admin privileges to generate a license report.
To generate a license report, from an HTTP client:
Report Structure
| Field | Description |
|---|---|
counters |
Counts the number of requests. • buckets: Counts the number of requests made in a given month. ∙ bucket: Year and month when the requests were processed. If the value in bucket is UNKNOWN, then the requests were processed before Kong Gateway 2.7.0.1. ∙ request_count: Number of requests processed in the given month and year. • total_requests: Number of requests processed in the buckets. i.e. total_requests is equivalent to adding up the request_count of each item in buckets. |
plugins_count |
Counts the number of plugins in use. • tiers: Separate counts by license tiers. ∙ free: Number of free plugins in use. ∙ enterprise: Number of enterprise plugins in use. ∙ custom: Number of custom plugins in use. • unique_route_lambdas: Number of awk-lambda plugin in use. Only counts in case of the plugin is defined on a service-less route level and have a unique function name. • unique_route_kafkas: Number of unique broker IPs listed in broker array across kafka-upstream plugin defined on a service-less route level. |
db_version |
The type and version of the datastore Kong Gateway is using. |
kong_version |
The version of the Kong Gateway instance. |
license |
Displays information about the current license running Kong Gateway instance. • license_expiration_date: The date current license expires. If no license is present, the field displays as 2017-7-20. • license_key: Current license key. If no license is present, the field displays as UNLICENSED. |
rbac_users |
The number of users registered with through RBAC. |
services_count |
The number of configured services in the Kong Gateway instance. |
routes_count |
The number of configured routes in the Kong Gateway instance. |
system_info |
Displays information about the system running Kong Gateway. • cores: Number of CPU cores on the node • hostname: Encrypted system hostname • uname: Operating system` |
deployment_info |
Displays information about the deployment running Kong Gateway. • type: Type of the deployment mode • connected_dp_count: Number of dataplanes across the cluster. If the deployment is not hybrid mode, the field is not displayed. |
timestamp |
Timestamp of the current response. |
checksum |
The checksum of the current report. |
workspaces_count |
The number of workspaces configured in the Kong Gateway instance. |
