2022/04/09 03:10:36.096404 metrics.go:23: INFO Metrics logging every 30s
2022/04/09 03:10:36.096496 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/09 03:10:36.096573 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/09 03:10:36.096842 logstash.go:90: INFO Max Retries set to: 3
2022/04/09 03:10:36.097016 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/09 03:10:36.097330 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-h5n7w
2022/04/09 03:10:36.097775 async.go:63: INFO Flush Interval set to: 1s
2022/04/09 03:10:36.097825 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/09 03:10:36.098662 beat.go:221: INFO filebeat start running.
2022/04/09 03:10:36.098795 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/09 03:10:36.108670 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/09 03:10:36.108861 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/09 03:10:36.108970 crawler.go:38: INFO Loading Prospectors: 1
2022/04/09 03:10:36.109000 registrar.go:236: INFO Starting Registrar
2022/04/09 03:10:36.109211 sync.go:41: INFO Start sending events to output
2022/04/09 03:10:36.109418 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/09 03:10:36.110534 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/09 03:10:36.111120 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/09 03:10:36.111572 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/09 03:10:56.114816 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/09 03:10:56.115029 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/09 03:10:56.115161 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/09 03:10:56.115400 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/09 03:10:56.115427 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/09 03:11:01.135591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:01.135648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:02.142008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:02.142235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:04.146134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:04.146181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:06.096926 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=200 registrar.writes=1
2022/04/09 03:11:08.152558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:08.152591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:16.161126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:16.161199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:32.181220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:32.181277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:36.096716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:12:04.200287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:12:04.200415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:12:06.096796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:12:36.096992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:13:04.219111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:13:04.219294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:13:06.097035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:13:36.096864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:14:04.238403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:14:04.238445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:14:06.097193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:14:36.097109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:15:04.259936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:15:04.260010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:15:06.097262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:15:36.097185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:16:01.126196 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/09 03:16:01.126313 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/09 03:16:01.126350 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/09 03:16:01.126392 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/09 03:16:04.276923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:16:04.276971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:16:06.097233 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/09 03:16:07.137569 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/09 03:16:36.097224 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/09 03:17:04.293835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:17:04.293874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:17:06.097171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:17:36.097150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:18:04.312978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:18:04.313022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:18:06.096712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:18:36.096841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:19:04.330060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:19:04.330099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:19:06.096820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:19:36.096790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:20:04.346986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:20:04.347037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:20:06.096778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:20:36.096766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:21:04.365627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:21:04.365664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:21:06.096818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:21:36.096839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:22:04.382528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:22:04.382571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:22:06.096752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:22:36.096753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:23:04.402758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:23:04.402796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:23:06.096758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:23:36.096754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:24:04.422262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:24:04.422304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:24:06.096789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:24:36.096806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:25:04.441798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:25:04.441847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:25:06.096812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:25:36.096738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:26:04.459406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:26:04.459456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:26:06.096751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:26:36.096775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:27:04.478084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:27:04.478166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:27:06.096732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:27:36.096730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:28:04.496675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:28:04.496723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:28:06.096686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:28:36.096886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:29:04.514531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:29:04.514576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:29:06.096861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:29:36.096842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:30:04.530639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:30:04.530673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:30:06.096781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:30:36.096754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:31:04.548367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:31:04.548409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:31:06.096733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:31:36.096941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:32:04.566003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:32:04.566050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:32:06.096796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:32:36.096702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:33:04.582717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:33:04.582757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:33:06.096802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:33:36.096729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:34:04.601340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:34:04.601411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:34:06.096709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:34:36.096744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:35:04.618910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:35:04.618957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:35:06.096766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:35:36.096796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:36:04.637374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:36:04.637423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:36:06.096733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:36:36.097125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:37:04.655630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:37:04.655670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:37:06.096834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:37:36.096798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:38:04.679993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:38:04.680051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:38:06.096711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:38:36.096746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:39:04.697795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:39:04.697832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:39:06.096806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:39:36.096765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:40:04.716279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:40:04.716315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:40:06.096707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:40:36.096726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:41:04.734285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:41:04.734333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:41:06.096732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:41:36.096774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:42:04.752369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:42:04.752427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:42:06.096785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:42:36.096784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:43:04.769770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:43:04.769810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:43:06.096738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:43:36.096732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:44:04.785455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:44:04.785494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:44:06.096759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:44:36.096775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:45:04.802136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:45:04.802341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:45:06.096794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:45:36.096788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:46:04.820006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:46:04.820040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:46:06.096752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:46:36.096732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:47:04.836365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:47:04.836399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:47:06.096758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:47:36.096782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:48:04.853692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:48:04.853899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:48:06.096801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:48:36.096812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:49:04.871922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:49:04.872094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:49:06.096765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:49:36.096724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:50:04.888964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:50:04.889010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:50:06.097001 metrics.go:34: INFO No non-zero metrics in the last 30s