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