Hello @agylpradipta
As simple as possible, Open
under Dynatrace operator
As per the hostmonitoring.yaml you can customize the monitoring configurations for the K8s entities.
apiVersion: dynatrace.com/v1beta2
kind: DynaKube
metadata:
name: dynakube
namespace: dynatrace
spec:
# Dynatrace apiUrl including the `/api` path at the end.
# For SaaS, set `ENVIRONMENTID` to your environment ID.
# For Managed, change the apiUrl address.
# For instructions on how to determine the environment ID and how to configure the apiUrl address, see https://{environmentid}.live.dynatrace.com/api
# Optional: Name of the secret holding the credentials required to connect to the Dynatrace tenant
# If unset, the name of this custom resource is used
#
# tokens: “”
# Optional: Disable certificate validation checks for installer download and API communication
# skipCertCheck: true
# Optional: Set custom proxy settings either directly or from a secret with the field ‘proxy’
# proxy:
# value: my-proxy-url.com
# valueFrom: name-of-my-proxy-secret
# Optional: Adds custom RootCAs from a configmap.
# Put the certificate under “certs” key within your configmap.
# Applies to Dynatrace Operator, OneAgent and ActiveGate.
# trustedCAs: name-of-my-ca-configmap
# Optional: Sets Network Zone for OneAgent and ActiveGate pods
# Make sure networkZones are enabled on your cluster before (see Get started with network zones — Dynatrace Docs)
#
# networkZone: name-of-my-network-zone
# Optional: Defines a custom pull secret in case you use a private registry when pulling images from the Dynatrace environment
# The secret has to be of type ‘kubernetes.io/dockerconfigjson’ (see Pull an Image from a Private Registry | Kubernetes)
#
# customPullSecret: “custom-pull-secret”
# Optional: If enabled, and if Istio is installed on the Kubernetes environment, the
# Operator will create the corresponding VirtualService and ServiceEntry objects to allow access
# to the Dynatrace cluster from agents or activeGates. Disabled by default.
#
# enableIstio: false
# Optional: Configuration for thresholding Dynatrace API requests in minutes. Default is 15 minutes.
#
# dynatraceApiRequestThreshold: 15
# Configuration for Metadata Enrichment.
#
metadataEnrichment:
# Optional: Enables or disables metadata enrichment
# Defaults to “true”
#
enabled: true
# The namespaces in which metadata enrichment should be injected into
# If unset, all namespace will be injected into
# For examples regarding namespaceSelectors, see Labels and Selectors | Kubernetes
#
# namespaceSelector:
# matchLabels:
# app: my-app
# matchExpressions:
# - key: app
# operator: In
# values: [my-frontend, my-backend, my-database]
# Configuration for OneAgent instances
#
oneAgent:
# Optional: Sets a host group for OneAgent.
#
# hostGroup: “”
# Enables host monitoring and changes its settings
# Cannot be used in conjunction with cloud-native fullstack monitoring, classic fullstack monitoring or application-only monitoring
#
hostMonitoring:
# Optional: If specified, indicates the OneAgent version to use
# Defaults to the configured version on your Dynatrace environment
# Available versions can be found using the UI or the Dynatrace API
# The version is expected to be provided in the semver format
# Example: <major>.<minor>.<release>.<timestamp>, e.g. 1.200.0.20240501-085142
#
# version: “”
# Optional: Sets the URI for the image containing the OneAgent installer used by the DaemonSet
# Defaults to the latest OneAgent image on the tenant’s registry
#
# image: “”
# Optional: Sets a node selector to control on which nodes the OneAgent will be deployed.
# For more information on node selectors, see Assign Pods to Nodes | Kubernetes
#
# nodeSelector: {}
# Optional: Sets the priority class assigned to the OneAgent Pods. No class is set by default.
# For more information on priority classes, see Pod Priority and Preemption | Kubernetes
#
# priorityClassName: priority-class
# Optional: Specifies tolerations to include with the OneAgent DaemonSet.
# For more information on tolerations, see Taints and Tolerations | Kubernetes
#
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/master
operator: Exists
- effect: NoSchedule
key: node-role.kubernetes.io/control-plane
operator: Exists
# Optional: Adds resource settings for OneAgent container
# Consumption of the OneAgent heavily depends on the workload to monitor
# The values should be adjusted according to the workload
#
# oneAgentResources:
# requests:
# cpu: 100m
# memory: 512Mi
# limits:
# cpu: 300m
# memory: 1.5Gi
# Optional: Enables or disables automatic updates of OneAgent pods
# By default, if a new version is available, the OneAgent pods are restarted to apply the update
# If set to “false”, this behavior is disabled
# Defaults to “true”
#
# autoUpdate: true
# Optional: Sets the DNS Policy for OneAgent pods
# Defaults to “ClusterFirstWithHostNet”
# For more information on DNS policies, see DNS for Services and Pods | Kubernetes
#
# dnsPolicy: “ClusterFirstWithHostNet”
# Optional: Adds custom labels to OneAgent pods
# Can be used to structure workloads
#
# labels:
# custom: label
# Optional: Adds custom annotations to OneAgent pods
#
# annotations:
# custom: annotations
# Optional: Adds custom environment variables to OneAgent pods
#
# env: []
# Optional: Adds custom arguments to the OneAgent installer
# For a list of available options, see Customize OneAgent installation on Linux — Dynatrace Docs
# For a list of the limitations for OneAgents in Docker, see Set up Dynatrace OneAgent as a Docker container — Dynatrace Docs
#
args:
- --set-monitoring-mode=infra-only
# Optional: The SecComp Profile that will be used by the OneAgent in
# order to run in secure computing mode.
#
# secCompProfile: “”
