2022/03/28 03:04:06.388324 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/03/28 03:04:06.388406 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/28 03:04:06.388542 logstash.go:90: INFO Max Retries set to: 3
2022/03/28 03:04:06.388657 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/28 03:04:06.389691 metrics.go:23: INFO Metrics logging every 30s
2022/03/28 03:04:06.389800 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-8nzhc
2022/03/28 03:04:06.390124 async.go:63: INFO Flush Interval set to: 1s
2022/03/28 03:04:06.390202 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/28 03:04:06.390880 beat.go:221: INFO filebeat start running.
2022/03/28 03:04:06.390969 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/28 03:04:06.395848 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/28 03:04:06.395938 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/28 03:04:06.395975 crawler.go:38: INFO Loading Prospectors: 1
2022/03/28 03:04:06.396184 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/28 03:04:06.396316 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/28 03:04:06.396344 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/28 03:04:06.396367 registrar.go:236: INFO Starting Registrar
2022/03/28 03:04:06.396445 sync.go:41: INFO Start sending events to output
2022/03/28 03:04:06.396491 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/28 03:04:26.399275 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/28 03:04:26.399518 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/28 03:04:26.399589 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/28 03:04:26.400062 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/28 03:04:26.400487 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/28 03:04:31.416681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:31.416771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:32.421991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:32.422049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:34.428277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:34.428356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:36.390134 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=64 registrar.writes=1
2022/03/28 03:04:38.437050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:38.437236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:46.447706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:04:46.447751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:02.465689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:02.465721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:06.390082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:05:34.486982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:34.487022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:36.390201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:06:06.390039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:06:34.505459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:06:34.505508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:06:36.390139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:07:06.390062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:07:34.524264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:07:34.524582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:07:36.390001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:08:06.390113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:08:34.542567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:08:34.542615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:08:36.390111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:09:06.390056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:09:31.411665 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:09:31.411694 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:09:31.411730 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:09:31.412095 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:09:34.559558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:09:34.559679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:09:36.389999 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/28 03:09:42.419853 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:10:06.390059 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/28 03:10:34.577386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:10:34.577436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:10:36.390134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:11:06.389968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:11:34.598276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:11:34.598317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:11:36.390013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:12:06.390474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:12:34.615325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:12:34.615367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:12:36.389976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:13:06.390053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:13:34.633327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:13:34.633365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:13:36.390041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:14:06.390108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:14:34.651771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:14:34.651807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:14:36.390100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:15:06.390213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:15:34.668732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:15:34.668783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:15:36.390016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:16:06.389962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:16:34.686517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:16:34.686561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:16:36.390057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:17:06.390044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:17:34.703599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:17:34.703634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:17:36.389946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:18:06.389978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:18:34.719886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:18:34.719925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:18:36.390146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:19:06.390236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:19:34.738092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:19:34.738130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:19:36.389977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:20:06.390083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:20:34.769000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:20:34.769053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:20:36.390134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:21:06.390042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:21:34.788599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:21:34.788667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:21:36.390199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:22:06.390881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:22:34.808096 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:22:34.808150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:22:36.390053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:06.390038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:34.826343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:23:34.826397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:23:36.390104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:06.389986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:34.850247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:24:34.850292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:24:36.390015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:06.390124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:34.867223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:25:34.867272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:25:36.390102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:06.390021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:34.884877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:26:34.884917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:26:36.389999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:27:06.390107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:27:34.900977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:27:34.901010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:27:36.390020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:06.389998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:34.920391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:28:34.920441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:28:36.390008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:06.390084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:34.939008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:29:34.939052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:29:36.390027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:06.390036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:34.955430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:30:34.955466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:30:36.389989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:06.390106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:34.973875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:31:34.973928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:31:36.389977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:06.390002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:34.990989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:32:34.991044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:32:36.389957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:06.390094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:35.008318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:33:35.008353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:33:36.389993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:06.390048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:35.025930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:34:35.025971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:34:36.390052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:06.390160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:35.044006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:35:35.044051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:35:36.390013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:06.390087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:35.063016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:36:35.063070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:36:36.390138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:06.390100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:35.081511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:37:35.081539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:37:36.390000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:06.390120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:35.099015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:38:35.099078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:38:36.390024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:06.390397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:35.115931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:39:35.115968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:39:36.390070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:06.390041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:35.134239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:40:35.134290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:40:36.389994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:06.390086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:35.153890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:41:35.153938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:41:36.390071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:06.390017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:35.169998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:42:35.170066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:42:36.390111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:06.390179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:35.188211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:43:35.188256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:43:36.389998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:44:06.390000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:44:35.204825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:44:35.204878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:44:36.390022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:45:06.390055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:45:35.223923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:45:35.223961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:45:36.390011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:46:06.390117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:46:35.240455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:46:35.240490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:46:36.389966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:47:06.390010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:47:35.257645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:47:35.257792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:47:36.390010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:48:06.389974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:48:35.278832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:48:35.278890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:48:36.390089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:06.390082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:35.301389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:49:35.301440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:49:36.390016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:50:06.390021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:50:35.308919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:35.308999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:36.390133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:51:06.390053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:51:35.327126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:51:35.327159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:51:36.390024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:52:06.390076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:52:35.344643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:52:35.344670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:52:36.390031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:53:06.390139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:53:35.362627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:53:35.362670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:53:36.390039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:06.390005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:35.379846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:54:35.379879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:54:36.389985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:55:06.390140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:55:35.397267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:55:35.397315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:55:36.390011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:56:06.389968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:56:35.414787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:56:35.414842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:56:36.389946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:57:06.390061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:57:35.432611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:57:35.432667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:57:36.390004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:58:06.389964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:58:35.450395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:58:35.450448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:58:36.390011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:59:06.390108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:59:35.466805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:59:35.466862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:59:36.390007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:00:06.389966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:00:35.486256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:00:35.486310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:00:36.389972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:01:06.390049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:01:35.503056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:01:35.503097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:01:36.390040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:02:06.389948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:02:35.520523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:02:35.520572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:02:36.390020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:03:06.390030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:03:35.541231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:03:35.541266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:03:36.390069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:04:06.390042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:04:35.559617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:04:35.559654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:04:36.390009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:05:06.389994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:05:35.576999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:05:35.577033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:05:36.390152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:06:06.390019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:06:35.593277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:06:35.593315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:06:36.390011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:07:06.390044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:07:35.609160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:07:35.609213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:07:36.390053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:08:06.390064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:08:35.625917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:08:35.625959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:08:36.389942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:09:06.390053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:09:35.645233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:09:35.645302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:09:36.390169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:10:06.390050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:10:35.662765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:10:35.662820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:10:36.390042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:11:06.390088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:11:35.686650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:11:35.686693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:11:36.390017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:12:06.390015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:12:35.705872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:12:35.705907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:12:36.389971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:13:06.390051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:13:35.729722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:13:35.729758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:13:36.389985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:14:06.389958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:14:35.748660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:14:35.748712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:14:36.390099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:15:06.390030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:15:35.766807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:15:35.766860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:15:36.390010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:16:06.390045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:16:35.785720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:16:35.785756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:16:36.390047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:17:06.390088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:17:35.807436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:17:35.807497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:17:36.389981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:18:06.389976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:18:35.825502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:18:35.825709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:18:36.390010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:19:06.390048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:19:35.842477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:19:35.842515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:19:36.389979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:20:06.390019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:20:35.859783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:20:35.859819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:20:36.389973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:21:06.390067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:21:35.885186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:21:35.885232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:21:36.389957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:22:06.390016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:22:35.902772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:22:35.902823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:22:36.389997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:23:06.390061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:23:35.921342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:23:35.921383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:23:36.390039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:24:06.390123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:24:35.939195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:24:35.939256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:24:36.389998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:25:06.390068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:25:35.956984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:25:35.957045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:25:36.389977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:26:06.389996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:26:35.974764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:26:35.974803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:26:36.389976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:27:06.390069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:27:35.992197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:27:35.992244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:27:36.389996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:28:06.389983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:28:36.007585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:28:36.007643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:28:36.389935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:29:06.390140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:29:36.025546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:29:36.025632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:29:36.389977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:30:06.390062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:30:36.044291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:30:36.044341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:30:36.390047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:31:06.390071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:31:36.064470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:31:36.064509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:31:36.390017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:32:06.389957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:32:36.080866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:32:36.080942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:32:36.390029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:33:06.390050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:33:36.097127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:33:36.097161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:33:36.389983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:34:06.390023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:34:36.115143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:34:36.115197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:34:36.390003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:35:06.389957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:35:36.134003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:35:36.134042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:35:36.390166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:36:06.390262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:36:36.150801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:36:36.150854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:36:36.390040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:37:06.390061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:37:36.170329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:37:36.170522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:37:36.390002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:38:06.390055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:38:36.189996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:38:36.190042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:38:36.390022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:39:06.390014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:39:36.209088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:39:36.209134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:39:36.390014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:40:06.389994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:40:36.226916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:40:36.226968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:40:36.390016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:41:06.389962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:41:36.246125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:41:36.246170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:41:36.390033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:42:06.389963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:42:36.266544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:42:36.266987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:42:36.389928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:43:06.390077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:43:36.286614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:43:36.286659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:43:36.389968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:44:06.390034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:44:36.304363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:44:36.304420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:44:36.390055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:45:06.389986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:45:36.322307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:45:36.322338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:45:36.390017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:46:06.390356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:46:36.339928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:46:36.339993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:46:36.390087 metrics.go:34: INFO No non-zero metrics in the last 30s