By type
2022/03/02 03:10:51.371167 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/02 03:10:51.371227 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/02 03:10:51.371318 metrics.go:23: INFO Metrics logging every 30s
2022/03/02 03:10:51.371360 logstash.go:90: INFO Max Retries set to: 3
2022/03/02 03:10:51.371433 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/02 03:10:51.371572 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-gbvsw
2022/03/02 03:10:51.371802 async.go:63: INFO Flush Interval set to: 1s
2022/03/02 03:10:51.371822 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/02 03:10:51.372213 beat.go:221: INFO filebeat start running.
2022/03/02 03:10:51.372284 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/02 03:10:51.430579 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/02 03:10:51.430647 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/02 03:10:51.430719 crawler.go:38: INFO Loading Prospectors: 1
2022/03/02 03:10:51.430745 registrar.go:236: INFO Starting Registrar
2022/03/02 03:10:51.430885 sync.go:41: INFO Start sending events to output
2022/03/02 03:10:51.430902 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/02 03:10:51.431020 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/02 03:10:51.431032 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/02 03:10:51.430904 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/02 03:11:21.371680 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/02 03:11:31.433143 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/02 03:11:31.433300 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/02 03:11:31.433457 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/02 03:11:31.433523 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/02 03:11:31.433787 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/02 03:11:31.442204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:31.442238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:32.448206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:32.448243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:34.450999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:34.451031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:38.456930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:38.456958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:46.465678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:46.465712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:11:51.371621 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=35
2022/03/02 03:12:02.472379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:12:02.472416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:12:21.371912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:12:34.508935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:12:34.509012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:12:51.371594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:13:21.371561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:13:34.514235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:34.514353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:51.371584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:14:21.371584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:14:34.520169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:14:34.520330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:14:51.371635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:15:21.371648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:15:34.556555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:15:34.556600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:15:51.371661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:16:21.371569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:16:34.561957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:16:34.561984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:16:36.448118 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/02 03:16:51.371620 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/02 03:16:51.443201 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/02 03:16:51.443236 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/02 03:16:51.443321 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/02 03:17:21.371616 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/03/02 03:17:34.567904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:17:34.567935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:17:51.371613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:18:21.371623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:18:34.666911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:18:34.666974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:18:51.371613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:19:21.371675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:19:34.673778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:19:34.673802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:19:51.371645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:20:21.371625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:20:34.679453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:20:34.679488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:20:51.371574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:21:21.371561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:21:35.077399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:21:35.077434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:21:51.371587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:22:21.371536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:22:35.083769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:22:35.083797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:22:51.371648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:23:21.371708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:23:35.090433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:23:35.090473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:23:51.371751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:24:21.371724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:24:35.097357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:24:35.097404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:24:51.371644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:25:21.371620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:25:35.106009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:25:35.106037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:25:51.371762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:26:21.371571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:26:35.112805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:26:35.112836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:26:51.371536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:27:21.371599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:27:35.119344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:27:35.119381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:27:51.371657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:28:21.371624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:28:35.126569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:28:35.126621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:28:51.371603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:29:21.371578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:29:35.133458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:29:35.133494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:29:51.371594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:30:21.371677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:30:35.139641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:30:35.139678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:30:51.371587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:31:21.371673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:31:35.146150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:31:35.146183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:31:51.371645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:32:21.371585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:32:35.152841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:32:35.152884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:32:51.371578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:33:21.371619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:33:35.159299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:33:35.159339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:33:51.371605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:34:21.371613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:34:35.164936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:34:35.164970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:34:51.371560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:35:21.371625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:35:35.170922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:35:35.170958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:35:51.371689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:36:21.371597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:36:35.176562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:36:35.176616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:36:51.371594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:37:21.371619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:37:35.183057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:37:35.183090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:37:51.371566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:38:21.371584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:38:35.188948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:38:35.188981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:38:51.371605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:39:21.371571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:39:35.195915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:39:35.195943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:39:51.371553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:40:21.371557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:40:35.202118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:40:35.202157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:40:51.371559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:41:21.371633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:41:35.208278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:41:35.208427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:41:51.371567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:42:21.371561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:42:35.214767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:42:35.214796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:42:51.371617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:43:21.371643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:43:35.221684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:43:35.221717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:43:51.371596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:44:21.371649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:44:35.228373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:44:35.228406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:44:51.371601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:45:21.371649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:45:35.234013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:45:35.234042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:45:51.371637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:46:21.371552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:46:35.239971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:46:35.240000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:46:51.371589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:47:21.371603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:47:35.246240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:47:35.246278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:47:51.371611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:48:21.371585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:48:35.252119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:48:35.252156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:48:51.371586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:49:21.371559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:49:35.257976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:49:35.258004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:49:51.371593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:50:21.371580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:50:35.268158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:50:35.268195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:50:51.371582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:51:21.371556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:51:35.274115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:51:35.274157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:51:51.371518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:52:21.371559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:52:35.281835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:52:35.281867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:52:51.371537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:53:21.371618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:53:35.287828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:53:35.287973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:53:51.371618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:54:21.371634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:54:35.294685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:54:35.294720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:54:51.371643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:55:21.371608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:55:35.300881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:55:35.300913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:55:51.371623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:56:21.371584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:56:35.307241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:56:35.307284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:56:51.371657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:57:21.371600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:57:35.313063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:57:35.313097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:57:51.371588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:58:21.371595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:58:35.319771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:58:35.319807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:58:51.371622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:59:21.371636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:59:35.326341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:59:35.326382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:59:51.371601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:00:21.371581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:00:35.332980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:00:35.333014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:00:51.371610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:01:21.371573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:01:35.339525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:01:35.339593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:01:51.371674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:02:21.371637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:02:35.346262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:02:35.346293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:02:51.371620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:03:21.371569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:03:35.352696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:03:35.352725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:03:51.371565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:04:21.371565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:04:35.359479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:04:35.359511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:04:51.371535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:05:21.371583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:05:35.365684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:05:35.365716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:05:51.371591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:06:21.371561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:06:35.372027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:06:35.372079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:06:51.371550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:07:21.371581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:07:35.378471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:07:35.378496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:07:51.371677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:08:21.371586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:08:35.384359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:08:35.384399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:08:51.371554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:09:21.371604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:09:35.390818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:09:35.390849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:09:51.371642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:10:21.371567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:10:35.396886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:10:35.396916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:10:51.371542 metrics.go:34: INFO No non-zero metrics in the last 30s