By type
2022/03/07 03:11:23.981722 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/07 03:11:23.981844 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/07 03:11:23.982288 logstash.go:90: INFO Max Retries set to: 3
2022/03/07 03:11:23.982451 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/07 03:11:23.982730 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-xzqqg
2022/03/07 03:11:23.983190 metrics.go:23: INFO Metrics logging every 30s
2022/03/07 03:11:23.983345 async.go:63: INFO Flush Interval set to: 1s
2022/03/07 03:11:23.983378 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/07 03:11:23.984391 beat.go:221: INFO filebeat start running.
2022/03/07 03:11:23.984584 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/07 03:11:24.001495 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/07 03:11:24.001664 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/07 03:11:24.001747 crawler.go:38: INFO Loading Prospectors: 1
2022/03/07 03:11:24.002143 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/07 03:11:24.002294 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/07 03:11:24.002327 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/07 03:11:24.002352 registrar.go:236: INFO Starting Registrar
2022/03/07 03:11:24.002442 sync.go:41: INFO Start sending events to output
2022/03/07 03:11:24.002493 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/07 03:11:53.984238 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/07 03:11:54.009218 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/07 03:11:54.009554 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/07 03:11:54.009718 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/07 03:11:54.010281 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/07 03:11:54.010702 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/07 03:11:59.030844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:11:59.030880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:00.038706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:00.038766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:02.049357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:02.049415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:06.094903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:06.094961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:14.111961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:14.112007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:23.983931 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=72
2022/03/07 03:12:30.137277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:30.137363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:53.984212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:13:02.160681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:13:02.160741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:13:23.983592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:13:53.983719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:14:02.274308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:14:02.274360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:14:23.986752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:14:53.983643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:15:02.306550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:15:02.306608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:15:23.983710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:15:53.988013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:16:02.332872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:16:02.332946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:16:23.983730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:16:53.985340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:16:59.049720 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/07 03:17:02.356713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:17:02.356763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:17:23.985459 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/07 03:17:53.983557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:18:02.420630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:18:02.420681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:18:23.984590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:18:53.983926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:19:02.450481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:19:02.450575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:19:23.983740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:19:53.983626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:20:02.479512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:20:02.479562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:20:23.983562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:20:53.983690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:21:02.512419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:21:02.512487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:21:23.983868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:21:53.983596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:22:02.570882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:22:02.570949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:22:23.990269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:22:53.984172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:23:02.625872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:23:02.625959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:23:23.986420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:23:53.983578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:24:02.719367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:24:02.719425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:24:23.984741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:24:53.983888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:25:02.839279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:25:02.839331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:25:23.999294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:25:53.983879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:26:02.882263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:26:02.882314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:26:23.983602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:26:53.987002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:27:02.920344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:27:02.931622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:27:23.989015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:27:53.984234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:28:02.978714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:28:02.978764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:28:23.983724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:28:53.984184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:29:03.051629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:29:03.051690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:29:23.985236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:29:53.986799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:30:03.119185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:30:03.119255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:30:23.983754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:30:53.983548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:31:03.159666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:31:03.159733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:31:23.984316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:31:53.987277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:32:03.194374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:32:03.194425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:32:23.983605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:32:53.984208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:33:03.230385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:33:03.230997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:33:23.983841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:33:53.983581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:34:03.281233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:34:03.281293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:34:23.983616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:34:53.988620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:35:03.347953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:35:03.348367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:35:23.983743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:35:53.985571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:36:03.383794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:36:03.383851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:36:23.983747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:36:53.983750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:37:03.451199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:37:03.451254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:37:23.983739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:37:53.984566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:38:03.474154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:38:03.474218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:38:23.985829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:38:53.983713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:39:03.501360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:39:03.501402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:39:23.983577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:39:53.983824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:40:03.523372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:40:03.523432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:40:23.985821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:40:53.985239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:41:03.604598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:41:03.604650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:41:23.983975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:41:53.983513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:42:03.639359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:42:03.639427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:42:23.983992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:42:53.983635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:43:03.674018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:43:03.674055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:43:23.983668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:43:53.983610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:44:03.709175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:44:03.709234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:44:23.983570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:44:53.984585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:45:03.738019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:45:03.738182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:45:23.983860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:45:53.988924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:46:03.764704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:46:03.764760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:46:23.983809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:46:53.985101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:47:03.818394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:47:03.818483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:47:23.983724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:47:53.984592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:48:03.850168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:48:03.850222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:48:23.984263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:48:53.983562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:49:03.877787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:49:03.877853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:49:23.983928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:49:53.985503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:50:03.933429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:50:03.933485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:50:23.983665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:50:53.983721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:51:03.966066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:51:03.966124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:51:23.983623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:51:53.986662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:52:04.005328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:52:04.005388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:52:23.983642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:52:53.985000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:53:04.046094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:53:04.046155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:53:23.983594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:53:53.983502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:54:04.098589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:54:04.098659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:54:23.984964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:54:53.983483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:55:04.117781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:55:04.117843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:55:23.985395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:55:53.983594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:56:04.148883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:56:04.148933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:56:23.987066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:56:53.983771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:57:04.183938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:57:04.183992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:57:23.986241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:57:53.984146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:58:04.214341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:04.214408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:23.983726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:58:53.983843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:59:04.240888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:04.240937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:23.983629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:59:53.983648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:00:04.267694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:00:04.267749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:00:23.983636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:00:53.983775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:01:04.306091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:01:04.306134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:01:23.983519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:01:53.983854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:02:04.328564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:02:04.328605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:02:23.983847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:02:53.983741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:03:04.342840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:03:04.342889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:03:23.983649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:03:53.984839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:04:04.376700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:04:04.376767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:04:23.984603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:04:53.983720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:05:04.413008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:05:04.413067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:05:23.994276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:05:53.983654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:06:04.422143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:06:04.422194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:06:23.983545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:06:53.983612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:07:04.465397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:07:04.465446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:07:23.983739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:07:53.983922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:08:04.477283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:08:04.477326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:08:23.984072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:08:53.983572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:09:04.493621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:09:04.493665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:09:23.983515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:09:53.983537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:10:04.506812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:10:04.506855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:10:23.983586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:10:53.990214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:11:04.523995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:11:04.524158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:11:23.984251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:11:53.983870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:12:04.533090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:12:04.533135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:12:23.983684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:12:53.984120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:13:04.542888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:13:04.542945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:13:23.983807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:13:53.983649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:14:04.568798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:14:04.568850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:14:23.983524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:14:53.988423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:15:04.609190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:15:04.609228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:15:23.984234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:15:53.983855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:16:04.621714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:16:04.621791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:16:23.984027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:16:53.983582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:17:04.633980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:17:04.634016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:17:23.983709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:17:53.984739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:18:04.663479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:18:04.663535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:18:23.984177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:18:53.984468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:19:04.688616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:19:04.688668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:19:23.984150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:19:53.983618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:20:04.697772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:20:04.697831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:20:23.983701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:20:53.983671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:21:04.726296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:21:04.726345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:21:23.994794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:21:53.983760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:22:04.747984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:22:04.748028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:22:23.984199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:22:53.983480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:23:04.772657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:23:04.772707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:23:23.983526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:23:53.983505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:24:04.788021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:24:04.788066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:24:23.983636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:24:53.983512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:25:04.799793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:25:04.799842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:25:23.983572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:25:53.984869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:26:04.831693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:26:04.831743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:26:23.994870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:26:53.983912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:27:04.862671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:27:04.862728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:27:23.984010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:27:53.984058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:28:04.915800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:28:04.915848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:28:23.983989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:28:53.983529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:29:04.939890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:29:04.939932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:29:23.983536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:29:53.983596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:30:04.972837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:30:04.972885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:30:23.983582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:30:53.983641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:31:04.984291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:31:04.984353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:31:23.983570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:31:53.983695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:32:04.998245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:32:04.998295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:32:23.983940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:32:53.983833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:33:05.011808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:33:05.011861 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:33:23.983580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:33:53.987276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:34:05.037508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:34:05.037573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:34:23.987618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:34:53.983947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:35:05.068617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:35:05.068675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:35:23.984560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:35:53.983798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:36:05.093991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:36:05.094050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:36:23.984457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:36:53.984111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:37:05.103778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:37:05.103815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:37:23.988398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:37:53.983778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:38:05.114799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:38:05.114842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:38:23.983547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:38:53.983727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:39:05.189290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:39:05.189336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:39:23.983719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:39:53.983623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:40:05.208068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:40:05.208111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:40:23.983629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:40:53.983791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:41:05.268220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:41:05.268279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:41:23.983660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:41:53.985109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:42:05.299450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:42:05.299517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:42:23.983576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:42:53.986922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:43:05.312156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:43:05.312320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:43:23.983788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:43:53.983636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:44:05.322357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:44:05.322419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:44:23.984329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:44:53.983630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:45:05.338735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:45:05.338783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:45:23.983702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:45:53.983606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:46:05.352859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:46:05.352915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:46:23.985193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:46:53.983510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:47:05.363199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:47:05.363256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:47:23.983643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:47:53.984327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:48:05.404700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:48:05.404754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:48:23.983600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:48:53.983733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:49:05.413244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:49:05.413289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:49:23.985870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:49:53.983680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:50:05.435302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:50:05.435359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:50:23.986588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:50:53.983586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:51:05.459869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:51:05.459944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:51:23.985930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:51:53.985543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:52:05.475885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:52:05.475949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:52:23.983968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:52:53.983623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:53:05.517178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:53:05.517227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:53:23.985539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:53:53.983724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:54:05.555075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:54:05.555130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:54:23.998365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:54:53.987372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:55:05.576714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:55:05.576766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:55:23.984315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:55:53.987077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:56:05.599063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:56:05.599286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:56:23.986400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:56:53.988173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:57:05.624958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:57:05.625015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:57:23.985418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:57:53.991558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:58:05.753152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:58:05.754031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:58:23.983814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:58:53.984599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:59:05.824514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:59:05.824585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:59:23.993875 metrics.go:34: INFO No non-zero metrics in the last 30s