2022/01/14 03:28:07.107012 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/01/14 03:28:07.107068 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/14 03:28:07.107168 logstash.go:90: INFO Max Retries set to: 3
2022/01/14 03:28:07.107194 metrics.go:23: INFO Metrics logging every 30s
2022/01/14 03:28:07.107246 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/14 03:28:07.107396 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-t4vgx
2022/01/14 03:28:07.107601 async.go:63: INFO Flush Interval set to: 1s
2022/01/14 03:28:07.107626 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/14 03:28:07.108226 beat.go:221: INFO filebeat start running.
2022/01/14 03:28:07.108365 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/14 03:28:07.651148 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/14 03:28:07.651307 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/14 03:28:07.651333 crawler.go:38: INFO Loading Prospectors: 1
2022/01/14 03:28:07.651377 registrar.go:236: INFO Starting Registrar
2022/01/14 03:28:07.651519 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/14 03:28:07.651552 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/14 03:28:07.651531 sync.go:41: INFO Start sending events to output
2022/01/14 03:28:07.651598 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/14 03:28:07.651628 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/14 03:28:37.107702 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/01/14 03:28:47.655492 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/14 03:28:47.655613 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/14 03:28:47.655886 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/14 03:28:47.656047 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/14 03:28:47.656141 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/14 03:28:52.664272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:28:52.664317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:28:53.670457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:28:53.670518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:28:55.675316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:28:55.675349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:28:59.691415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:28:59.691457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:29:07.107771 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=54
2022/01/14 03:29:07.700904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:29:07.700937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:29:23.709837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:29:23.709879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:29:37.107535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:29:55.717642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:29:55.717692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:30:07.107606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:30:37.107459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:30:55.726381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:30:55.726431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:31:07.107450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:31:37.107632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:31:55.735354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:31:55.735398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:32:07.107534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:32:37.107675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:32:55.743989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:32:55.744024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:33:07.107526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:33:37.107663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:33:52.668352 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/14 03:33:55.753436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:33:55.753472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:34:07.107684 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/14 03:34:17.670152 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/14 03:34:17.670210 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/14 03:34:17.670278 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/14 03:34:37.107653 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/01/14 03:34:55.762015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:34:55.762082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:07.107787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:35:37.107721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:35:55.769112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:55.769159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:36:07.107622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:36:37.107475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:36:55.778514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:36:55.778550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:37:07.107572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:37:37.107559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:37:55.787831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:37:55.787908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:38:07.107566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:38:37.107631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:38:55.796648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:38:55.796696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:39:07.107709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:39:37.107562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:39:55.806366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:39:55.806439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:40:07.107594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:40:37.107496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:40:55.816622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:40:55.816673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:41:07.107590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:41:37.107555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:41:55.825683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:41:55.825726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:42:07.107593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:42:37.107608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:42:55.832636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:42:55.832675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:43:07.107642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:43:37.107618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:43:55.842061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:43:55.842099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:44:07.107583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:44:37.107547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:44:55.849429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:44:55.849487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:45:07.107580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:45:37.107893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:45:55.857955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:45:55.857998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:46:07.107579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:46:37.107621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:46:55.867931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:46:55.867977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:47:07.107517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:47:37.107518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:47:55.876329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:47:55.876364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:48:07.107503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:48:37.107613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:48:55.886372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:48:55.886436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:49:07.107609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:49:37.107659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:49:55.897118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:49:55.897166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:50:07.107607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:50:37.107646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:50:55.905886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:50:55.905919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:51:07.107594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:51:37.107477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:51:55.914881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:51:55.914920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:52:07.107575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:52:37.107634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:52:55.925244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:52:55.925298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:53:07.107705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:53:37.107572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:53:55.934918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:53:55.934967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:54:07.107577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:54:37.107475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:54:55.944024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:54:55.944055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:55:07.107541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:55:37.107570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:55:55.952621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:55:55.952663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:56:07.107536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:56:37.107507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:56:55.962302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:56:55.962337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:57:07.107678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:57:37.107711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:57:55.972471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:57:55.972521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:58:07.107700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:58:37.107625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:58:55.982591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:58:55.982619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:59:07.107715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:59:37.107617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:59:55.993299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:59:55.993336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:00:07.107724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:00:37.107504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:00:56.001857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:00:56.001921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:01:07.107469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:01:37.107488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:01:56.011944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:01:56.011978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:02:07.107544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:02:37.107513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:02:56.018567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:02:56.018611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:03:07.107465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:03:37.107554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:03:56.028499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:03:56.028540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:04:07.107740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:04:37.107614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:04:56.035432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:04:56.035524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:05:07.107574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:05:37.107509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:05:56.045233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:05:56.045257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:06:07.107619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:06:37.107710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:06:56.054547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:06:56.054590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:07:07.107502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:07:37.107612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:07:56.062998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:07:56.063058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:08:07.107774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:08:37.107546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:08:56.072567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:08:56.072600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:09:07.107461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:09:37.107599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:09:56.082248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:09:56.082292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:10:07.107682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:10:37.107680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:10:56.089177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:10:56.089204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:11:07.107613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:11:37.107583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:11:56.099064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:11:56.099178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:12:07.107695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:12:37.107727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:12:56.109485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:12:56.109536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:13:07.107785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:13:37.107692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:13:56.118447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:13:56.118480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:14:07.107704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:14:37.107632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:14:56.127503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:14:56.127549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:15:07.107695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:15:37.107515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:15:56.136081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:15:56.136148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:16:07.107664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:16:37.107591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:16:56.146423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:16:56.146475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:17:07.107541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:17:37.107603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:17:56.155392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:17:56.155438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:18:07.107571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:18:37.107615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:18:56.165634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:18:56.165689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:19:07.107583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:19:37.107492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:19:56.175285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:19:56.175344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:20:07.107527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:20:37.107615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:20:56.184126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:20:56.184194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:21:07.107678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:21:37.107632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:21:56.195121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:21:56.195174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:22:07.107710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:22:37.107680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:22:56.202840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:22:56.202992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:23:07.107586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:23:37.107701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:23:56.212034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:23:56.212101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:24:07.107702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:24:37.107736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:24:56.220637 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:24:56.220676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:25:07.107943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:25:37.107714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:25:56.230159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:25:56.230200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:26:07.107648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:26:37.107664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:26:56.240548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:26:56.240597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:27:07.107652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:27:37.107692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:27:56.251322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:27:56.251388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:28:07.107636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:28:37.107748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:28:56.261535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:28:56.261580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:29:07.107679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:29:37.107631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:29:56.272448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:29:56.272483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:30:07.107652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:30:37.107786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:30:56.282984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:30:56.283049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:31:07.107714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:31:37.107763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:31:56.293053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:31:56.293125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:32:07.107714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:32:37.107662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:32:56.300975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:32:56.301016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:33:07.107607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:33:37.107602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:33:56.309715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:33:56.309742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:34:07.107657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:34:37.107472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:34:56.319378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:34:56.319422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:35:07.107663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:35:37.107680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:35:56.327587 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:35:56.327630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:36:07.107432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:36:37.107576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:36:56.337014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:36:56.337051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:37:07.107668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:37:37.107445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:37:56.346626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:37:56.346666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:38:07.107452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:38:37.107430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:38:56.355253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:38:56.355326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:39:07.107668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:39:37.107711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:39:56.365162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:39:56.365229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:40:07.107633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:40:37.107559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:40:56.374054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:40:56.374094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:41:07.107806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:41:37.107481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:41:56.382227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:41:56.382253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:42:07.107544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:42:37.107577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:42:56.390790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:42:56.390828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:43:07.107458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:43:37.107625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:43:56.401445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:43:56.401498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:44:07.107702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:44:37.107516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:44:56.409907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:44:56.409937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:45:07.107761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:45:37.107662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:45:56.420329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:45:56.420382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:46:07.107623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:46:37.107644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:46:56.469027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:46:56.469074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:47:07.107887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:47:37.107595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:47:56.478699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:47:56.478771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:48:07.107564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:48:37.107528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:48:56.486919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:48:56.486967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:49:07.107653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:49:37.107614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:49:56.494109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:49:56.494161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:50:07.107683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:50:37.107682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:50:56.502114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:50:56.502179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:51:07.107690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:51:37.107714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:51:56.509712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:51:56.509744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:52:07.107817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:52:37.107606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:52:56.516784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:52:56.516815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:53:07.107625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:53:37.107739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:53:56.531651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:53:56.531680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:54:07.107709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:54:37.107545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:54:56.540508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:54:56.540544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:55:07.107726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:55:37.107644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:55:56.549066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:55:56.549101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:56:07.107606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:56:37.107494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:56:56.558014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:56:56.558060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:57:07.107586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:57:37.107591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:57:56.564345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:57:56.564373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:58:07.107598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:58:37.107612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:58:56.572850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:58:56.572907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:59:07.107515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:59:37.107477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:59:56.581435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:59:56.581463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:00:07.107620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:00:37.107696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:00:56.589626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:00:56.589664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:01:07.107667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:01:37.107679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:01:56.598843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:01:56.598878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:02:07.107575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:02:37.107582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:02:56.607579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:02:56.607606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:03:07.107732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:03:37.107549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:03:56.616259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:03:56.616321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:04:07.107897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:04:37.107553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:04:56.623567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:04:56.623623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:05:07.107731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:05:37.107602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:05:56.631341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:05:56.631380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:06:07.107665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:06:37.107611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:06:56.639459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:06:56.639497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:07:07.107702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:07:37.107804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:07:56.647069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:07:56.647120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:08:07.107516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:08:37.107651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:08:56.655714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:08:56.655762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:09:07.107607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:09:37.107505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:09:56.665041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:09:56.665088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:10:07.107541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:10:37.107625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:10:56.672771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:10:56.672801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:11:07.107788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:11:37.107592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:11:56.683916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:11:56.683961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:12:07.107626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:12:37.107752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:12:56.698116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:12:56.698383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:13:07.107752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:13:37.107584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:13:56.705718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:13:56.705760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:14:07.107664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:14:37.107578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:14:56.715910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:14:56.715958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:15:07.107697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:15:37.107631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:15:56.722651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:15:56.722675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:16:07.107694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:16:37.107708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:16:56.731632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:16:56.731680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:17:07.107720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:17:37.107934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:17:56.739812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:17:56.739840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:18:07.107686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:18:37.107616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:18:56.747519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:18:56.747561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:19:07.107631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:19:37.107756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:19:56.756593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:19:56.756644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:20:07.107599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:20:37.107617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:20:56.766038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:20:56.766100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:21:07.107596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:21:37.107642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:21:56.774484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:21:56.774523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:22:07.107712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:22:37.107579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:22:56.782710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:22:56.782748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:23:07.107698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:23:37.107613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:23:56.790860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:23:56.790905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:24:07.107689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:24:37.107494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:24:56.799228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:24:56.799407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:25:07.107710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:25:37.107824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:25:56.807333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:25:56.807380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:26:07.107630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:26:37.107566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:26:56.816528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:26:56.816578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:27:07.107601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:27:37.107659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:27:56.825496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:27:56.825549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:28:07.107679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:28:37.107513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:28:56.841348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:28:56.841381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:29:07.107471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:29:37.107590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:29:56.850847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:29:56.850882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:30:07.107616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:30:37.107901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:30:56.860499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:30:56.860535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:31:07.107636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:31:37.107704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:31:56.869643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:31:56.869686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:32:07.107646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:32:37.107620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:32:56.876939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:32:56.876972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:33:07.107672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:33:37.107674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:33:56.884669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:33:56.884706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:34:07.107654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:34:37.107589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:34:56.892850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:34:56.892882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:35:07.107705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:35:37.107461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:35:56.903018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:35:56.903066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:36:07.107707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:36:37.107621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:36:56.909695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:36:56.909728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:37:07.107635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:37:37.107619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:37:56.917481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:37:56.917652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:38:07.107525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:38:37.107459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:38:56.925707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:38:56.925734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:39:07.107667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:39:37.107668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:39:56.933074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:39:56.933100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:40:07.107591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:40:37.107583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:40:56.943715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:40:56.943756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:41:07.107669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:41:37.107679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:41:56.951766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:41:56.951819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:42:07.107650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:42:37.107539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:42:56.961086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:42:56.961130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:43:07.107720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:43:37.107454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:43:56.969379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:43:56.969412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:44:07.107608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:44:37.107555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:44:56.978295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:44:56.978347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:45:07.107589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:45:37.107794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:45:56.986844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:45:56.986894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:46:07.107555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:46:37.107637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:46:56.995742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:46:56.995771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:47:07.107657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:47:37.107563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:47:57.005520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:47:57.005554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:48:07.107661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:48:37.107685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:48:57.014538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:48:57.014588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:49:07.107655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:49:37.107639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:49:57.022625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:49:57.022661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:50:07.107595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:50:37.107517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:50:57.030234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:50:57.030262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:51:07.107584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:51:37.107507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:51:57.038556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:51:57.038600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:52:07.107536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:52:37.107667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:52:57.048157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:52:57.048202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:53:07.107729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:53:37.107635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:53:57.055074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:53:57.055111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:54:07.107586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:54:37.107571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:54:57.065022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:54:57.065073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:55:07.107650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:55:37.107649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:55:57.074531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:55:57.074581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:56:07.107578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:56:37.107728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:56:57.084229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:56:57.084256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:57:07.107579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:57:37.107609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:57:57.092930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:57:57.092988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:58:07.107614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:58:37.107529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:58:57.100469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:58:57.100512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:59:07.107624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:59:37.107609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:59:57.109177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:59:57.109226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:00:07.107678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:00:37.107716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:00:57.116899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:00:57.116934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:01:07.107637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:01:37.107668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:01:57.125986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:01:57.126062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:02:07.107698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:02:37.107518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:02:57.134721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:02:57.134747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:03:07.107522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:03:37.107560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:03:57.142604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:03:57.142655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:04:07.107641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:04:37.107527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:04:57.149437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:04:57.149461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:05:07.107658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:05:37.107711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:05:57.158497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:05:57.158550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:06:07.107664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:06:37.107500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:06:57.167359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:06:57.167392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:07:07.107560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:07:37.107588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:07:57.177146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:07:57.177216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:08:07.107607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:08:37.107639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:08:57.185916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:08:57.185971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:09:07.107802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:09:37.107775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:09:57.194095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:09:57.194167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:10:07.107596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:10:37.107596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:10:57.202511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:10:57.202559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:11:07.107508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:11:37.107776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:11:57.212723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:11:57.212773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:12:07.107576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:12:37.107574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:12:57.221175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:12:57.221227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:13:07.107615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:13:37.107552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:13:57.230159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:13:57.230277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:14:07.107629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:14:37.107633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:14:57.240597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:14:57.240628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:15:07.107588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:15:37.107655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:15:57.249609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:15:57.249649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:16:07.107501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:16:37.107585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:16:57.257973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:16:57.258030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:17:07.107651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:17:37.107617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:17:57.266935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:17:57.266993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:18:07.107594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:18:37.107526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:18:57.275498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:18:57.275547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:19:07.107648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:19:37.107520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:19:57.284313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:19:57.284362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:20:07.107732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:20:37.107614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:20:57.293874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:20:57.293924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:21:07.107634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:21:37.107601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:21:57.302884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:21:57.302933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:22:07.107605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:22:37.107717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:22:57.312744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:22:57.312793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:23:07.107632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:23:37.107750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:23:57.321901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:23:57.321942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:24:07.107674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:24:37.107534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:24:57.331582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:24:57.331616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:25:07.107659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:25:37.107495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:25:57.340935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:25:57.340964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:26:07.107573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:26:37.107695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:26:57.348205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:26:57.348244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:27:07.107618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:27:37.107682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:27:57.354726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:27:57.354760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:28:07.107583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:28:37.107777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:28:57.364292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:28:57.364351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:29:07.107638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:29:37.107676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:29:57.372422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:29:57.372473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:30:07.107595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:30:37.107576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:30:57.381253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:30:57.381304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:31:07.107655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:31:37.108366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:31:57.391049 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:31:57.391210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:32:07.107539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:32:37.107612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:32:57.402184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:32:57.402261 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:33:07.107669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:33:37.107572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:33:57.413603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:33:57.413654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:34:07.107721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:34:37.107651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:34:57.423549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:34:57.423573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:35:07.107691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:35:37.107590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:35:57.435149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:35:57.435184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:36:07.107441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:36:37.107632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:36:57.444338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:36:57.444375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:37:07.107727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:37:37.107725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:37:57.454871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:37:57.454920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:38:07.107621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:38:37.107631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:38:57.464334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:38:57.464380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:39:07.107570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:39:37.107559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:39:57.473928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:39:57.473955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:40:07.108036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:40:37.107484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:40:57.486781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:40:57.486821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:41:07.107487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:41:37.107574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:41:57.497386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:41:57.497440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:42:07.107836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:42:37.107572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:42:57.504321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:42:57.504352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:43:07.107522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:43:37.107563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:43:57.513521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:43:57.513558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:44:07.107717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:44:37.107783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:44:57.524033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:44:57.524072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:45:07.107675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:45:37.107556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:45:57.533168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:45:57.533285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:46:07.107520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:46:37.107750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:46:57.541784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:46:57.541811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:47:07.107643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:47:37.107772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:47:57.551421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:47:57.551623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:48:07.107637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:48:37.107577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:48:57.560518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:48:57.560571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:49:07.107598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:49:37.107705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:49:57.570217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:49:57.570281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:50:07.107665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:50:37.107590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:50:57.580321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:50:57.580449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:51:07.107600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:51:37.107535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:51:57.589260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:51:57.589624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:52:07.107655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:52:37.107491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:52:57.599529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:52:57.599579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:53:07.107565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:53:37.107524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:53:57.609545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:53:57.609597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:54:07.107602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:54:37.107615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:54:57.618542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:54:57.618607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:55:07.107583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:55:37.107484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:55:57.627544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:55:57.627610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:56:07.107571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:56:37.107501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:56:57.637132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:56:57.637202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:57:07.107538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:57:37.107610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:57:57.644847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:57:57.644887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:58:07.107522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:58:37.107536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:58:57.654201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:58:57.654265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:59:07.107574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:59:37.107531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:59:57.662052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:59:57.662098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:00:07.107480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:00:37.107484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:00:57.669603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:00:57.669642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:01:07.107626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:01:37.107580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:01:57.679431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:01:57.679472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:02:07.107577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:02:37.107759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:02:57.688999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:02:57.689043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:03:07.107459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:03:37.107470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:03:57.698642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:03:57.698769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:04:07.107642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:04:37.107665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:04:57.708129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:04:57.708162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:05:07.107599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:05:37.107628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:05:57.715205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:05:57.715232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:06:07.107548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:06:37.107676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:06:57.722456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:06:57.722491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:07:07.107627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:07:37.107669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:07:57.731581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:07:57.731628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:08:07.107605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:08:37.107587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:08:57.740848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:08:57.740890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:09:07.107744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:09:37.107582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:09:57.749135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:09:57.749183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:10:07.107573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:10:37.107531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:10:57.757763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:10:57.757800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:11:07.107542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:11:37.107562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:11:57.766200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:11:57.766236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:12:07.107564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:12:37.107558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:12:57.775730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:12:57.775784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:13:07.107590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:13:37.107473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:13:57.790329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:13:57.790374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:14:07.107592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:14:37.107829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:14:57.796434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:14:57.796472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:15:07.107652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:15:37.107626 metrics.go:34: INFO No non-zero metrics in the last 30s