Skip to content
Kong Logo | Kong Docs Logo
  • Docs
    • Explore the API Specs
      View all API Specs View all API Specs View all API Specs arrow image
    • Documentation
      API Specs
      Kong Gateway
      Lightweight, fast, and flexible cloud-native API gateway
      Kong Konnect
      Single platform for SaaS end-to-end connectivity
      Kong AI Gateway
      Multi-LLM AI Gateway for GenAI infrastructure
      Kong Mesh
      Enterprise service mesh based on Kuma and Envoy
      decK
      Helps manage Kong’s configuration in a declarative fashion
      Kong Ingress Controller
      Works inside a Kubernetes cluster and configures Kong to proxy traffic
      Kong Gateway Operator
      Manage your Kong deployments on Kubernetes using YAML Manifests
      Insomnia
      Collaborative API development platform
  • Plugin Hub
    • Explore the Plugin Hub
      View all plugins View all plugins View all plugins arrow image
    • Functionality View all View all arrow image
      View all plugins
      AI's icon
      AI
      Govern, secure, and control AI traffic with multi-LLM AI Gateway plugins
      Authentication's icon
      Authentication
      Protect your services with an authentication layer
      Security's icon
      Security
      Protect your services with additional security layer
      Traffic Control's icon
      Traffic Control
      Manage, throttle and restrict inbound and outbound API traffic
      Serverless's icon
      Serverless
      Invoke serverless functions in combination with other plugins
      Analytics & Monitoring's icon
      Analytics & Monitoring
      Visualize, inspect and monitor APIs and microservices traffic
      Transformations's icon
      Transformations
      Transform request and responses on the fly on Kong
      Logging's icon
      Logging
      Log request and response data using the best transport for your infrastructure
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
Kong Ingress Controller
3.2.x
  • Home icon
  • Kong Ingress Controller
  • Production
  • Observability
  • Prometheus Metrics
github-edit-pageEdit this page
report-issueReport an issue
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Kong AI Gateway
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Kong Gateway Operator
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • unreleased
  • 3.4.x (latest) (LTS)
  • 3.3.x
  • 3.2.x
  • 3.1.x
  • 3.0.x
  • 2.12.x (LTS)
  • 2.11.x
  • 2.10.x
  • 2.9.x
  • 2.8.x
  • 2.7.x
  • 2.6.x
  • 2.5.x (LTS)
  • Introduction
    • Overview
    • Kubernetes Gateway API
    • Version Support Policy
    • Changelog
  • How KIC Works
    • Architecture
    • Gateway API
    • Ingress
    • Custom Resources
    • Using Annotations
    • Admission Webhook
  • Get Started
    • Install KIC
    • Services and Routes
    • Rate Limiting
    • Proxy Caching
    • Key Authentication
  • KIC in Production
    • Deployment Topologies
      • Overview
      • Gateway Discovery
      • Database Backed
      • Traditional (sidecar)
    • Installation Methods
      • Helm
      • Kong Gateway Operator
    • Cloud Deployment
      • Azure
      • Amazon
      • Google
    • Enterprise License
    • Observability
      • Prometheus Metrics
      • Configuring Prometheus and Grafana
      • Kubernetes Events
    • Upgrading
      • Kong Gateway
      • Ingress Controller
  • Guides
    • Service Configuration
      • HTTP Service
      • TCP Service
      • UDP Service
      • gRPC Service
      • TLS
      • External Service
      • HTTPS Redirects
      • Multiple Backend Services
      • Configuring Gateway API resources across namespaces
      • Configuring Custom Kong Entities
    • Request Manipulation
      • Rewriting Hosts and Paths
      • Rewrite Annotation
      • Customizing load-balancing behavior
    • High Availability
      • KIC High Availability
      • Service Health Checks
      • Last Known Good Config
      • Fallback Configuration
    • Security
      • Kong Vaults
      • Using Workspaces
      • Preserving Client IP
      • Kubernetes Secrets in Plugins
    • Migrate
      • KongIngress to KongUpstreamPolicy
      • Migrating from Ingress to Gateway
      • Credential Type Labels
    • Customize Deployments
      • Images
    • Custom Ingress Class
      • Internal / External Traffic
  • Plugins
    • Custom Plugins
    • Cross-namespace Plugins
    • Authentication
    • ACL
    • Rate Limiting
    • mTLS
    • OIDC
  • Reference
    • Troubleshooting
    • Version Compatibility
    • Annotations
    • Configuration Options
    • Feature Gates
    • FAQ
      • Plugin Compatibility
      • Kong Router
      • Custom nginx.conf
    • Custom Resource Definitions
    • Resources Requiring Setting Ingress Class
    • Gateway API migration
    • Required Permissions for Installation
enterprise-switcher-icon Switch to OSS
On this pageOn this page
  • Prometheus metrics for configuration updates
    • ingress_controller_configuration_push_count
    • ingress_controller_translation_count
    • ingress_controller_configuration_push_duration_milliseconds
    • ingress_controller_configuration_push_broken_resource_count
    • ingress_controller_configuration_push_last_successful
    • ingress_controller_translation_broken_resource_count
    • ingress_controller_fallback_translation_count
    • ingress_controller_fallback_translation_broken_resource_count
    • ingress_controller_fallback_configuration_push_count
    • ingress_controller_fallback_configuration_push_last
    • ingress_controller_fallback_configuration_push_duration_milliseconds
    • ingress_controller_fallback_configuration_push_broken_resource_count
    • ingress_controller_fallback_cache_generation_duration_milliseconds
    • ingress_controller_processed_config_snapshot_cache_hit
    • ingress_controller_processed_config_snapshot_cache_miss
  • Low-level performance metrics
You are browsing documentation for an older version. See the latest documentation here.

Prometheus Metrics

Kong Ingress Controller, as well as Kong Gateway, both expose Prometheus metrics, under certain conditions:

  • Kong Ingress Controller version 2.0 and later, exposes Prometheus metrics for configuration updates.
  • Kong Gateway can expose Prometheus metrics for the requests that are served, if the Prometheus plugin is enabled. For more information about enabling plugin, see Using KongPlugin resource guide. You can also learn about specific integration details in the Integration with Prometheus and Grafana guide.

This is a reference for Integration with Prometheus and Grafana guide.

Prometheus metrics for configuration updates

ingress_controller_configuration_push_count

ingress_controller_configuration_push_count (type: counter) provides the number of successful or failed configuration pushes to Kong Gateway.

This metric provides these labels:

  • protocol describes the configuration protocol in use, which can be db-less or deck.
  • dataplane describes the data plane that was the target of configuration push.
  • success logs the status of configuration updates. If success is false, an unrecoverable error occurred. If success is true, the push succeeded with no errors.
  • failure_reason is populated if success="false". It describes the reason for the failure:
    • conflict: A configuration conflict that must be manually fixed.
    • network: A network related issues, such as Kong Gateway is offline.
    • other: Other issues, such as Kong Gateway reporting a non-conflict error.

ingress_controller_translation_count

ingress_controller_translation_count (type: counter) provides the number of translations from the Kubernetes state to the Kong Gateway state.

This metric provides the success label. success logs the status of configuration updates. If success is false, an unrecoverable error occurred. If success is true, the translation succeeded with no errors.

ingress_controller_configuration_push_duration_milliseconds

ingress_controller_configuration_push_duration_milliseconds (type: histogram) is the amount of time, in milliseconds, that it takes to push the configuration to Kong Gateway.

This metric provides these labels:

  • protocol describes the configuration protocol in use, which can be db-less or deck.
  • dataplane describes the data plane that was the target of configuration push.
  • success logs the status of configuration updates. If success is false, an unrecoverable error occurred. If success is true, the push succeeded with no errors.

ingress_controller_configuration_push_broken_resource_count

ingress_controller_configuration_push_broken_resource_count (type: counter) provides the number of resources not accepted by Kong Gateway when attempting to push configuration.

This metric provides these labels:

  • dataplane describes the data plane that was the target of the configuration push

ingress_controller_configuration_push_last_successful

ingress_controller_configuration_push_last_successful (type: gauge) provides the time of the last successful configuration push.

This metric provides these labels:

  • dataplane describes the data plane that was the target of the configuration push

ingress_controller_translation_broken_resource_count

ingress_controller_translation_broken_resource_count (type: gauge) provides the number of resources that the controller cannot successfully translate to Kong Gateway configuration.

ingress_controller_fallback_translation_count

ingress_controller_fallback_translation_count (type: counter) provides the count of translations from Kubernetes state to Kong state in fallback mode.

This metric provides the success label:

  • success logs the status of the translation. If success is false, an unrecoverable error occurs. If success is true, the translation succeeded without errors.

ingress_controller_fallback_translation_broken_resource_count

ingress_controller_fallback_translation_broken_resource_count (type: gauge) provides the number of resources that the controller cannot successfully translate to Kong configuration in fallback mode.

ingress_controller_fallback_configuration_push_count

ingress_controller_fallback_configuration_push_count (type: counter) provides the count of successful/failed fallback configuration pushes to Kong.

This metric provides these labels:

  • dataplane describes the data plane that was the target of the configuration push.
  • protocol describes the configuration protocol in use, which can be db-less or deck.
  • success logs the status of configuration updates. If success is false, an unrecoverable error occurs. If success is true, the push succeeded without errors.
  • failure_reason is populated if success="false". It describes the reason for the failure:
    • conflict: A configuration conflict that must be manually fixed.
    • network: A network related issue, such as Kong Gateway being offline.
    • other: Other issues, such as Kong Gateway reporting a non-conflict error.

ingress_controller_fallback_configuration_push_last

ingress_controller_fallback_configuration_push_last (type: gauge) provides the time of the last successful fallback configuration push.

This metric provides these labels:

  • dataplane describes the data plane that was the target of the configuration push.

ingress_controller_fallback_configuration_push_duration_milliseconds

ingress_controller_fallback_configuration_push_duration_milliseconds (type: histogram) provides the amount of time, in milliseconds, that it takes to push the fallback configuration to Kong.

This metric provides these labels:

  • dataplane describes the data plane that was the target of the configuration push.
  • protocol describes the configuration protocol in use, which can be db-less or deck.
  • success logs the status of configuration updates. If success is false, an unrecoverable error occurs. If success is true, the push succeeded without errors.

ingress_controller_fallback_configuration_push_broken_resource_count

ingress_controller_fallback_configuration_push_broken_resource_count (type: gauge) provides the number of resources not accepted by Kong when attempting to push the fallback configuration.

This metric provides these labels:

  • dataplane describes the data plane that was the target of the configuration push.

ingress_controller_fallback_cache_generation_duration_milliseconds

ingress_controller_fallback_cache_generation_duration_milliseconds (type: histogram) provides the amount of time, in milliseconds, that it takes to generate a fallback cache.

This metric provides the success label:

  • success logs the status of cache generation. If success is false, an unrecoverable error occurs. If success is true, the cache generation succeeded without errors.

ingress_controller_processed_config_snapshot_cache_hit

ingress_controller_processed_config_snapshot_cache_hit (type: counter) provides the count of times the controller hit the processed configuration snapshot cache and skipped generating a new one.

ingress_controller_processed_config_snapshot_cache_miss

ingress_controller_processed_config_snapshot_cache_miss (type: counter) provides the count of times the controller missed the processed configuration snapshot cache and had to generate a new one.

Low-level performance metrics

In addition, Kong Ingress Controller exposes more low-level performance metrics, but these may change from version to version because they are provided by underlying frameworks of Kong Ingress Controller.

A non-exhaustive list of these low-level metrics is described in the following:

  • Controller-runtime metrics
  • Workqueue metrics
Thank you for your feedback.
Was this page useful?
Too much on your plate? close cta icon
More features, less infrastructure with Kong Konnect. 1M requests per month for free.
Try it for Free
  • Kong
    Powering the API world

    Increase developer productivity, security, and performance at scale with the unified platform for API management, service mesh, and ingress controller.

    • Products
      • Kong Konnect
      • Kong Gateway Enterprise
      • Kong Gateway
      • Kong Mesh
      • Kong Ingress Controller
      • Kong Insomnia
      • Product Updates
      • Get Started
    • Documentation
      • Kong Konnect Docs
      • Kong Gateway Docs
      • Kong Mesh Docs
      • Kong Insomnia Docs
      • Kong Konnect Plugin Hub
    • Open Source
      • Kong Gateway
      • Kuma
      • Insomnia
      • Kong Community
    • Company
      • About Kong
      • Customers
      • Careers
      • Press
      • Events
      • Contact
  • Terms• Privacy• Trust and Compliance
© Kong Inc. 2025