Kong APIGW on AWS EKS w/ Prometheus plugin

Questions
1

Hi Everyone,

We are following Creating Prometheus and Grafana :: Kong on AWS to add observability to the Kong APIGW via the Prometheus plugin, with latency metrics enabled (see attached monitor.yaml) on EKS Fargate. However, the latency metrics is missing from /metrics. Is there a way to enable latency metrics that we may be missing? Attached is our kong CP and kong DP helm values.

monitor.yaml

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: prometheus
  annotations:
    kubernetes.io/ingress.class: kong
  labels:
    global: "true"
config:
  per_consumer: "true"
  status_code_metrics: "true"
  latency_metrics: "true"
  bandwidth_metrics: "true"
plugin: prometheus

kong-cp helm values


env:
  database: postgres
  role: control_plane
  cluster_cert: /etc/secrets/kong-cluster-cert/tls.crt
  cluster_cert_key: /etc/secrets/kong-cluster-cert/tls.key
  pg_host: localhost
  pg_port: 5432
  pg_user: postgres
  pg_password: pass
  pg_database: kong
  kong_admin_password: kong
ingressController:
  enabled: true
  env:
    kong_admin_filter_tag: ingress_controller_default
    kong_admin_tls_skip_verify: true
    kong_admin_token: kong
    kong_admin_url: https://localhost:8444
    publish_service: kong/kong-kong-proxy
cluster:
  enabled: true
  tls:
    enabled: true
    servicePort: 8005
    containerPort: 8005
clustertelemetry:
  enabled: true
  tls:
    enabled: true
    servicePort: 8006
    containerPort: 8006
admin:
  enabled: true
  type: NodePort
  http:
    enabled: true
  tls:
    # containerPort: 8000
    overrideServiceTargetPort: 8001
  ingress:
    enabled: true
manager:
  type: LoadBalancer
  portal:
    enabled: true
secretVolumes:
  - kong-cluster-cert
postgresql:
  enabled: false
proxy:
  annotations:
    prometheus.io/port: "9542"
    prometheus.io/scrape: "true"
  enabled: true
  type: NodePort
  http:
    containerPort: 8080
    enabled: true
    hostPort: 80
extraObjects:
- apiVersion: configuration.konghq.com/v1
  kind: KongClusterPlugin
  metadata:
    name: prometheus
    annotations:
      kubernetes.io/ingress.class: kong
    labels:
      global: "true"  
  config:
    per_consumer: "true"
    status_code_metrics: "true"
    latency_metrics: "true"
    bandwidth_metrics: "true"
  plugin: prometheus
autoscaling:
  enabled: true
  minReplicas: 3
  maxReplicas: 10

kong-dp helm values

podAnnotations:
  kuma.io/gateway: enabled
  traffic.sidecar.istio.io/includeInboundPorts: ""
  prometheus.io/scrape: "true"
serviceMonitor:
  enabled: true
  interval: 10s
  namespace: prometheus
  # labels:
  #   foo: bar
  # targetLabels:
  #   - foo
autoscaling:
  enabled: true
  minReplicas: 2
  maxReplicas: 5
resources:
  limits:
   cpu: 2
   memory: 4G
  requests:
   cpu: 2
   memory: 4G
ingressController:
  enabled: false
env:
  role: data_plane
  prefix: /kong_prefix/
  cluster_cert: /etc/secrets/kong-cluster-cert/tls.crt
  cluster_cert_key: /etc/secrets/kong-cluster-cert/tls.key
  lua_ssl_trusted_certificate: /etc/secrets/kong-cluster-cert/tls.crt
  cluster_control_plane: kong-kong-cluster.kong.svc.cluster.local:8005
  cluster_telemetry_endpoint: kong-kong-clustertelemetry.kong.svc.cluster.local:8006
  status_listen: 0.0.0.0:8100
secretVolumes:
  - kong-cluster-cert
manager:
  enabled: false
portal:
  enabled: false
portalapi:
  enabled: false
proxy:
  annotations:
    prometheus.io/scrape: "true"
  type: NodePort
  tls:
    overrideServiceTargetPort: 8000
  ingress:
    enabled: true