You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have prometheus global plugin setup on kong ingress controller running on k8s cluster
There are multiple paths defined inside rules (Example attached below)
When i try to get to metrics at each path level that is not available but metrics are available at route level
Is there an existing issue for this?
Current Behavior
We have prometheus global plugin setup on kong ingress controller running on k8s cluster
There are multiple paths defined inside rules (Example attached below)
When i try to get to metrics at each path level that is not available but metrics are available at route level
`kongHttpRoute:
enabled: true
routes:
- rules:
name: apis
annotations:
konghq.com/methods: "GET,POST,OPTIONS"
konghq.com/plugins: validate-customer-session, strip-prefix, prometheus
paths:
- type: RegularExpression
path: /service-name/api/v1/status
method: GET
- type: RegularExpression
path: /service-name/api/v1/health
method: POST
backendRefs: ads-service
port: 80
kongPlugin:
enabled: true
plugins:
- kongPluginName: validate-customer-session
config:
appendRiderId: false
authenticationBasePath: https://<domain_url>
authenticationValidateApiPath: /auth/v1/session-id/
- kongPluginName: strip-prefix
config:
count: 1
regex: /service-name
- kongPluginName: prometheus
config:
status_code_metrics: true
bandwidth_metrics: true
upstream_health_metrics: true
latency_metrics: true
per_consumer: true`
kong_http_requests_total{code="200", container="proxy", endpoint="status", exported_service="httproute..-apis.0", instance="", job="kic-gateway-proxy", namespace="infrastructure", pod="", route="httproute..-auth-apis.0.1", service="kic-gateway-proxy", source="service"}
PS : Our kong is already above 3.x.x.
Expected Behavior
Expecting metrics at Path like for above example
kong_http_requests_total should be available for both API Paths of above routes
How can this be achieved
Steps To Reproduce
Kong Ingress Controller version
> 3.x.x
Kubernetes version
Anything else?
Followed documentation for prometheus plugin with no luck
The text was updated successfully, but these errors were encountered: