Results

          2022/03/11 03:04:58.331645 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/11 03:04:58.331738 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/11 03:04:58.331775 metrics.go:23: INFO Metrics logging every 30s
2022/03/11 03:04:58.331864 logstash.go:90: INFO Max Retries set to: 3
2022/03/11 03:04:58.331975 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/11 03:04:58.332122 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-9t8hm
2022/03/11 03:04:58.332410 async.go:63: INFO Flush Interval set to: 1s
2022/03/11 03:04:58.332435 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/11 03:04:58.332910 beat.go:221: INFO filebeat start running.
2022/03/11 03:04:58.333014 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/11 03:04:58.338815 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/11 03:04:58.338884 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/11 03:04:58.338922 crawler.go:38: INFO Loading Prospectors: 1
2022/03/11 03:04:58.339169 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/11 03:04:58.339270 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/11 03:04:58.339293 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/11 03:04:58.339306 registrar.go:236: INFO Starting Registrar
2022/03/11 03:04:58.339332 sync.go:41: INFO Start sending events to output
2022/03/11 03:04:58.339374 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/11 03:05:18.341572 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/11 03:05:18.341813 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/11 03:05:18.341640 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/11 03:05:18.341735 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/11 03:05:18.341772 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/11 03:05:23.359862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:23.359911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:24.363502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:24.363551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:26.368848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:26.368890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:28.332141 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/11 03:05:30.375633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:30.375675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:38.382201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:38.382266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:54.400846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:54.400894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:05:58.332040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:06:26.419621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:26.419659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:28.332057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:06:58.332037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:07:26.436340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:07:26.436404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:07:28.332183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:07:58.332040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:08:26.459992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:08:26.460049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:08:28.332131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:08:58.332164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:09:26.477060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:09:26.477114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:09:28.332132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:09:58.332091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:10:23.362145 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:10:23.362146 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:10:23.362265 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:10:23.362885 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:10:26.494740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:10:26.494782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:10:28.332304 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/11 03:10:33.365206 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:10:58.332056 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/11 03:11:26.513253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:11:26.513299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:11:28.332132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:11:58.332158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:12:26.531718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:12:26.531791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:12:28.332147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:12:58.332754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:13:26.549429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:13:26.549473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:13:28.332221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:13:58.332055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:14:26.568947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:14:26.568997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:14:28.332081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:14:58.332116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:15:26.587931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:15:26.587977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:15:28.332084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:15:58.332416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:16:26.604813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:16:26.604855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:16:28.332128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:16:58.332244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:17:26.625873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:17:26.625959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:17:28.332084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:17:58.332097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:18:26.651557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:18:26.651603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:18:28.332151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:18:58.332163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:19:26.674094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:19:26.674145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:19:28.332171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:19:58.332109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:26.704727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:20:26.704769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:20:28.335736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:58.332101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:26.723795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:21:26.723847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:21:28.332153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:58.332080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:26.744837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:22:26.744886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:22:28.332326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:58.332210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:26.762909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:23:26.762979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:23:28.332180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:58.332241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:24:26.785408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:24:26.785446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:24:28.332072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:24:58.332046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:26.803144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:25:26.803180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:25:28.332999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:58.332049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:26.822589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:26:26.822619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:26:28.332258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:58.332198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:26.841523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:27:26.841570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:27:28.332137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:58.332105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:26.861584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:28:26.861641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:28:28.332177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:58.332126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:26.880868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:29:26.880907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:29:28.332172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:58.332106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:26.899999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:30:26.900043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:30:28.332084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:58.332084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:26.917290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:31:26.917345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:31:28.332159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:58.332421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:26.941555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:32:26.941633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:32:28.332158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:58.332097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:26.958411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:33:26.958449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:33:28.332165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:58.332073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:26.981480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:34:26.981535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:34:28.332113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:58.332133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:27.001068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:35:27.001126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:35:28.332135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:58.332022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:27.019582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:36:27.019625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:36:28.332101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:58.332079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:27.037886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:37:27.037919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:37:28.332166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:58.332082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:27.058520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:38:27.058569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:38:28.332091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:58.332101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:27.078389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:39:27.078430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:39:28.332145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:58.332101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:27.096876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:40:27.096942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:40:28.332136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:58.332090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:27.118180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:41:27.118222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:41:28.332132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:58.332083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:27.136186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:42:27.136251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:42:28.332539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:58.332216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:27.158873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:43:27.158924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:43:28.332073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:58.332158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:27.180047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:44:27.180097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:44:28.332202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:58.332079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:27.198084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:45:27.198115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:45:28.332009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:58.332067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:27.216538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:46:27.216583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:46:28.332464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:58.332076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:27.235265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:27.235323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:28.332079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:58.332171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:48:27.245847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:27.245896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:28.332073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:48:58.332133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:27.266850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:27.266894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:28.332169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:58.332077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:27.285739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:27.285768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:28.332085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:58.332214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:27.305088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:27.305147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:28.332217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:58.332198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:27.321801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:27.321860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:28.332110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:58.332078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:27.339418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:27.339483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:28.332066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:58.332166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:27.356078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:27.356140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:28.332150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:58.332046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:27.374147 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:27.374185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:28.332097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:58.332208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:27.391858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:27.391925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:28.332104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:58.332123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:27.409204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:27.409289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:28.332125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:58.332153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:27.427809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:27.427883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:28.332174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:58.332085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:27.450252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:27.450302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:28.332169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:58.332060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:27.468537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:27.468601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:28.332088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:58.332135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:27.488538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:27.488656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:28.332190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:58.332103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:27.506545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:27.506597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:28.332068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:58.332132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:27.526548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:27.526603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:28.332187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:58.332160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:27.544378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:27.544428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:28.332124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:58.332110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:27.565327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:27.565397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:28.332092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:58.332178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:27.588304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:27.588367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:28.332117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:58.332254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:27.605290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:27.605342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:28.332105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:58.332118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:27.620948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:27.621002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:28.332096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:58.332165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:27.653091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:27.653125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:28.332180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:58.332081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:27.670647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:27.670715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:28.332102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:58.332106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:27.687662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:27.687723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:28.332099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:58.332219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:27.707527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:27.707586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:28.332070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:58.332324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:27.725430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:27.725493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:28.332129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:58.332255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:27.755434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:27.755481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:28.332131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:58.332084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:27.772769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:27.772806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:28.332129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:58.332130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:27.790621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:27.790676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:28.332058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:58.332145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:27.809769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:27.809814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:28.332119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:58.332070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:27.825771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:27.825820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:28.332039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:58.332067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:27.842820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:27.842855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:28.332031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:58.332119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:27.864201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:27.864242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:28.332147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:58.332155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:27.883697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:27.883923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:28.332082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:58.332148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:27.900858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:27.900898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:28.332174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:58.332111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:27.917726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:27.918034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:28.332228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:58.332189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:27.935556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:27.935596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:28.332129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:58.332502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:27.956378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:27.956415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:28.332184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:58.332126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:27.974012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:27.974066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:28.332177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:58.332330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:27.993539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:27.993595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:28.332168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:58.332156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:28.012484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:28.012527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:28.332097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:58.332171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:28.033313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:28.033392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:28.332136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:58.332139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:28.050603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:28.050651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:28.332126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:58.332089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:28.067295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:28.067332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:28.332094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:58.332078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:28.083881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:28.083923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:28.332096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:58.332074 metrics.go:34: INFO No non-zero metrics in the last 30s