Skip to content
|
Plugin Hub
github-edit-pageEdit this page
report-issueReport an issue
header icon

Basic config examples for Kong Splunk Log

By Optum

Basic configuration examples

The following examples provide some typical configurations for enabling the kong-splunk-log plugin on a service.

Make the following request:

curl -X POST http://localhost:8001/services/{serviceName|Id}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --data '
    {
  "name": "kong-splunk-log",
  "config": {
    "splunk_endpoint": "https://hec-splunk.company.com/services/collector",
    "splunk_access_token": "aaaaaaaa-bbbb-cccc-dddd-ffffffffffff",
    "method": "POST",
    "content_type": "application/json",
    "timeout": 10000,
    "retry_count": 5,
    "queue_size": 20,
    "flush_timeout": 30,
    "keepalive": 60000
  }
}
    '

Replace SERVICE_NAME|ID with the id or name of the service that this plugin configuration will target.

Make the following request, substituting your own access token, region, control plane ID, and service ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/services/{serviceId}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"kong-splunk-log","config":{"splunk_endpoint":"https://hec-splunk.company.com/services/collector","splunk_access_token":"aaaaaaaa-bbbb-cccc-dddd-ffffffffffff","method":"POST","content_type":"application/json","timeout":10000,"retry_count":5,"queue_size":20,"flush_timeout":30,"keepalive":60000}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

First, create a KongPlugin resource:

echo "
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: kong-splunk-log-example
plugin: kong-splunk-log
config:
  splunk_endpoint: https://hec-splunk.company.com/services/collector
  splunk_access_token: aaaaaaaa-bbbb-cccc-dddd-ffffffffffff
  method: POST
  content_type: application/json
  timeout: 10000
  retry_count: 5
  queue_size: 20
  flush_timeout: 30
  keepalive: 60000
" | kubectl apply -f -

Next, apply the KongPlugin resource to an ingress by annotating the service as follows:

kubectl annotate service SERVICE_NAME konghq.com/plugins=kong-splunk-log-example

Replace SERVICE_NAME with the name of the service that this plugin configuration will target. You can see your available ingresses by running kubectl get service.

Note: The KongPlugin resource only needs to be defined once and can be applied to any service, consumer, or route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

Add this section to your declarative configuration file:

plugins:
- name: kong-splunk-log
  service: SERVICE_NAME|ID
  config:
    splunk_endpoint: https://hec-splunk.company.com/services/collector
    splunk_access_token: aaaaaaaa-bbbb-cccc-dddd-ffffffffffff
    method: POST
    content_type: application/json
    timeout: 10000
    retry_count: 5
    queue_size: 20
    flush_timeout: 30
    keepalive: 60000

Replace SERVICE_NAME|ID with the id or name of the service that this plugin configuration will target.

The following examples provide some typical configurations for enabling the kong-splunk-log plugin on a route.

Make the following request:

curl -X POST http://localhost:8001/routes/{routeName|Id}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --data '
    {
  "name": "kong-splunk-log",
  "config": {
    "splunk_endpoint": "https://hec-splunk.company.com/services/collector",
    "splunk_access_token": "aaaaaaaa-bbbb-cccc-dddd-ffffffffffff",
    "method": "POST",
    "content_type": "application/json",
    "timeout": 10000,
    "retry_count": 5,
    "queue_size": 20,
    "flush_timeout": 30,
    "keepalive": 60000
  }
}
    '

Replace ROUTE_NAME|ID with the id or name of the route that this plugin configuration will target.

Make the following request, substituting your own access token, region, control plane ID, and route ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/routes/{routeId}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"kong-splunk-log","config":{"splunk_endpoint":"https://hec-splunk.company.com/services/collector","splunk_access_token":"aaaaaaaa-bbbb-cccc-dddd-ffffffffffff","method":"POST","content_type":"application/json","timeout":10000,"retry_count":5,"queue_size":20,"flush_timeout":30,"keepalive":60000}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

First, create a KongPlugin resource:

echo "
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: kong-splunk-log-example
plugin: kong-splunk-log
config:
  splunk_endpoint: https://hec-splunk.company.com/services/collector
  splunk_access_token: aaaaaaaa-bbbb-cccc-dddd-ffffffffffff
  method: POST
  content_type: application/json
  timeout: 10000
  retry_count: 5
  queue_size: 20
  flush_timeout: 30
  keepalive: 60000
" | kubectl apply -f -

Next, apply the KongPlugin resource to an ingress by annotating the ingress as follows:

kubectl annotate ingress INGRESS_NAME konghq.com/plugins=kong-splunk-log-example

Replace INGRESS_NAME with the name of the ingress that this plugin configuration will target. You can see your available ingresses by running kubectl get ingress.

Note: The KongPlugin resource only needs to be defined once and can be applied to any service, consumer, or route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

Add this section to your declarative configuration file:

plugins:
- name: kong-splunk-log
  route: ROUTE_NAME|ID
  config:
    splunk_endpoint: https://hec-splunk.company.com/services/collector
    splunk_access_token: aaaaaaaa-bbbb-cccc-dddd-ffffffffffff
    method: POST
    content_type: application/json
    timeout: 10000
    retry_count: 5
    queue_size: 20
    flush_timeout: 30
    keepalive: 60000

Replace ROUTE_NAME|ID with the id or name of the route that this plugin configuration will target.

A plugin which is not associated to any service, route, consumer, or consumer group is considered global, and will be run on every request.

  • In self-managed Kong Gateway Enterprise, the plugin applies to every entity in a given workspace.
  • In self-managed Kong Gateway (OSS), the plugin applies to your entire environment.
  • In Konnect, the plugin applies to every entity in a given control plane.

Read the Plugin Reference and the Plugin Precedence sections for more information.

The following examples provide some typical configurations for enabling the Kong Splunk Log plugin globally.

Make the following request:

curl -X POST http://localhost:8001/plugins/ \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --data '
    {
  "name": "kong-splunk-log",
  "config": {
    "splunk_endpoint": "https://hec-splunk.company.com/services/collector",
    "splunk_access_token": "aaaaaaaa-bbbb-cccc-dddd-ffffffffffff",
    "method": "POST",
    "content_type": "application/json",
    "timeout": 10000,
    "retry_count": 5,
    "queue_size": 20,
    "flush_timeout": 30,
    "keepalive": 60000
  }
}
    '

Make the following request, substituting your own access token, region, and control plane ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/plugins/ \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"kong-splunk-log","config":{"splunk_endpoint":"https://hec-splunk.company.com/services/collector","splunk_access_token":"aaaaaaaa-bbbb-cccc-dddd-ffffffffffff","method":"POST","content_type":"application/json","timeout":10000,"retry_count":5,"queue_size":20,"flush_timeout":30,"keepalive":60000}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

Create a KongClusterPlugin resource and label it as global:

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: <global-kong-splunk-log>
  annotations:
    kubernetes.io/ingress.class: kong
  labels:
    global: "true"
config:
  splunk_endpoint: https://hec-splunk.company.com/services/collector
  splunk_access_token: aaaaaaaa-bbbb-cccc-dddd-ffffffffffff
  method: POST
  content_type: application/json
  timeout: 10000
  retry_count: 5
  queue_size: 20
  flush_timeout: 30
  keepalive: 60000
plugin: kong-splunk-log

Add a plugins entry in the declarative configuration file:

plugins:
- name: kong-splunk-log
  config:
    splunk_endpoint: https://hec-splunk.company.com/services/collector
    splunk_access_token: aaaaaaaa-bbbb-cccc-dddd-ffffffffffff
    method: POST
    content_type: application/json
    timeout: 10000
    retry_count: 5
    queue_size: 20
    flush_timeout: 30
    keepalive: 60000