By type
2022/03/17 09:46:20.702764 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/17 09:46:20.703162 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/17 09:46:20.704281 logstash.go:90: INFO Max Retries set to: 3
2022/03/17 09:46:20.704593 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/17 09:46:20.704996 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-74skz
2022/03/17 09:46:20.705570 async.go:63: INFO Flush Interval set to: 1s
2022/03/17 09:46:20.705666 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/17 09:46:20.707439 beat.go:221: INFO filebeat start running.
2022/03/17 09:46:20.707555 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/17 09:46:20.708697 metrics.go:23: INFO Metrics logging every 30s
2022/03/17 09:46:20.721081 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/17 09:46:20.721226 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/17 09:46:20.721317 crawler.go:38: INFO Loading Prospectors: 1
2022/03/17 09:46:20.721484 registrar.go:236: INFO Starting Registrar
2022/03/17 09:46:20.721525 sync.go:41: INFO Start sending events to output
2022/03/17 09:46:20.721703 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/17 09:46:20.721726 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/17 09:46:20.722214 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/17 09:46:20.722594 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/17 09:46:40.726102 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/17 09:46:40.726308 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/17 09:46:40.726420 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/17 09:46:40.726546 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/17 09:46:40.726808 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/17 09:46:45.781989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:46:45.782050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:46:46.788377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:46:46.788419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:46:48.792595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:46:48.792636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:46:50.709439 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/17 09:46:52.802613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:46:52.802696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:47:00.813447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:47:00.813516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:47:16.839132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:47:16.839207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:47:20.709260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:47:48.867797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:47:48.867859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:47:50.709281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:48:20.709283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:48:48.889189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:48:48.889262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:48:50.709217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:49:20.709221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:49:48.925344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:49:48.925399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:49:50.709319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:50:20.709457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:50:48.953159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:48.953232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:50.709403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:51:20.709307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:51:45.742865 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/17 09:51:45.742873 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/17 09:51:45.742971 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/17 09:51:45.750271 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/17 09:51:48.976284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:51:48.976342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:51:50.709312 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/17 09:52:00.749871 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/17 09:52:20.713328 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/17 09:52:49.009477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:52:49.009530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:52:50.709311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:53:20.709291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:53:49.036413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:53:49.036458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:53:50.709247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:54:20.709341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:54:49.062691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:54:49.062770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:54:50.709354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:55:20.709331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:55:49.086065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:55:49.086242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:55:50.709293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:56:20.709353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:56:49.106205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:56:49.106266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:56:50.709322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:57:20.709310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:57:49.125998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:57:49.126064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:57:50.709311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:58:20.709169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:58:49.146213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:58:49.146286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:58:50.709390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:59:20.709328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:59:49.174422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:59:49.174493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:59:50.709291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:00:20.709481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:00:49.228804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:00:49.228843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:00:50.709261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:01:20.709908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:01:49.261132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:01:49.261181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:01:50.709270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:02:20.709378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:02:49.289124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:02:49.289183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:02:50.709286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:03:20.709288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:03:49.311217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:03:49.311345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:03:50.710347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:04:20.709194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:04:49.334496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:04:49.334537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:04:50.709273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:05:20.709420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:05:49.356647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:05:49.356703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:05:50.709255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:06:20.709291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:06:49.377591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:06:49.377637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:06:50.709284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:07:20.709275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:07:49.400075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:07:49.400117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:07:50.709172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:08:20.709185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:08:49.422107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:08:49.422148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:08:50.709361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:09:20.709281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:09:49.439597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:09:49.439636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:09:50.709335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:10:20.709278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:10:49.457634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:10:49.457692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:10:50.709232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:11:20.709240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:11:49.480376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:11:49.480674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:11:50.709310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:12:20.709264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:12:49.501379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:12:49.501421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:12:50.709353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:13:20.709275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:13:49.520239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:13:49.520287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:13:50.709479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:14:20.709360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:14:49.538324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:14:49.538365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:14:50.709369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:15:20.709207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:15:49.558558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:15:49.558607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:15:50.709263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:16:20.709265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:16:49.587911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:16:49.587968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:16:50.709314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:17:20.709319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:17:49.608985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:17:49.609064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:17:50.709294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:18:20.709451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:18:49.630231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:18:49.630296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:18:50.709314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:19:20.709292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:19:49.661940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:19:49.662004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:19:50.709242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:20:20.709393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:20:49.688515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:20:49.688558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:20:50.709248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:21:20.709476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:21:49.710555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:21:49.710598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:21:50.709216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:22:20.709264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:22:49.736127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:22:49.736198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:22:50.709304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:23:20.709449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:23:49.758106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:23:49.758185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:23:50.709245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:24:20.709553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:24:49.781288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:24:49.781348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:24:50.709726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:25:20.709322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:25:49.806077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:25:49.806127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:25:50.709225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:26:20.709342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:26:49.829538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:26:49.829586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:26:50.709211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:27:20.709293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:27:49.848364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:27:49.848426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:27:50.709249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:28:20.709268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:28:49.874169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:28:49.874249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:28:50.709301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:29:20.709600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:29:49.896477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:29:49.896543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:29:50.709324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:30:20.709250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:30:49.927385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:30:49.927429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:30:50.709405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:31:20.709302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:31:49.951054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:31:49.951116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:31:50.709265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:32:20.709377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:32:49.973526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:32:49.973585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:32:50.709256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:33:20.709325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:33:50.002842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:33:50.002896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:33:50.709495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:34:20.709302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:34:50.026375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:34:50.026412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:34:50.709298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:35:20.709508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:35:50.045508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:35:50.045554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:35:50.709298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:36:20.709394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:36:50.064309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:36:50.064388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:36:50.709377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:37:20.709309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:37:50.093293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:37:50.093526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:37:50.709275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:38:20.709275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:38:50.118169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:38:50.118211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:38:50.709399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:39:20.709176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:39:50.122023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:39:50.122067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:39:50.709273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:40:20.709267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:40:50.130280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:40:50.130340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:40:50.709399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:41:20.709347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:41:50.139125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:41:50.139185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:41:50.709691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:42:20.709412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:42:50.149990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:42:50.150332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:42:50.709388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:43:20.709388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:43:50.160633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:43:50.160678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:43:50.709259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:44:20.709258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:44:50.170709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:44:50.170780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:44:50.709193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:45:20.709263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:45:50.178457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:45:50.178513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:45:50.709339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:46:20.709261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:46:50.187257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:46:50.187309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:46:50.709267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:47:20.709225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:47:50.213665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:47:50.213736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:47:50.709341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:48:20.709322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:48:50.220542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:48:50.220592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:48:50.709295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:49:20.709295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:49:50.234631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:49:50.234668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:49:50.709453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:50:20.709392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:50:50.246403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:50:50.246467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:50:50.709376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:51:20.709242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:51:50.254295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:51:50.254356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:51:50.709373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:52:20.709210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:52:50.263683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:52:50.263746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:52:50.709314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:53:20.709258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:53:50.275240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:53:50.275373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:53:50.709222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:54:20.709391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:54:50.283614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:54:50.283652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:54:50.709273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:55:20.709259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:55:50.291353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:55:50.291389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:55:50.709291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:56:20.709255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:56:50.300364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:56:50.300402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:56:50.709318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:57:20.709276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:57:50.311932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:57:50.312044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:57:50.709210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:58:20.709437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:58:50.319782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:58:50.319836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:58:50.709260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:59:20.709237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:59:50.328861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:59:50.328953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:59:50.713423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:00:20.709358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:00:50.335790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:00:50.335840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:00:50.709241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:01:20.709395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:01:50.345767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:01:50.345879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:01:50.709233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:02:20.709288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:02:50.355721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:02:50.355761 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:02:50.709345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:03:20.709413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:03:50.364137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:03:50.364177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:03:50.709214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:04:20.709324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:04:50.377470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:04:50.377515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:04:50.709329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:05:20.709269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:05:50.390602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:05:50.390646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:05:50.709315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:06:20.709299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:06:50.398033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:06:50.398091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:06:50.709250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:07:20.709304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:07:50.406019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:07:50.406480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:07:50.709241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:08:20.709286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:08:50.417820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:08:50.417869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:08:50.709249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:09:20.709225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:09:50.425099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:09:50.425138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:09:50.709285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:10:20.709224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:10:50.432570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:10:50.432616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:10:50.709215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:11:20.710170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:11:50.441767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:11:50.441818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:11:50.709276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:12:20.709214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:12:50.450756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:12:50.450802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:12:50.709271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:13:20.709341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:13:50.468612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:13:50.468674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:13:50.709232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:14:20.709205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:14:50.477607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:14:50.477650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:14:50.709370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:15:20.709347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:15:50.486101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:15:50.486157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:15:50.709342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:16:20.709262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:16:50.493048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:16:50.493085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:16:50.709232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:17:20.709418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:17:50.500471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:17:50.500517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:17:50.709386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:18:20.709366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:18:50.510426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:18:50.510470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:18:50.709346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:19:20.709287 metrics.go:34: INFO No non-zero metrics in the last 30s