By type
2022/01/15 03:11:03.135336 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/01/15 03:11:03.135374 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/15 03:11:03.135431 logstash.go:90: INFO Max Retries set to: 3
2022/01/15 03:11:03.135494 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/15 03:11:03.135533 metrics.go:23: INFO Metrics logging every 30s
2022/01/15 03:11:03.135583 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-prv7d
2022/01/15 03:11:03.135736 async.go:63: INFO Flush Interval set to: 1s
2022/01/15 03:11:03.135756 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/15 03:11:03.136126 beat.go:221: INFO filebeat start running.
2022/01/15 03:11:03.136177 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/15 03:11:03.187001 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/15 03:11:03.187064 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/15 03:11:03.187104 crawler.go:38: INFO Loading Prospectors: 1
2022/01/15 03:11:03.187285 registrar.go:236: INFO Starting Registrar
2022/01/15 03:11:03.187305 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/15 03:11:03.187452 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/15 03:11:03.187471 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/15 03:11:03.187381 sync.go:41: INFO Start sending events to output
2022/01/15 03:11:03.187528 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/15 03:11:03.188374 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/15 03:11:03.188435 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/15 03:11:03.188629 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/15 03:11:03.188663 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/15 03:11:03.188758 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/15 03:11:08.195922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:08.195944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:09.199957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:09.200135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:11.205082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:11.205134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:15.212633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:15.212678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:23.220268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:23.220304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:33.135945 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/01/15 03:11:39.234288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:11:39.234351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:12:03.136032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:12:11.242883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:12:11.242952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:12:33.135853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:13:03.136007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:13:11.252925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:13:11.252973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:13:33.135966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:14:03.136002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:14:11.263682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:14:11.263734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:14:33.136052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:15:03.135853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:15:11.270255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:15:11.270285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:15:33.136034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:16:03.136193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:16:08.199917 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/15 03:16:08.199976 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/15 03:16:08.200009 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/15 03:16:08.200017 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/15 03:16:11.280385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:16:11.280443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:16:33.135913 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/01/15 03:16:42.211369 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/01/15 03:17:03.135910 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/01/15 03:17:11.293547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:11.293577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:33.135904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:18:03.135850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:18:11.304710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:18:11.304760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:18:33.135921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:19:03.136023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:19:11.316450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:19:11.316485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:19:33.136025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:20:03.135932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:20:11.323937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:20:11.323961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:20:33.135850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:21:03.135952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:21:11.332975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:21:11.333045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:21:33.135919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:22:03.135809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:22:11.341881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:22:11.341917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:22:33.135774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:23:03.135840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:23:11.351448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:23:11.351489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:23:33.135918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:24:03.135783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:24:11.359965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:24:11.360064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:24:33.135875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:25:03.135822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:25:11.369784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:25:11.369821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:25:33.135889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:26:03.136084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:26:11.377941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:26:11.377996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:26:33.135866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:27:03.135898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:27:11.387495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:27:11.387522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:27:33.135945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:28:03.135886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:28:11.396571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:28:11.396621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:28:33.135930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:29:03.135782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:29:11.404173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:29:11.404239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:29:33.136230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:30:03.135841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:30:11.417452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:30:11.417492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:30:33.136012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:31:03.136204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:31:11.426961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:31:11.427002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:31:33.135947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:32:03.135912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:32:11.438168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:32:11.438222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:32:33.135849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:33:03.136069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:33:11.447631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:33:11.447677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:33:33.135884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:34:03.135829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:34:11.456636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:34:11.456666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:34:33.135929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:35:03.135825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:35:11.464295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:35:11.464332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:35:33.135936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:36:03.135918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:36:11.474700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:36:11.474749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:36:33.135760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:37:03.135927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:37:11.484917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:37:11.484969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:37:33.135785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:38:03.135942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:38:11.500238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:38:11.500291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:38:33.135923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:39:03.135973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:39:11.510238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:39:11.510326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:39:33.135974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:40:03.135941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:40:11.520280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:40:11.520335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:40:33.135915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:41:03.135821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:41:11.529427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:41:11.529486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:41:33.135784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:42:03.135957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:42:11.536629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:42:11.536651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:42:33.135968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:43:03.135968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:43:11.542902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:43:11.542943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:43:33.135820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:44:03.135784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:44:11.552014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:44:11.552065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:44:33.136105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:45:03.138649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:45:11.562647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:45:11.562697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:45:33.135974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:46:03.135838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:46:11.571691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:46:11.571728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:46:33.135968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:47:03.136013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:47:11.579814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:47:11.579844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:47:33.135988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:48:03.136116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:48:11.590251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:48:11.590294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:48:33.135937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:49:03.136028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:49:11.599173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:49:11.599208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:49:33.135945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:50:03.136095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:50:11.609117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:50:11.609169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:50:33.135933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:51:03.136020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:51:11.618375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:51:11.618439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:51:33.135935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:52:03.135926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:52:11.629094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:52:11.629137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:52:33.136153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:53:03.135857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:53:11.639603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:53:11.639818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:53:33.136078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:54:03.136006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:54:11.650267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:54:11.650316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:54:33.136031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:55:03.136026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:55:11.660007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:55:11.660069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:55:33.135917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:56:03.135907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:56:11.670205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:56:11.670252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:56:33.136105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:57:03.135945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:57:11.679156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:57:11.679188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:57:33.136008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:58:03.135855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:58:11.690251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:58:11.690316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:58:33.135830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:59:03.135871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:59:11.699166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:59:11.699192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:59:33.136109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:00:03.135971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:00:11.708522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:00:11.708569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:00:33.135865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:01:03.135920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:01:11.717105 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:01:11.717157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:01:33.135998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:02:03.135806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:02:11.725766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:02:11.725801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:02:33.135851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:03:03.135958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:03:11.735988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:03:11.736106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:03:33.135941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:04:03.136115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:04:11.744296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:04:11.744343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:04:33.135899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:05:03.135934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:05:11.753931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:05:11.753977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:05:33.136010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:06:03.135982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:06:11.763081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:06:11.763105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:06:33.135976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:07:03.136021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:07:11.772058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:07:11.772090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:07:33.135836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:08:03.136093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:08:11.783878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:08:11.783922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:08:33.135993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:09:03.135933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:09:11.793584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:09:11.793649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:09:33.136007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:10:03.135952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:10:11.803862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:10:11.803902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:10:33.135795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:11:03.136093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:11:11.813147 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:11:11.813193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:11:33.135973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:12:03.135826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:12:11.825873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:12:11.825927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:12:33.135941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:13:03.135898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:13:11.838884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:13:11.838934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:13:33.135936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:14:03.135964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:14:11.850393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:14:11.850445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:14:33.135887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:15:03.135975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:15:11.906195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:15:11.906286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:15:33.136016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:16:03.135956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:16:11.917780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:16:11.917805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:16:33.135982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:17:03.135912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:17:11.928985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:17:11.929013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:17:33.135890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:18:03.135819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:18:11.939337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:18:11.939388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:18:33.135918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:19:03.135976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:19:11.951122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:19:11.951159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:19:33.135995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:20:03.136130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:20:11.961328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:20:11.961371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:20:33.135888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:21:03.136003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:21:11.971767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:21:11.971819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:21:33.135801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:22:03.135983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:22:11.982374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:22:11.982422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:22:33.136031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:23:03.136009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:23:11.993398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:23:11.993430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:23:33.135855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:24:03.135954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:24:12.001576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:24:12.001603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:24:33.135954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:25:03.135986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:25:12.011553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:25:12.011603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:25:33.135972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:26:03.135991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:26:12.021132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:26:12.021198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:26:33.135907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:27:03.136007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:27:12.028760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:27:12.028819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:27:33.135843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:28:03.135967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:28:12.039093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:28:12.039128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:28:33.135999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:29:03.136143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:29:12.050327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:29:12.050376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:29:33.136037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:30:03.135845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:30:12.058015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:30:12.058039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:30:33.135920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:31:03.136238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:31:12.068864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:31:12.068914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:31:33.135849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:32:03.135908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:32:12.077830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:32:12.077886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:32:33.135987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:33:03.135968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:33:12.086638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:33:12.086673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:33:33.136072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:34:03.135874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:34:12.097674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:34:12.097724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:34:33.136026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:35:03.135988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:35:12.109269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:35:12.109316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:35:33.135921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:36:03.135825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:36:12.120135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:36:12.120171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:36:33.135985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:37:03.135831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:37:12.129358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:37:12.129504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:37:33.135962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:38:03.135967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:38:12.141667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:38:12.141710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:38:33.135799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:39:03.135914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:39:12.151628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:39:12.151664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:39:33.135973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:40:03.136040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:40:12.161486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:40:12.161530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:40:33.135854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:41:03.135931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:41:12.173536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:41:12.173574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:41:33.135834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:42:03.135981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:42:12.186330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:42:12.186384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:42:33.135842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:43:03.136007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:43:12.195450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:43:12.195510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:43:33.135948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:44:03.135980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:44:12.206129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:44:12.206177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:44:33.135879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:45:03.136165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:45:12.215804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:45:12.215841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:45:33.135818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:46:03.135863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:46:12.224201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:46:12.224329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:46:33.136023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:47:03.135757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:47:12.257907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:47:12.257932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:47:33.135817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:48:03.135922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:48:12.267154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:48:12.267187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:48:33.136062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:49:03.136291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:49:12.279366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:49:12.279406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:49:33.135827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:50:03.136032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:50:12.286582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:50:12.286631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:50:33.135899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:51:03.135971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:51:12.297829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:51:12.297875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:51:33.135826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:52:03.135940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:52:12.307415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:52:12.307467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:52:33.135938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:53:03.136121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:53:12.311076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:53:12.311209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:53:33.135786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:54:03.136037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:54:12.321806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:54:12.321835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:54:33.135871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:55:03.136055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:55:12.332725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:55:12.332783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:55:33.136001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:56:03.135941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:56:12.344627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:56:12.344656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:56:33.135865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:57:03.135956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:57:12.355068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:57:12.355112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:57:33.136093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:58:03.135801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:58:12.364006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:58:12.364037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:58:33.136082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:59:03.135843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:59:12.371876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:59:12.371910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:59:33.135805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:00:03.135910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:00:12.381243 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:00:12.381271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:00:33.135984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:01:03.135958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:01:12.389312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:01:12.389356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:01:33.136003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:02:03.135974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:02:12.399296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:02:12.399634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:02:33.135910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:03:03.135986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:03:12.409474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:03:12.409519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:03:33.135993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:04:03.136063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:04:12.421104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:04:12.421153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:04:33.136054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:05:03.135921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:05:12.428980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:05:12.429026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:05:33.135955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:06:03.136148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:06:12.436288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:06:12.436327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:06:33.135928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:07:03.135989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:07:12.444813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:07:12.445095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:07:33.135869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:08:03.135754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:08:12.456532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:08:12.456577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:08:33.135935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:09:03.135962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:09:12.467167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:09:12.467219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:09:33.135824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:10:03.135888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:10:12.477217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:10:12.477277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:10:33.135866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:11:03.135897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:11:12.488190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:11:12.488238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:11:33.135936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:12:03.135844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:12:12.498237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:12:12.498287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:12:33.135761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:13:03.135834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:13:12.507928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:13:12.507988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:13:33.136032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:14:03.135855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:14:12.516229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:14:12.516257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:14:33.135930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:15:03.135900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:15:12.526672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:15:12.526722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:15:33.135821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:16:03.135941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:16:12.534767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:16:12.534803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:16:33.135861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:17:03.135856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:17:12.546466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:17:12.546511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:17:33.135931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:18:03.136137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:18:12.555809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:18:12.555857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:18:33.135965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:19:03.136065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:19:12.565053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:19:12.565106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:19:33.135934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:20:03.135971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:20:12.576508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:20:12.576727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:20:33.136051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:21:03.135988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:21:12.586074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:21:12.586126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:21:33.135970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:22:03.136108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:22:12.595509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:22:12.595547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:22:33.136016 metrics.go:34: INFO No non-zero metrics in the last 30s