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
On which environment your Kong instance is running?
Kubernetes
Plugin Configuration
apiVersion: configuration.konghq.com/v1
config:
agent_host: datadog.ns.svc.cluster.local
environment: prod
service_name: kong
static_tags:
name: service
value: service-name
trace_agent_port: 8126
kind: KongPlugin
What happened?
We started with this latest version of the plugin, seems like this caused CPU spike over time.
Please see the screenshot below, this caused increased latencies in the server causing application timeouts eventually and we had setup a restart cron every 30 minutes as a workaround. So, if you see the graph it rapidly increases and after 30 min it drops down. We tried different plugins and finally found this opentelemetry plugin as the savior here. After switching apm to opentelemetry, the cpu usage stabilised. Please look into this. Below graph shows CPU usage with ddtrace and opentelemetry plugins.
The text was updated successfully, but these errors were encountered:
Kong Version
3.7.1
Plugin Version
0.2.1
On which environment your Kong instance is running?
Kubernetes
Plugin Configuration
apiVersion: configuration.konghq.com/v1
config:
agent_host: datadog.ns.svc.cluster.local
environment: prod
service_name: kong
static_tags:
value: service-name
trace_agent_port: 8126
kind: KongPlugin
What happened?
We started with this latest version of the plugin, seems like this caused CPU spike over time.
Please see the screenshot below, this caused increased latencies in the server causing application timeouts eventually and we had setup a restart cron every 30 minutes as a workaround. So, if you see the graph it rapidly increases and after 30 min it drops down. We tried different plugins and finally found this opentelemetry plugin as the savior here. After switching apm to opentelemetry, the cpu usage stabilised. Please look into this. Below graph shows CPU usage with ddtrace and opentelemetry plugins.
The text was updated successfully, but these errors were encountered: