mirror of
https://github.com/wahyd4/home-docker.git
synced 2026-08-09 04:15:52 +10:00
enable apm
This commit is contained in:
+19
-15
@@ -179,7 +179,8 @@ datadog:
|
||||
# datadog.apm.enabled -- Enable this to enable APM and tracing, on port 8126
|
||||
## ref: https://github.com/DataDog/docker-dd-agent#tracing-from-the-host
|
||||
portEnabled: true
|
||||
socketEnabled: true
|
||||
socketEnabled: false
|
||||
enabled: true
|
||||
|
||||
# datadog.apm.port -- Override the trace Agent port
|
||||
## Note: Make sure your client is sending to the same UDP port.
|
||||
@@ -811,7 +812,11 @@ agents:
|
||||
# <POD_ANNOTATION>: '[{"key": "<KEY>", "value": "<VALUE>"}]'
|
||||
|
||||
# agents.tolerations -- Allow the DaemonSet to schedule on tainted nodes (requires Kubernetes >= 1.6)
|
||||
tolerations: []
|
||||
tolerations:
|
||||
- key: "node"
|
||||
operator: "Equal"
|
||||
value: "special"
|
||||
effect: "NoSchedule"
|
||||
|
||||
# agents.nodeSelector -- Allow the DaemonSet to schedule on selected nodes
|
||||
## Ref: https://kubernetes.io/docs/user-guide/node-selection/
|
||||
@@ -846,7 +851,7 @@ agents:
|
||||
## ref: https://docs.datadoghq.com/agent/guide/agent-configuration-files/?tab=agentv6
|
||||
## ref: https://github.com/DataDog/datadog-agent/blob/master/pkg/config/config_template.yaml
|
||||
## Note the `agents.useConfigMap` needs to be set to `true` for this parameter to be taken into account.
|
||||
customAgentConfig: {}
|
||||
customAgentConfig:
|
||||
# # Autodiscovery for Kubernetes
|
||||
# listeners:
|
||||
# - name: kubelet
|
||||
@@ -857,11 +862,10 @@ agents:
|
||||
# - name: docker
|
||||
# polling: true
|
||||
#
|
||||
# # Enable APM by setting the DD_APM_ENABLED envvar to true, or override this configuration
|
||||
# apm_config:
|
||||
# enabled: false
|
||||
# apm_non_local_traffic: true
|
||||
#
|
||||
# Enable APM by setting the DD_APM_ENABLED envvar to true, or override this configuration
|
||||
apm_config:
|
||||
enabled: false
|
||||
apm_non_local_traffic: true
|
||||
# # Enable java cgroup handling. Only one of those options should be enabled,
|
||||
# # depending on the agent version you are using along that chart.
|
||||
#
|
||||
@@ -922,13 +926,13 @@ clusterChecksRunner:
|
||||
replicas: 2
|
||||
|
||||
# clusterChecksRunner.resources -- Datadog clusterchecks-agent resource requests and limits.
|
||||
resources: {}
|
||||
# requests:
|
||||
# cpu: 200m
|
||||
# memory: 500Mi
|
||||
# limits:
|
||||
# cpu: 200m
|
||||
# memory: 500Mi
|
||||
resources:
|
||||
# requests:
|
||||
# cpu: 200m
|
||||
# memory: 500Mi
|
||||
# limits:
|
||||
# cpu: 200m
|
||||
# memory: 500Mi
|
||||
|
||||
# clusterChecksRunner.affinity -- Allow the ClusterChecks Deployment to schedule using affinity rules.
|
||||
## By default, ClusterChecks Deployment Pods are forced to run on different Nodes.
|
||||
|
||||
Reference in New Issue
Block a user