-
Problem report
-
Resolution: Fixed
-
Trivial
-
6.2.6
-
production
-
Sprint 97 (Feb 2023), Sprint 98 (Mar 2023)
-
1
Steps to reproduce:
- Use the kubernetes integration helm chart installing zabbix agent and proxy
- Apply Kubernetes cluster state by HTTP and Kubernetes nodes by HTTP
- Start collecting metrics/items using
name: 'Kubernetes: Get state metrics'
type: SCRIPT
key: kube.state.metrics
value_type: TEXT
- Add some history and test : get state metrics.
Result:
See screenshot : the result is truncated at 65535 characters
Check Text data limits as per documentation https://www.zabbix.com/documentation/current/en/manual/config/items/item
So out of10480 lines (checked by port-forward svc/zabbix-agent-kube-state-metrics and getting the metrics) zabbix is ingesting only 643 lines of my metrics.
Resulting in data missing for a lot of items.
Saw this issue while testing/forcing a pending pvc. The trigger 'PVC discovery ... PVC is pending' was not issuing/provoking a problem as it had no data in its item.
Expected:
All items getting data values.