Splunk Cloud Platform

Error while collecting GKE conainer logs using splunk otel

abhi04
Communicator

Hi Team,

 

I am using splunk otel to gather logs from GKE to splunk cloud platformand I see the below errors:

otel-collector 2025-02-25T23:29:46.515Z error reader/reader.go:214 failed to process token {"kind": "receiver", "name": "filelog", "data_type": "logs", "component": "fileconsumer", "path": "/var/log/pods/lxysdsdb/istio-proxy/0.log", "error": "failed to send entry after error: remove: field does not exist: attributes.time"}

How can I resolve this?

 

I am using the below helm template values, can someone point out to what can be changed? I am using cri and otel (not fluentd) to collect the logs.



# This is an example of using insecure configurations
clusterName: "${cluster_name}"

splunkPlatform:
endpoint: ${endpoint}
token: ${global_token}
index: ${index_name}
metricsIndex: "${index_name}_metrics"

insecureSkipVerify: true

logsEnabled: true
metricsEnabled: false
tracesEnabled: false

logsEngine: otel

cloudProvider: "gcp"

distribution: "gke"


agent:
enabled: true

ports:
otlp:
containerPort: 4317
hostPort: 4317
protocol: TCP
enabled_for: [traces, metrics, logs, profiling]
otlp-http:
containerPort: 4318
protocol: TCP
enabled_for: [metrics, traces, logs, profiling]

resources:
limits:
cpu: ${logging_cpu_requests}
memory: ${logging_memory_requests}

podLabels:
%{ for label, value in labels ~}
${label}: "${value}"
%{ endfor ~}

clusterReceiver:
enabled: false

logsCollection:

# Container logs collection
containers:
enabled: true

# Container runtime. One of `docker`, `cri-o`, or `containerd`
# Automatically discovered if not set.
containerRuntime: "${log_format_type}"

excludePaths:
%{ for path in exclude_path ~}
- ${path}
%{ endfor ~}
# Boolean for ingesting the agent's own log
excludeAgentLogs: true

 

Labels (1)
0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...