2022/03/05 03:11:13.196675 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/05 03:11:13.196719 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:11:13.196791 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:11:13.196853 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:11:13.196950 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-w7ctg
2022/03/05 03:11:13.197200 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:11:13.197224 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:11:13.197753 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:11:13.198094 beat.go:221: INFO filebeat start running.
2022/03/05 03:11:13.198273 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:11:13.201960 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:11:13.202023 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:11:13.202055 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:11:13.202235 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:11:13.202344 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/05 03:11:13.202371 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:11:13.202383 registrar.go:236: INFO Starting Registrar
2022/03/05 03:11:13.202410 sync.go:41: INFO Start sending events to output
2022/03/05 03:11:13.202439 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:11:33.205528 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/05 03:11:33.206297 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/05 03:11:33.206522 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/05 03:11:33.206884 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/05 03:11:33.207098 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/05 03:11:38.214443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:38.214600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:39.219597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:39.219650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:41.222697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:41.222852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:43.198186 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/03/05 03:11:45.238211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:45.238249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:53.249593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:11:53.249647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:09.262646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:09.262696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:13.198203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:12:41.272391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:41.272428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:43.198144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:13:13.198215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:13:41.289809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:13:41.289872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:13:43.198066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:14:13.198092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:14:41.299646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:14:41.299677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:14:43.198174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:15:13.198065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:15:41.307124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:15:41.307163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:15:43.198142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:16:13.198118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:16:38.214866 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:16:38.214948 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:16:38.215145 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:16:38.215288 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:16:41.320675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:16:41.320714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:16:43.198103 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/03/05 03:16:45.225798 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:17:13.198104 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/03/05 03:17:41.336177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:17:41.336210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:17:43.198113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:18:13.198054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:18:41.343956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:18:41.344013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:18:43.198077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:19:13.198116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:19:41.354331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:19:41.354377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:19:43.198028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:20:13.198095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:20:41.360874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:20:41.360905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:20:43.198101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:21:13.198063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:21:41.371533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:21:41.371586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:21:43.198098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:22:13.198155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:22:41.378246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:22:41.378279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:22:43.198120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:23:13.198125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:23:41.385318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:23:41.385364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:23:43.198127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:24:13.198069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:24:41.392629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:24:41.392837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:24:43.198076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:25:13.198034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:25:41.401086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:25:41.401119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:25:43.198059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:26:13.198082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:26:41.408453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:26:41.408488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:26:43.198104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:27:13.198166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:27:41.415616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:27:41.415659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:27:43.198157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:28:13.198156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:28:41.423093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:28:41.423123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:28:43.198180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:29:13.198192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:29:41.428858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:29:41.428893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:29:43.198064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:13.198084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:41.451409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:30:41.451480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:30:43.198074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:13.198099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:41.459854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:31:41.459895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:31:43.198053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:13.198105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:41.466795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:32:41.466834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:32:43.198182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:13.198115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:41.472717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:33:41.472851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:33:43.198230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:13.198068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:41.481118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:34:41.481177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:34:43.198096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:13.198283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:41.488733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:35:41.488776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:35:43.198151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:13.198406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:41.495518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:36:41.495663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:36:43.198072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:13.198130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:41.502415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:37:41.502454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:37:43.198107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:13.198143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:41.509681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:38:41.509721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:38:43.198041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:13.198048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:41.517021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:39:41.517064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:39:43.198053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:13.198155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:41.525309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:40:41.525373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:40:43.198247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:13.198090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:41.531931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:41:41.532060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:41:43.198164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:13.198153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:41.540292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:42:41.540344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:42:43.198178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:13.198184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:41.548460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:43:41.548500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:43:43.198096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:13.198067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:41.556689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:44:41.556741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:44:43.198068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:13.198371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:41.563793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:45:41.563830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:45:43.198132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:13.198176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:41.575224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:46:41.575311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:46:43.198145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:13.198190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:41.582444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:47:41.582507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:47:43.198162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:13.198054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:41.593599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:48:41.593641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:48:43.198131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:13.198096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:41.601076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:49:41.601125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:49:43.198243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:13.198163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:41.609035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:50:41.609065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:50:43.198167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:13.198078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:41.616068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:51:41.616111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:51:43.198110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:13.198159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:41.630728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:52:41.630757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:52:43.198249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:13.198122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:41.638438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:53:41.638660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:53:43.198099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:13.198112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:41.646161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:54:41.646209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:54:43.198185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:13.200893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:41.655123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:55:41.655177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:55:43.198063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:13.198060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:41.665757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:56:41.665795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:56:43.198144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:13.198133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:41.682128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:57:41.682165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:57:43.198048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:13.198120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:41.687268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:41.687303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:43.198128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:13.198064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:41.707307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:41.707364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:43.198108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:13.198177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:41.726985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:41.727078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:43.198103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:13.198042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:41.734626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:41.734662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:43.198129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:13.198144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:41.743146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:41.743189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:43.198156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:13.198051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:41.752802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:41.752839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:43.198133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:13.198043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:41.761055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:41.761111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:43.198218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:13.198227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:41.780111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:41.780270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:43.198140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:13.198037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:41.788686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:41.788737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:43.198066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:13.198155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:41.795308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:41.795521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:43.198106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:13.198112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:41.804020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:41.804146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:43.198122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:13.198095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:41.817947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:41.817982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:43.198077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:13.198044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:41.828180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:41.828216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:43.198190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:13.198111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:41.835768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:41.835813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:43.198110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:13.198203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:41.845167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:41.845202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:43.198067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:13.198014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:41.852645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:41.852693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:43.198138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:13.198134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:41.864230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:41.864260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:43.198087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:13.198032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:41.874520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:41.874561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:43.198107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:13.198049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:41.888711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:41.888749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:43.198046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:13.198293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:41.899926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:41.899961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:43.198496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:13.198119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:41.908894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:41.908943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:43.198047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:13.198178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:41.919917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:41.919955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:43.198213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:13.198113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:41.929330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:41.929378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:43.198072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:13.198184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:41.939209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:41.939356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:43.198117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:13.198058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:41.946386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:41.946447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:43.198160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:13.198061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:41.976926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:41.976965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:43.198116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:13.198129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:41.984777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:41.985022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:43.198080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:13.198106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:41.992931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:41.992992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:43.198158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:13.198103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:42.000615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:42.000650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:43.198108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:13.198110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:42.007423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:42.007498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:43.198102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:13.198328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:42.015123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:42.015162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:43.198119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:13.198104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:42.022905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:42.023160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:43.198100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:13.198039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:42.035118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:42.035157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:43.198137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:13.198137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:42.043193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:42.043233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:43.198125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:13.198159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:42.052952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:42.053007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:43.198124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:13.197979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:42.071403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:42.071491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:43.198209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:13.198140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:42.078968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:42.079013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:43.198083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:13.198090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:42.088640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:42.088692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:43.198097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:13.198082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:42.095740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:42.095772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:43.198052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:13.198100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:42.102213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:42.102248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:43.198154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:13.198057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:42.111498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:42.111538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:43.198062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:13.198095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:42.118828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:42.118866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:43.198084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:13.198106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:42.126384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:42.126422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:43.198133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:13.198128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:42.133399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:42.133474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:43.198257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:13.198304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:42.141937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:42.142007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:43.198175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:13.198136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:42.148786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:42.148824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:43.198119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:13.198113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:42.156358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:42.156403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:43.198143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:13.198133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:42.164311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:42.164364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:43.198152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:13.198056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:42.172866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:42.172901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:43.198042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:13.198072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:42.178993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:42.179038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:43.198088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:13.198137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:42.187567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:42.187597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:43.198133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:13.198184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:42.196140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:42.196198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:43.198282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:13.198123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:42.206017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:42.206088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:43.198101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:13.198193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:42.212797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:42.212848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:43.198103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:13.198120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:42.220380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:42.220558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:43.198065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:13.198135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:42.227392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:42.227493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:43.198147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:13.198747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:42.235260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:42.235303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:43.198041 metrics.go:34: INFO No non-zero metrics in the last 30s