By type
2022/02/05 03:07:42.424201 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/02/05 03:07:42.424274 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/05 03:07:42.424340 logstash.go:90: INFO Max Retries set to: 3
2022/02/05 03:07:42.424362 metrics.go:23: INFO Metrics logging every 30s
2022/02/05 03:07:42.424413 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/05 03:07:42.424517 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-xgxvh
2022/02/05 03:07:42.424717 async.go:63: INFO Flush Interval set to: 1s
2022/02/05 03:07:42.424738 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/05 03:07:42.425091 beat.go:221: INFO filebeat start running.
2022/02/05 03:07:42.425154 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/05 03:07:42.801820 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/05 03:07:42.801967 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/05 03:07:42.802032 crawler.go:38: INFO Loading Prospectors: 1
2022/02/05 03:07:42.802071 registrar.go:236: INFO Starting Registrar
2022/02/05 03:07:42.802252 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/05 03:07:42.802281 sync.go:41: INFO Start sending events to output
2022/02/05 03:07:42.802307 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/05 03:07:42.802473 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/05 03:07:42.802508 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/05 03:07:42.803342 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/02/05 03:07:42.803576 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/02/05 03:07:42.803639 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/02/05 03:07:42.803823 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/02/05 03:07:42.804029 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/02/05 03:07:47.831689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:07:47.831732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:07:48.839066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:07:48.839150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:07:50.844437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:07:50.844592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:07:54.852886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:07:54.853031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:08:02.862749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:08:02.862776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:08:12.424959 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=64 registrar.writes=1
2022/02/05 03:08:18.874482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:08:18.874553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:08:42.424713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:08:50.883747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:08:50.883798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:09:12.424701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:09:42.424708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:09:50.892672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:09:50.892721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:10:12.424696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:10:42.424922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:10:50.903765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:10:50.903796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:11:12.424721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:11:42.424899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:11:50.914368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:11:50.914424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:12.424990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:12:42.424705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:12:47.816808 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/02/05 03:12:47.816862 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/02/05 03:12:47.816846 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/02/05 03:12:47.816807 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/05 03:12:50.924940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:50.925085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:13:12.424683 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/02/05 03:13:23.836729 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/02/05 03:13:42.425196 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/02/05 03:13:50.934720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:13:50.934765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:14:12.424731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:14:42.424697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:14:50.942619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:14:50.942650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:15:12.424777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:15:42.424716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:15:50.951125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:15:50.951177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:16:12.424600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:16:42.424929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:16:50.965203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:16:50.965286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:17:12.424770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:17:42.424769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:17:50.973938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:17:50.973968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:18:12.424641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:18:42.424712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:18:50.984443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:18:50.984503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:19:12.424749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:19:42.424706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:19:50.992812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:19:50.992854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:20:12.424766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:20:42.424708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:20:51.008382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:20:51.008419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:21:12.424723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:21:42.424721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:21:51.018621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:21:51.018664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:22:12.424778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:22:42.424835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:22:51.028657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:22:51.028721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:23:12.424786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:23:42.424688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:23:51.040456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:23:51.040508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:24:12.424769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:24:42.424674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:24:51.048939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:24:51.049108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:25:12.424723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:25:42.424664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:25:51.058432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:25:51.058496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:26:12.424804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:26:42.424840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:26:51.066475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:26:51.066567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:27:12.424735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:27:42.424690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:27:51.077898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:27:51.077950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:28:12.424784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:28:42.424779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:28:51.086512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:28:51.086567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:29:12.424725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:29:42.424712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:29:51.095718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:29:51.095767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:30:12.424853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:30:42.424838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:30:51.106867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:30:51.106905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:31:12.424629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:31:42.424636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:31:51.115727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:31:51.115763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:32:12.424900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:32:42.424852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:32:51.127276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:32:51.127314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:33:12.424762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:33:42.424752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:33:51.135237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:33:51.135276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:34:12.424640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:34:42.424671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:34:51.143684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:34:51.143718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:35:12.424760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:35:42.424747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:35:51.155057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:35:51.155114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:36:12.424800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:36:42.424806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:36:51.166350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:36:51.166385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:37:12.424770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:37:42.424651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:37:51.180339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:37:51.180388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:38:12.424751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:38:42.424791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:38:51.190551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:38:51.190602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:39:12.424634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:39:42.424674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:39:51.203554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:39:51.203603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:40:12.424756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:40:42.424948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:40:51.213885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:40:51.213920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:41:12.424770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:41:42.424716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:41:51.225311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:41:51.225366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:42:12.424743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:42:42.424856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:42:51.236504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:42:51.236545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:43:12.424689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:43:42.424714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:43:51.246978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:43:51.247046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:44:12.424732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:44:42.424713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:44:51.257829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:44:51.257866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:45:12.424689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:45:42.424668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:45:51.266776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:45:51.266814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:46:12.424829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:46:42.424752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:46:51.277104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:46:51.277136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:47:12.424613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:47:42.424591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:47:51.287004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:47:51.287039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:48:12.424685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:48:42.424683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:48:51.295723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:48:51.295775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:49:12.424884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:49:42.424845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:49:51.305110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:49:51.305141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:50:12.424992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:50:42.424660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:50:51.313894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:50:51.313948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:51:12.424733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:51:42.424848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:51:51.322768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:51:51.322821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:52:12.424821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:52:42.424661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:52:51.332349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:52:51.332398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:53:12.424635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:53:42.424719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:53:51.341508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:53:51.341540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:54:12.424714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:54:42.424727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:54:51.351148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:54:51.351191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:55:12.424744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:55:42.424712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:55:51.361781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:55:51.361819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:56:12.424706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:56:42.424696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:56:51.373386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:56:51.373423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:57:12.424809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:57:42.424627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:57:51.386489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:57:51.386558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:58:12.424701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:58:42.424764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:58:51.395661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:58:51.395706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:59:12.424731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:59:42.424742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:59:51.405631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:59:51.405662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:00:12.424683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:00:42.424733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:00:51.417488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:00:51.417539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:01:12.424719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:01:42.424765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:01:51.428873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:01:51.428913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:02:12.424716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:02:42.424914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:02:51.438597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:02:51.438658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:03:12.424838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:03:42.424647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:03:51.450209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:03:51.450283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:04:12.424763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:04:42.424746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:04:51.465353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:04:51.465379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:05:12.424782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:05:42.424723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:05:51.476117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:05:51.476159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:06:12.424748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:06:42.424833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:06:51.486380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:06:51.486416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:07:12.424774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:07:42.424818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:07:51.497563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:07:51.497590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:08:12.424713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:08:42.424712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:08:51.506740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:08:51.506774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:09:12.424626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:09:42.424711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:09:51.515919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:09:51.516009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:10:12.424709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:10:42.424797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:10:51.527232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:10:51.527274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:11:12.424839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:11:42.424779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:11:51.535358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:11:51.535384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:12:12.424719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:12:42.424832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:12:51.544716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:12:51.544749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:13:12.424661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:13:42.424709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:13:51.553884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:13:51.553929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:14:12.424746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:14:42.424729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:14:51.563528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:14:51.563574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:15:12.424718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:15:42.424733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:15:51.569640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:15:51.569680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:16:12.424703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:16:42.424785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:16:51.579808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:16:51.579864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:17:12.425296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:17:42.424769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:17:51.588621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:17:51.588698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:18:12.424778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:18:42.424817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:18:51.599274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:18:51.599308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:19:12.424727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:19:42.424661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:19:51.609193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:19:51.609251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:20:12.424754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:20:42.424759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:20:51.618577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:20:51.618624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:21:12.424679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:21:42.424726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:21:51.626945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:21:51.626989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:22:12.424626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:22:42.424817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:22:51.636491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:22:51.636539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:23:12.424720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:23:42.424645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:23:51.646834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:23:51.646868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:24:12.424702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:24:42.424792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:24:51.657330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:24:51.657452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:25:12.424742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:25:42.424720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:25:51.666501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:25:51.666597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:26:12.424759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:26:42.424733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:26:51.677025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:26:51.677070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:27:12.424932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:27:42.424764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:27:51.686825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:27:51.686969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:28:12.424723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:28:42.424825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:28:51.697125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:28:51.697172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:29:12.424688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:29:42.424674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:29:51.708045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:29:51.708086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:30:12.424718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:30:42.424725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:30:51.717847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:30:51.717907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:31:12.424719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:31:42.426750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:31:51.727344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:31:51.727381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:32:12.424718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:32:42.424798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:32:51.737014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:32:51.737096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:33:12.424748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:33:42.424721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:33:51.747224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:33:51.747257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:34:12.424702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:34:42.424659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:34:51.757323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:34:51.757388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:35:12.424752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:35:42.424704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:35:51.767278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:35:51.767330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:36:12.424707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:36:42.424682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:36:51.777168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:36:51.777236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:37:12.424706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:37:42.424587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:37:51.786363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:37:51.786403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:38:12.424632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:38:42.424721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:38:51.794979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:38:51.795036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:39:12.424608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:39:42.424605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:39:51.803470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:39:51.803513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:40:12.424707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:40:42.424810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:40:51.813363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:40:51.813417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:41:12.424729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:41:42.424765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:41:51.822945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:41:51.822971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:42:12.425776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:42:42.424889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:42:51.832691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:42:51.832741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:43:12.424747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:43:42.424708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:43:51.842097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:43:51.842144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:44:12.424804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:44:42.424712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:44:51.851936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:44:51.852011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:45:12.424786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:45:42.424774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:45:51.860721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:45:51.860758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:46:12.424927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:46:42.424725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:46:51.870892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:46:51.870934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:47:12.424768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:47:42.424682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:47:51.880736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:47:51.880768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:48:12.424759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:48:42.424822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:48:51.891467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:48:51.891514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:49:12.424773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:49:42.424754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:49:51.901493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:49:51.901551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:50:12.424697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:50:42.424771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:50:51.912235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:50:51.912277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:51:12.424814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:51:42.424829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:51:51.921349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:51:51.921393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:52:12.424802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:52:42.424682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:52:51.931433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:52:51.931491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:53:12.424739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:53:42.424828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:53:51.940640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:53:51.940678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:54:12.424850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:54:42.424740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:54:51.950553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:54:51.950588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:55:12.424753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:55:42.424814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:55:51.959134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:55:51.959168 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:56:12.424718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:56:42.424926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:56:51.969963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:56:51.970006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:57:12.424776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:57:42.424739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:57:51.980392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:57:51.980449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:58:12.424775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:58:42.424764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:58:51.989557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:58:51.989610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:59:12.424649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:59:42.424620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:59:51.999447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:59:51.999492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:00:12.424710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:00:42.424800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:00:52.006873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:00:52.006920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:01:12.424661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:01:42.424695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:01:52.014561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:01:52.014595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:02:12.424687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:02:42.424749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:02:52.023273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:02:52.023332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:03:12.424599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:03:42.424711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:03:52.032464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:03:52.032498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:04:12.424765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:04:42.424833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:04:52.042383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:04:52.042416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:05:12.424763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:05:42.424758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:05:52.051266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:05:52.051327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:06:12.424752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:06:42.424799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:06:52.060454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:06:52.060504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:07:12.424697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:07:42.424616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:07:52.069657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:07:52.069707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:08:12.424764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:08:42.424907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:08:52.083533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:08:52.083580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:09:12.424760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:09:42.424608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:09:52.094280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:09:52.094319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:10:12.424778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:10:42.424764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:10:52.102797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:10:52.102832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:11:12.424660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:11:42.424686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:11:52.111677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:11:52.111712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:12:12.424761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:12:42.424775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:12:52.123139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:12:52.123285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host