Results

          2022/03/22 10:49:08.025633 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/22 10:49:08.025786 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/22 10:49:08.025959 logstash.go:90: INFO Max Retries set to: 3
2022/03/22 10:49:08.026111 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/22 10:49:08.026284 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-7rq78
2022/03/22 10:49:08.026632 async.go:63: INFO Flush Interval set to: 1s
2022/03/22 10:49:08.026690 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/22 10:49:08.027309 metrics.go:23: INFO Metrics logging every 30s
2022/03/22 10:49:08.027704 beat.go:221: INFO filebeat start running.
2022/03/22 10:49:08.027862 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/22 10:49:08.032992 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/22 10:49:08.033134 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/22 10:49:08.033254 crawler.go:38: INFO Loading Prospectors: 1
2022/03/22 10:49:08.033553 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/22 10:49:08.033829 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/22 10:49:08.033867 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/22 10:49:08.033906 registrar.go:236: INFO Starting Registrar
2022/03/22 10:49:08.033949 sync.go:41: INFO Start sending events to output
2022/03/22 10:49:08.034008 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/22 10:49:28.036838 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/22 10:49:28.036953 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/22 10:49:28.037065 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/22 10:49:28.037135 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/22 10:49:28.037327 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/22 10:49:28.083828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:28.083883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:29.093851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:29.093893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:31.099188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:31.099229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:35.110441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:35.110488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:38.028018 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/22 10:49:43.120320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:43.120370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:59.141455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:49:59.141506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:50:08.027654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:50:31.191968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:50:31.192031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:50:38.027943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:51:08.027681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:51:31.214655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:31.214708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:38.029060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:52:08.027735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:52:31.236495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:52:31.236542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:52:38.027694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:53:08.027770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:53:31.290332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:53:31.290371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:53:38.027665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:54:08.027641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:54:31.313767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:54:31.314049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:54:33.076962 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/22 10:54:33.077059 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/22 10:54:33.076982 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/22 10:54:33.077517 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/22 10:54:38.027722 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/22 10:54:48.072373 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/22 10:55:08.027907 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/22 10:55:31.337467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:55:31.337525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:55:38.027794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:56:08.027756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:56:31.362762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:56:31.362807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:56:38.027962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:57:08.027767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:57:31.387450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:57:31.387569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:57:38.027725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:58:08.027780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:58:31.415178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:58:31.415399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:58:38.027737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:59:08.027748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:59:31.438126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:59:31.438194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:59:38.027819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:00:08.027737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:00:31.463884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:00:31.464096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:00:38.027740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:01:08.027682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:01:31.493444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:01:31.493503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:01:38.027807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:02:08.027697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:02:31.515373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:02:31.515431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:02:38.027714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:03:08.027779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:03:31.534817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:03:31.534868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:03:38.027710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:04:08.028038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:04:31.554888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:04:31.554971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:04:38.027774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:05:08.027737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:05:31.575151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:05:31.575190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:05:38.027695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:06:08.027756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:06:31.598608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:06:31.598672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:06:38.028311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:07:08.027624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:07:31.634762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:07:31.634814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:07:38.027844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:08:08.027899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:08:31.668181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:08:31.668251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:08:38.031690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:09:08.027723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:09:31.696024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:09:31.696158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:09:38.027816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:10:08.028381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:10:31.716072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:10:31.716114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:10:38.027676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:11:08.027718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:11:31.739186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:11:31.739241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:11:38.027696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:12:08.027894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:12:31.769438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:12:31.769706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:12:38.027721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:13:08.027732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:13:31.789981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:13:31.790032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:13:38.027759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:14:08.027679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:14:31.811313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:14:31.811370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:14:38.027698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:15:08.027733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:15:31.847836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:15:31.847880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:15:38.028277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:16:08.027782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:16:31.877993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:16:31.878178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:16:38.027670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:17:08.027660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:17:31.900457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:17:31.900500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:17:38.027720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:18:08.027878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:18:31.924052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:18:31.924106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:18:38.027890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:19:08.027668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:19:31.951700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:19:31.951758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:19:38.027706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:20:08.027696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:20:31.980503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:20:31.980555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:20:38.027733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:21:08.027758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:21:32.004407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:21:32.004756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:21:38.027711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:22:08.027945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:22:32.024940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:22:32.024986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:22:38.027979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:23:08.027698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:23:32.044719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:23:32.044767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:23:38.027667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:24:08.027687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:24:32.073198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:24:32.073264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:24:38.027750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:25:08.027921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:25:32.094699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:25:32.094775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:25:38.027773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:26:08.027812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:26:32.114366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:26:32.114418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:26:38.027714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:27:08.027706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:27:32.135559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:27:32.135600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:27:38.027689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:28:08.027767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:28:32.157842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:28:32.157899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:28:38.027837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:29:08.027721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:29:32.182378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:29:32.182435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:29:38.027725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:30:08.027703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:30:32.205848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:30:32.205957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:30:38.027702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:31:08.028183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:31:32.224958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:31:32.225008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:31:38.027898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:32:08.027696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:32:32.247794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:32:32.247851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:32:38.027715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:33:08.028313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:33:32.270308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:33:32.270370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:33:38.027744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:34:08.027672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:34:32.291535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:34:32.291595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:34:38.027907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:35:08.027729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:35:32.309787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:35:32.309829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:35:38.027705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:36:08.027814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:36:32.329374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:36:32.329430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:36:38.028090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:37:08.027658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:37:32.354677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:37:32.354716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:37:38.027702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:38:08.027770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:38:32.374626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:38:32.374665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:38:38.027674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:39:08.027655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:39:32.395188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:39:32.395244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:39:38.027654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:40:08.027726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:40:32.416236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:40:32.416283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:40:38.027783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:41:08.027905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:41:32.439700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:41:32.439741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:41:38.027694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:42:08.027717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:42:32.473641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:42:32.473709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:42:38.027770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:43:08.027781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:43:32.497877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:43:32.497913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:43:38.028893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:44:08.027744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:44:32.518492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:44:32.518547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:44:38.027774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:45:08.027727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:45:32.552982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:45:32.553049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:45:38.027650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:46:08.027671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:46:32.591349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:46:32.591413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:46:38.027637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:47:08.027762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:47:32.610824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:47:32.610960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:47:38.027695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:48:08.027702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:48:32.633656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:48:32.633710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:48:38.027733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:49:08.027754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:49:32.661068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:49:32.661129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:49:38.027771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:50:08.027760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:50:32.686841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:50:32.686925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:50:38.027643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:51:08.027810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:51:32.708434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:51:32.708497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:51:38.027989 metrics.go:34: INFO No non-zero metrics in the last 30s