By type
2022/03/22 03:24:27.228949 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/22 03:24:27.229041 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/22 03:24:27.229204 logstash.go:90: INFO Max Retries set to: 3
2022/03/22 03:24:27.229363 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/22 03:24:27.229487 metrics.go:23: INFO Metrics logging every 30s
2022/03/22 03:24:27.229581 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-rfv55
2022/03/22 03:24:27.230038 async.go:63: INFO Flush Interval set to: 1s
2022/03/22 03:24:27.230074 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/22 03:24:27.231649 beat.go:221: INFO filebeat start running.
2022/03/22 03:24:27.231951 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/22 03:24:27.251866 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/22 03:24:27.251987 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/22 03:24:27.252054 crawler.go:38: INFO Loading Prospectors: 1
2022/03/22 03:24:27.252187 registrar.go:236: INFO Starting Registrar
2022/03/22 03:24:27.252268 sync.go:41: INFO Start sending events to output
2022/03/22 03:24:27.252470 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/22 03:24:27.252928 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/22 03:24:27.253081 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/22 03:24:27.253128 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/22 03:24:57.230327 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/22 03:24:57.260315 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/22 03:24:57.260494 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/22 03:24:57.260834 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/22 03:24:57.260928 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/22 03:24:57.261008 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/22 03:24:57.320684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:57.320760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:58.327313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:58.327355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:00.338767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:00.338819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:04.415512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:04.415570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:12.467336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:12.467386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:27.230170 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=61
2022/03/22 03:25:28.527894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:28.527934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:57.230098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:26:00.602638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:26:00.602698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:26:27.232013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:26:57.230149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:27:00.677411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:27:00.677498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:27:27.230075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:27:57.230053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:28:00.791376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:28:00.791425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:28:27.229993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:28:57.229846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:29:00.817334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:29:00.817397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:29:27.229977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:29:57.230453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:30:00.905494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:30:00.905565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:30:02.357890 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/22 03:30:27.232547 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/22 03:30:57.230048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:31:00.937779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:31:00.937839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:31:27.230875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:31:57.230323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:32:00.991571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:32:00.991617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:32:27.230043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:32:57.230812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:33:01.051507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:33:01.051569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:33:27.230057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:33:57.230032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:34:01.177825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:34:01.177880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:34:27.231571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:34:57.229908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:35:01.347721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:35:01.350095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:35:27.229944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:35:57.229932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:36:01.404946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:36:01.405012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:36:27.230324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:36:57.230038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:37:01.424961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:37:01.425000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:37:27.230145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:37:57.230111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:38:01.465550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:38:01.465617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:38:27.235367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:38:57.230071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:39:01.529964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:39:01.530019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:39:27.229980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:39:57.230123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:40:01.563262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:40:01.563318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:40:27.230116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:40:57.229936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:41:01.593485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:41:01.593581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:41:27.230034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:41:57.229959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:42:03.642668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:42:03.642725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:42:27.230055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:42:57.230044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:43:03.671069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:43:03.671202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:43:27.230783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:43:57.230352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:44:03.773749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:44:03.773806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:44:27.230021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:44:57.230104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:45:03.795650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:45:03.795707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:45:27.231381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:45:57.229982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:46:03.818292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:46:03.818499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:46:27.229936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:46:57.230068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:47:03.846220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:47:03.846273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:47:27.229941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:47:57.230001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:48:03.888127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:48:03.888188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:48:27.229938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:48:57.230075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:49:03.923725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:49:03.923780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:49:27.229974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:49:57.230438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:50:03.977315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:50:03.977382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:50:27.230009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:50:57.230057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:51:03.998474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:51:03.998526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:51:27.229975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:51:57.229938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:52:04.031509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:52:04.031556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:52:27.229875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:52:57.239703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:53:04.069370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:53:04.069453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:53:27.229946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:53:57.229903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:54:04.092030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:54:04.092070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:54:27.229995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:54:57.230021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:55:04.121427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:55:04.121493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:55:27.230090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:55:57.230032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:56:04.172625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:56:04.172668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:56:27.230143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:56:57.230088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:57:04.201965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:57:04.202028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:57:27.229973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:57:57.230018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:58:04.254485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:58:04.254543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:58:27.229875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:58:57.229991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:59:04.303840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:59:04.303888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:59:27.229948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:59:57.229938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:00:04.334823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:00:04.334879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:00:27.230729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:00:57.230187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:01:04.404881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:01:04.404947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:01:27.230135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:01:57.229918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:02:04.426361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:02:04.426409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:02:27.229943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:02:57.230338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:03:04.460075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:03:04.460145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:03:27.229956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:03:57.229918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:04:04.537073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:04:04.537119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:04:27.230068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:04:57.229869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:05:04.615897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:05:04.615949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:05:27.229941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:05:57.230084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:06:04.642961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:06:04.643023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:06:27.229895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:06:57.230134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:07:04.684401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:07:04.684536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:07:27.230160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:07:57.230037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:08:04.824058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:08:04.824125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:08:27.230100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:08:57.230038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:09:04.892572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:09:04.892627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:09:27.230056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:09:57.229889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:10:04.934759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:10:04.934844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:10:27.230013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:10:57.232107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:11:04.974546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:11:04.974592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:11:27.230032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:11:57.230099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:12:05.000197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:12:05.000254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:12:27.230050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:12:57.229941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:13:05.027867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:13:05.027921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:13:27.230078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:13:57.229959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:14:05.060280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:14:05.060354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:14:27.229963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:14:57.229932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:15:05.094496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:15:05.094544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:15:27.230605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:15:57.230201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:16:05.120580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:16:05.120636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:16:27.230118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:16:57.229933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:17:05.143246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:17:05.143331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:17:27.230039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:17:57.230038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:18:05.187295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:18:05.187355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:18:27.230101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:18:57.229890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:19:05.213980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:19:05.214036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:19:27.229945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:19:57.229967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:20:05.275889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:20:05.275972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:20:27.229984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:20:57.230818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:21:05.325196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:21:05.325261 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:21:27.229930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:21:57.230131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:22:05.359933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:22:05.360163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:22:27.230408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:22:57.229919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:23:05.407893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:23:05.407949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:23:27.230275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:23:57.230098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:24:05.452509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:24:05.452565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:24:27.230011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:24:57.230038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:25:05.489779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:25:05.489878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:25:27.230046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:25:57.230061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:26:05.533156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:26:05.533609 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:26:27.230149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:26:57.238026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:27:05.561393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:27:05.561475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:27:27.230176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:27:57.230125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:28:05.599450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:28:05.599525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:28:27.247400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:28:57.229956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:29:05.629007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:29:05.629059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:29:27.229947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:29:57.230069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:30:05.656602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:30:05.656648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:30:27.230194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:30:57.230003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:31:05.685032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:31:05.685109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:31:27.229905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:31:57.230027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:32:05.708830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:32:05.708874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:32:27.230023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:32:57.230132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:33:05.741315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:33:05.741373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:33:27.229932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:33:57.235218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:34:05.772843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:34:05.772907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:34:27.230501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:34:57.230219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:35:05.797958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:35:05.798029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:35:27.230314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:35:57.230284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:36:05.847984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:36:05.848045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:36:27.229944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:36:57.229956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:37:05.888571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:37:05.888633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:37:27.229900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:37:57.230185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:38:05.949750 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:38:05.949841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:38:27.230075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:38:57.230023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:39:05.983970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:39:05.984028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:39:27.229982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:39:57.230141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:40:06.014626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:40:06.014808 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:40:27.229993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:40:57.230120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:41:06.076805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:41:06.077623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:41:27.229998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:41:57.229945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:42:06.101489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:42:06.101547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:42:27.230093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:42:57.229895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:43:06.153817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:43:06.153867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:43:27.230109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:43:57.230123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:44:06.186825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:44:06.186874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:44:27.229949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:44:57.230006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:45:06.239633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:45:06.239702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:45:27.230713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:45:57.230194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:46:06.271544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:46:06.271599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:46:27.229981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:46:57.232518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:47:06.348132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:47:06.348201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:47:27.229949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:47:57.229946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:48:06.382068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:48:06.382132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:48:27.230855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:48:57.230016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:49:06.414801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:49:06.414963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:49:27.230063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:49:57.230190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:50:06.450220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:50:06.450274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:50:27.230036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:50:57.229980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:51:06.533979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:51:06.534039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:51:27.229955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:51:57.229937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:52:06.562551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:52:06.562608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:52:27.230132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:52:57.229946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:53:06.607392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:53:06.607444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:53:27.230010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:53:57.229955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:54:06.643663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:54:06.643939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:54:27.229900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:54:57.230360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:55:06.692036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:55:06.692074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:55:27.230106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:55:57.230064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:56:06.756205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:56:06.756263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:56:27.229937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:56:57.229943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:57:06.798185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:57:06.798235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:57:27.230175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:57:57.229944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:58:06.860508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:58:06.860564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:58:27.230108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:58:57.230131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:59:06.890868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:59:06.890920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:59:27.229965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:59:57.229978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:00:06.936955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:00:06.937025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:00:27.229945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:00:57.230095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:01:06.971021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:01:06.971063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:01:27.229965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:01:57.230035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:02:07.022148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:02:07.022218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:02:27.229990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:02:57.229967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:03:07.084156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:03:07.084204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:03:27.230647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:03:57.230097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:04:07.125796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:04:07.125937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host