Moesif is an AI-powered API insights platform for:
- API Debugging
- API Monitoring
- API Analytics
Support for REST, GraphQL, Ethereum Web3, JSON-RPC, SOAP, & more
Get real-time visibility into your (or your 3rd party) live API traffic saving you debug time.
- Understand how your customers actually use your API
- Root cause issues quickly with ML powered features like Smart Diff
- Get Slack and PagerDuty alerts of anomalous API behavior that pings tests don’t catch
Terminology
plugin: a plugin executing actions inside Kong before or after a request has been proxied to the upstream API.Service: the Kong entity representing an external upstream API or microservice.Route: the Kong entity representing a way to map downstream requests to upstream services.Consumer: an entity that makes requests for Kong to proxy; it represents either a user or an external service.Credential: a unique string associated with a Consumer, also referred to as an API key.Upstream service: this refers to your own API/service sitting behind Kong, to which client requests are forwarded.API: a legacy entity used to represent your upstream services. Deprecated in favor of Services since CE 0.13.0 and EE 0.32.
Configuration
Enabling the plugin on a Service
Configure this plugin on a Service by making the following request:
$ curl -X POST http://kong:8001/services/{service}/plugins \
--data "name=kong-plugin-moesif" \
--data "config.application_id=MY_MOESIF_APPLICATION_ID"
{service} is the id or name of the Service that this plugin configuration will target.
Enabling the plugin on a Route
Configure this plugin on a Route with:
$ curl -X POST http://kong:8001/routes/{route}/plugins \
--data "name=kong-plugin-moesif" \
--data "config.application_id=MY_MOESIF_APPLICATION_ID"
{route} is the id or name of the Route that this plugin configuration will target.
Enabling the plugin on a Consumer
Configure this plugin on a Consumer with:
$ curl -X POST http://kong:8001/consumers/{consumer}/plugins \
--data "name=kong-plugin-moesif" \
--data "config.application_id=MY_MOESIF_APPLICATION_ID"
{consumer} is the id or username of the Consumer that this plugin configuration will target.
You can combine consumer.id and service.id in the same request, to further narrow the scope of the plugin.
Enabling the plugin on an API
If you are using an older version of Kong with the legacy API entity (deprecated in favor of Services since CE 0.13.0 and EE 0.32.), you can configure this plugin on top of such an API by making the following request:
$ curl -X POST http://kong:8001/apis/{api}/plugins \
--data "name=kong-plugin-moesif" \
--data "config.application_id=MY_MOESIF_APPLICATION_ID"
api: either id or name of the API that this plugin configuration will target.
Global plugins
A plugin which is not associated to any Service, Route, or Consumer (or API, if you are using an older version of Kong) is considered "global", and will be run on every request. Read the Plugin Reference and the Plugin Precedence sections for more information.
Plugins can be configured using the http://kong:8001/plugins/ endpoint.
Parameters
Here's a list of all the parameters which can be used in this plugin's configuration:
| Form Parameter | Description |
|---|---|
name | The name of the plugin to use, in this case kong-plugin-moesif |
service.id | The ID of the Service the plugin targets. |
route.id | The ID of the Route the plugin targets. |
consumer.id | The ID of the Consumer the plugin targets. |
enableddefault value: true | Whether this plugin will be applied. |
api_id | The ID of the API the plugin targets. Note: The API Entity is deprecated in favor of Services since CE 0.13.0 and EE 0.32. |
config.application_id
|
The Moesif application token provided to you by Moesif. |
config.api_endpoint
optional default value:
|
URL for the Moesif API. |
config.timeout
optional default value:
|
An optional timeout in milliseconds when sending data to Moesif. |
config.keepalive
optional default value:
|
An optional value in milliseconds that defines for how long an idle connection will live before being closed. |
config.api_version
optional default value:
|
An optional API Version you want to tag this request with |
config.disable_capture_request_body
optional default value:
|
An option to disable logging of request body |
config.disable_capture_response_body
optional default value:
|
An option to disable logging of response body |
config.request_masks
optional default value:
|
An option to mask a specific request body field |
config.response_masks
optional default value:
|
An option to mask a specific response body field |
How it works
When enabled, this plugin will capture API requests and responses and log to Moesif API Insights for easy inspecting and real-time debugging of your API traffic.
Moesif natively supports REST, GraphQL, Ethereum Web3, SOAP, JSON-RPC, and more.
How to install
The .rock file is a self contained package that can be installed locally or from a remote server.
If the luarocks utility is installed in your system (this is likely the case if you used one of the official installation packages), you can install the ‘rock’ in your LuaRocks tree (a directory in which LuaRocks installs Lua modules).
It can be installed from luarocks repository by doing:
luarocks install --server=http://luarocks.org/manifests/moesif kong-plugin-moesif
Kong process errors
This logging plugin will only log HTTP request and response data. If you are looking for the Kong process error file (which is the nginx error file), then you can find it at the following path: