-
Problem report
-
Resolution: Unresolved
-
Trivial
-
None
-
None
-
Sprint candidates
It was originally fixed in ZBXNEXT-9397 but broken by ZBXNEXT-7048
1911416:20250804:171712.415 received configuration data from server at "127.0.0.1", datalen 387156 1911416:20250804:171722.916 received configuration data from server at "127.0.0.1", datalen 570 1911416:20250804:171733.037 received configuration data from server at "127.0.0.1", datalen 570 1911416:20250804:171743.151 received configuration data from server at "127.0.0.1", datalen 570 1911416:20250804:171753.270 received configuration data from server at "127.0.0.1", datalen 570 1911416:20250804:171803.375 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171813.478 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171823.589 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171833.705 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171843.806 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171853.903 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171904.006 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171914.108 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171924.194 received configuration data from server at "127.0.0.1", datalen 571 1911416:20250804:171934.269 received configuration data from server at "127.0.0.1", datalen 571
- caused by
-
ZBXNEXT-7048 Convert "config" table to key-value format
-
- Closed
-