The Dynakube's specification specifies standalone Log monitoring, but no image repository/tag is configure

[henk_stobbe]

Good morning all!

I have put the message in the subject, can anybody hint me what Dynatrace is telling me?

Using this option,

I have modified the yaml so no pod is injected.

removing: logMonitoring: {} works.

Who can help me?

KR Henk

[henk_stobbe]

included yaml (tokens removed, names modified)

apiVersion: v1
data:
apiToken:
dataIngestToken:
metadata:
name: my-cluster
namespace: dynatrace
labels:
dynatrace.com/created-by: "dynatrace.kubernetes"
type: Opaque
---
apiVersion: dynatrace.com/v1beta5
kind: DynaKube
metadata:
name: my-name
namespace: dynatrace
labels:
dynatrace.com/created-by: "dynatrace.kubernetes"
annotations:
feature.dynatrace.com/k8s-app-enabled: "true"
# Link to api reference for further information: https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/reference/dynakube-parameters
spec:
apiUrl: https://environment.live.dynatrace.com/api
metadataEnrichment:
enabled: true
oneAgent:
cloudNativeFullStack:
matchExpressions:
- key: dt-monitoring/true
operator: Exists
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/master
operator: Exists
- effect: NoSchedule
key: node-role.kubernetes.io/control-plane
operator: Exists
activeGate:
capabilities:
- routing
- kubernetes-monitoring
- debugging
resources:
requests:
cpu: 500m
memory: 1.5Gi
limits:
cpu: 1000m
memory: 1.5Gi
templates:
otelCollector:
imageRef:
repository: public.ecr.aws/dynatrace/dynatrace-otel-collector
tag: latest
logMonitoring: {}
telemetryIngest:
protocols:
- jaeger
- otlp
- statsd
- zipkin
serviceName: telemetry-ingest

[AntonPineiro]

Hi,

You are selecting the most right column in this table.

You have a diagram here.

Best regards

[t_pawlak · Accepted solution]

Hi,
You are using Cloud Native Full Stack, which by design relies on OneAgent injection into Pods via the Dynatrace mutating webhook.

logMonitoring: {} enables Pod-level log monitoring, which requires OneAgent injection.
If your goal is “no pod is injected”, then:

• you cannot use Cloud Native Full Stack
• or you must disable all features that require injection

By removing logMonitoring: {}:

• the Operator stops trying to inject OneAgent
• the configuration is no longer conflicting

If you want zero injection, use Kubernetes platform monitoring only

[henk_stobbe]

Thanks for your reply,

For now customer really wants this to be included:

Infrastructure observability

    Host and process level visibility

    Network analysis

    Disk analysis

And no pods in the monitoring (yet)

I will remove:

feature.dynatrace.com/k8s-app-enabled: "true"

KR Henk