By type
2022/04/17 03:15:00.099773 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/04/17 03:15:00.099830 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/17 03:15:00.099965 logstash.go:90: INFO Max Retries set to: 3
2022/04/17 03:15:00.100046 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/17 03:15:00.100228 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-msnct
2022/04/17 03:15:00.100483 async.go:63: INFO Flush Interval set to: 1s
2022/04/17 03:15:00.100495 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/17 03:15:00.100928 beat.go:221: INFO filebeat start running.
2022/04/17 03:15:00.101054 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/17 03:15:00.102904 metrics.go:23: INFO Metrics logging every 30s
2022/04/17 03:15:00.105551 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/17 03:15:00.105647 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/17 03:15:00.105702 crawler.go:38: INFO Loading Prospectors: 1
2022/04/17 03:15:00.105774 registrar.go:236: INFO Starting Registrar
2022/04/17 03:15:00.105824 sync.go:41: INFO Start sending events to output
2022/04/17 03:15:00.105887 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/17 03:15:00.105982 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/17 03:15:00.105982 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/17 03:15:00.106029 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/17 03:15:10.108287 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/17 03:15:10.108763 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/17 03:15:10.109121 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/17 03:15:10.109515 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/17 03:15:10.109923 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/17 03:15:15.120499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:15.120528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:16.124247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:16.124278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:18.132591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:18.132658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:22.140618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:22.140655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:30.103533 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=59 registrar.writes=1
2022/04/17 03:15:30.148471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:30.148522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:46.154686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:46.154724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:00.103344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:16:18.158289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:18.158321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:30.103443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:17:00.103290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:17:18.162007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:17:18.162046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:17:30.103493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:18:00.103500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:18:18.165758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:18:18.165790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:18:30.103334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:19:00.103390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:19:18.169684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:19:18.169731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:19:30.103367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:20:00.103381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:20:15.119618 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/17 03:20:18.172374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:20:18.172420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:20:22.121034 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/17 03:20:22.121149 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/17 03:20:22.121187 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/17 03:20:30.103316 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/04/17 03:20:33.124839 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/17 03:21:00.103379 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/04/17 03:21:18.177523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:21:18.177759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:21:30.103338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:22:00.103433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:22:18.181290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:22:18.181324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:22:30.103472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:23:00.103507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:23:18.185165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:23:18.185342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:23:30.103596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:24:00.103356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:24:18.189408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:24:18.189442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:24:30.103438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:25:00.103337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:25:18.193077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:25:18.193117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:25:30.103511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:26:00.103367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:26:18.202966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:26:18.202995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:26:30.103331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:27:00.103503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:27:18.209956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:27:18.209986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:27:30.103357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:28:00.103334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:28:18.218041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:28:18.218074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:28:30.103420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:29:00.103640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:29:18.226456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:29:18.226490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:29:30.103396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:30:00.103512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:30:18.234074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:30:18.234113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:30:30.103501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:31:00.103452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:31:18.242380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:31:18.242431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:31:30.103390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:32:00.103362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:32:18.248593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:32:18.248626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:32:30.103521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:33:00.103310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:33:18.256512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:33:18.256558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:33:30.103398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:34:00.103327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:34:18.263497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:34:18.263547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:34:30.103512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:35:00.103357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:35:18.273635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:35:18.273688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:35:30.103372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:36:00.103371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:36:18.281523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:36:18.281561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:36:30.103482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:37:00.103470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:37:18.290014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:37:18.290049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:37:30.103632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:38:00.103383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:38:18.298306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:38:18.298340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:38:30.103373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:39:00.103418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:39:18.305487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:39:18.305533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:39:30.103367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:40:00.103383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:40:18.312219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:40:18.312252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:40:30.103422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:41:00.103494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:41:18.318491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:41:18.318525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:41:30.103369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:42:00.103303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:42:18.324806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:42:18.324838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:42:30.103301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:43:00.103335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:43:18.332460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:43:18.332513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:43:30.103335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:44:00.103354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:44:18.360542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:44:18.360578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:44:30.103378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:45:00.103387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:45:18.371352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:45:18.371385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:45:30.103375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:46:00.103374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:46:18.378645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:46:18.378691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:46:30.103521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:47:00.103551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:47:18.385988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:47:18.386035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:47:30.103501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:48:00.103490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:48:18.392550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:48:18.392593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:48:30.103470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:49:00.103336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:49:18.399840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:49:18.399904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:49:30.103331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:50:00.103486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:50:18.407023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:50:18.407077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:50:30.103598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:51:00.103303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:51:18.417169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:51:18.417319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:51:30.103446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:52:00.103638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:52:18.424752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:52:18.424783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:52:30.103360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:53:00.103332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:53:18.430751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:53:18.430784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:53:30.103374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:54:00.103379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:54:18.437026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:54:18.437163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:54:30.103458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:55:00.103346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:55:18.443964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:55:18.443997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:55:30.103317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:56:00.103454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:56:18.450822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:56:18.450855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:56:30.103606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:57:00.103579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:57:18.459442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:57:18.459478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:57:30.103454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:58:00.103510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:58:18.466801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:58:18.466837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:58:30.103335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:59:00.103671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:59:18.473130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:59:18.473161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:59:30.103520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:00:00.103344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:00:18.480441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:00:18.480480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:00:30.103533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:01:00.103391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:01:18.487459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:01:18.487493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:01:30.103279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:02:00.103370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:02:18.495131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:02:18.495170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:02:30.103522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:03:00.103350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:03:18.503998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:03:18.504030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:03:30.103337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:04:00.103332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:04:18.517772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:04:18.517828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:04:30.103337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:05:00.103370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:05:18.525647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:05:18.525682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:05:30.103409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:06:00.103348 metrics.go:34: INFO No non-zero metrics in the last 30s