Results

          2022/03/10 03:00:25.858574 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/10 03:00:25.858643 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 03:00:25.858729 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 03:00:25.858840 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 03:00:25.858887 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 03:00:25.859013 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-2dhrp
2022/03/10 03:00:25.859257 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 03:00:25.859283 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 03:00:25.859752 beat.go:221: INFO filebeat start running.
2022/03/10 03:00:25.859851 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 03:00:25.865726 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 03:00:25.865829 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 03:00:25.865941 registrar.go:236: INFO Starting Registrar
2022/03/10 03:00:25.866006 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 03:00:25.866126 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 03:00:25.866300 sync.go:41: INFO Start sending events to output
2022/03/10 03:00:25.866360 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 03:00:25.866898 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/10 03:00:25.867168 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 03:00:45.874382 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/10 03:00:45.874599 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/10 03:00:45.874932 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/10 03:00:45.875037 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/10 03:00:45.875153 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/10 03:00:45.895807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:00:45.895902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:00:46.901327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:00:46.901403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:00:48.907534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:00:48.907598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:00:52.913772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:00:52.913803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:00:55.859270 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=38 registrar.writes=1
2022/03/10 03:01:00.921440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:00.921475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:16.937900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:16.937945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:25.859348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:01:48.956944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:48.957085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:55.859217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:02:25.859280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:02:48.974422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:02:48.974685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:02:55.859264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:03:25.859266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:03:48.996141 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:03:48.996220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:03:55.859315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:04:25.859284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:04:49.018353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:04:49.018393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:04:55.859249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:05:25.859270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:05:49.036444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:05:49.036500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:05:50.888093 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:05:50.888180 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:05:50.888088 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:05:50.888141 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:05:55.859486 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/10 03:05:58.893134 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:06:25.859241 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/10 03:06:49.056022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:06:49.056252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:06:55.859172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:07:25.859152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:07:49.073311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:07:49.073472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:07:55.859321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:08:25.859224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:08:49.090145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:08:49.090204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:08:55.859426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:09:25.859300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:09:49.108225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:09:49.108277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:09:55.859227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:10:25.859113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:10:49.128054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:10:49.128096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:10:55.859214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:11:25.859329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:11:49.144573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:11:49.144648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:11:55.859239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:12:25.859201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:12:49.160213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:12:49.160264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:12:55.859172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:13:25.859243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:13:49.179225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:13:49.179281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:13:55.859159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:14:25.859402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:14:49.203802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:14:49.203860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:14:55.859268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:15:25.859339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:15:49.221309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:15:49.221357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:15:55.859145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:16:25.859247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:16:49.239315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:16:49.239376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:16:55.859261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:25.859352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:49.258452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:17:49.258635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:17:55.859287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:25.859341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:49.278910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:18:49.278992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:18:55.859334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:25.859310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:49.302762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:19:49.302851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:19:55.859150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:25.859242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:49.322340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:20:49.322393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:20:55.859216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:21:25.859344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:21:49.342225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:21:49.342264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:21:55.859221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:25.859217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:49.361338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:22:49.361394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:22:55.859219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:25.859201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:49.380381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:23:49.380421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:23:55.859276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:25.859444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:49.399684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:24:49.399766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:24:55.859313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:25.859280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:49.418522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:25:49.418582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:25:55.859327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:25.859171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:49.435632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:26:49.435682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:26:55.859350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:25.859174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:49.456670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:27:49.456733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:27:55.859220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:25.859124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:49.472907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:28:49.472947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:28:55.859145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:25.863425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:49.491296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:29:49.491353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:29:55.859140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:25.859161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:49.510885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:30:49.510975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:30:55.859320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:25.859342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:51.530426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:31:51.530477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:31:55.859347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:25.859308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:51.549288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:32:51.549325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:32:55.859161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:25.859307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:51.575014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:33:51.575057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:33:55.859263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:25.859173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:51.600427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:34:51.600603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:34:55.859163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:25.859220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:51.619944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:35:51.620002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:35:55.859275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:25.859167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:51.639605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:36:51.639649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:36:55.859300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:25.859293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:51.658516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:37:51.658560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:37:55.859351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:25.859357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:51.676426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:38:51.676475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:38:55.859278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:25.859252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:51.693407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:39:51.693455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:39:55.859313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:25.859222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:51.713402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:40:51.713477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:40:55.859241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:25.859251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:51.732403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:41:51.732443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:41:55.859273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:25.859228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:51.748914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:42:51.748961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:42:55.859228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:25.859323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:51.775645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:43:51.775726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:43:55.859325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:25.859252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:51.794946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:51.795009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:55.859241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:45:25.859361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:45:51.803139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:51.803288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:55.859229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:25.859258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:51.820925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:46:51.820974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:46:55.859291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:25.859136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:51.844150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:47:51.844205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:47:55.859253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:25.859286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:51.866182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:48:51.866235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:48:55.859171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:25.859248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:51.885605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:49:51.885680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:49:55.859317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:50:25.859228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:50:51.903928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:50:51.903982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:50:55.859163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:25.859299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:51.923035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:51:51.923088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:51:55.859486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:25.859300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:51.943058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:52:51.943117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:52:55.859600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:25.859232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:51.962430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:53:51.962474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:53:55.859335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:25.859334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:51.980610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:54:51.980651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:54:55.859331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:25.859306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:51.999555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:55:51.999612 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:55:55.859722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:25.859314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:52.018162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:56:52.018204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:56:55.859283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:25.859321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:52.041945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:57:52.042004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:57:55.859261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:25.859375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:52.060730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:58:52.060771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:58:55.859262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:25.859260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:52.080982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:59:52.081038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:59:55.859320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:25.859242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:52.100732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:00:52.101167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:00:55.859194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:25.859231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:52.129994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:01:52.130090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:01:55.859231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:25.859159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:52.148127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:02:52.148177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:02:55.859297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:25.859226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:52.167803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:03:52.167847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:03:55.859347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:25.859328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:52.186266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:04:52.186328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:04:55.859212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:25.859206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:52.208228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:05:52.208303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:05:55.859294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:25.859299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:52.227879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:06:52.227929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:06:55.859366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:25.859237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:52.244415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:07:52.244461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:07:55.859235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:25.859347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:52.262630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:08:52.262695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:08:55.859155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:25.859279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:52.282625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:09:52.282669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:09:55.859286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:25.859221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:52.301519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:10:52.301578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:10:55.859267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:25.859388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:52.326756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:11:52.326821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:11:55.859219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:25.859290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:52.348409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:12:52.348475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:12:55.859382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:25.859381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:52.369315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:13:52.369375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:13:55.859297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:25.859247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:52.391898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:14:52.391964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:14:55.859216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:25.859236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:52.416302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:15:52.416530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:15:55.859292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:25.859227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:52.438569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:16:52.438631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:16:55.859283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:25.859273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:52.454921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:17:52.454967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:17:55.859249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:25.859241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:52.475461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:18:52.475526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:18:55.859233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:25.859278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:52.495955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:19:52.496016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:19:55.859224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:25.859253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:52.517393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:20:52.517454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:20:55.859235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:25.859312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:52.538434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:21:52.538472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:21:55.859153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:25.859162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:52.562238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:22:52.562279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:22:55.859219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:25.859277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:52.581787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:23:52.581834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:23:55.859233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:25.859283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:52.602534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:24:52.602573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:24:55.859236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:25.859241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:52.620715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:25:52.620785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:25:55.859437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:25.859382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:52.639705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:26:52.639743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:26:55.859326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:25.859341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:52.657932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:27:52.657983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:27:55.859287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:25.859260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:52.676449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:28:52.676495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:28:55.859233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:25.859264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:52.695891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:29:52.696057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:29:55.859298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:25.859304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:52.717079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:30:52.717121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:30:55.859158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:25.859253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:52.734128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:31:52.734170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:31:55.859302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:25.859169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:52.756772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:32:52.756815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:32:55.859332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:25.859292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:52.774470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:33:52.775109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:33:55.859237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:25.859320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:52.793144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:34:52.793183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:34:55.859312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:25.859147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:52.811286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:35:52.811417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:35:55.859295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:25.859242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:52.827893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:36:52.827938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:36:55.859262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:25.859250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:52.845107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:37:52.845158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:37:55.859228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:25.859249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:52.864189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:38:52.864227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:38:55.859241 metrics.go:34: INFO No non-zero metrics in the last 30s