By type
2022/03/05 03:12:36.695372 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/05 03:12:36.695411 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:12:36.695467 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:12:36.695534 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:12:36.695654 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-9x58m
2022/03/05 03:12:36.695668 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:12:36.695863 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:12:36.695892 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:12:36.696462 beat.go:221: INFO filebeat start running.
2022/03/05 03:12:36.696527 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:12:37.317221 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:12:37.317316 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:12:37.317470 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:12:37.317505 registrar.go:236: INFO Starting Registrar
2022/03/05 03:12:37.317858 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:12:37.317876 sync.go:41: INFO Start sending events to output
2022/03/05 03:12:37.317879 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:12:37.318007 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/05 03:12:37.318074 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:12:37.319071 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/05 03:12:37.319206 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/05 03:12:37.319305 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/05 03:12:37.319349 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/05 03:12:37.319409 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/05 03:12:42.337235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:42.337318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:43.341576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:43.341600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:45.347576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:45.347652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:49.357775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:49.357846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:57.367533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:12:57.367575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:13:06.696209 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=55 registrar.writes=1
2022/03/05 03:13:13.377539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:13:13.377575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:13:36.696709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:13:45.389803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:13:45.390114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:14:06.696116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:14:36.696102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:14:45.399778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:14:45.399844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:15:06.696192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:15:36.696065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:15:45.436528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:15:45.436659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:16:06.696147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:16:36.696441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:16:45.446567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:16:45.446601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:17:06.696179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:17:36.696102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:17:42.332081 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:17:45.457510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:17:45.457660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:17:57.333063 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:17:57.333144 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:17:57.333122 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:18:06.696074 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-4
2022/03/05 03:18:36.696063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:18:45.481393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:18:45.481427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:19:06.696165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:19:36.696151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:19:45.491679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:19:45.491718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:20:06.696090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:20:36.696075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:20:45.501564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:20:45.501597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:21:06.696110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:21:36.696146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:21:45.526564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:21:45.526615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:22:06.696173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:22:36.696235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:22:45.535883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:22:45.535919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:23:06.696102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:23:36.696118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:23:45.544294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:23:45.544393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:24:06.696116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:24:36.696176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:24:45.585883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:24:45.585925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:25:06.696081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:25:36.696151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:25:45.594487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:25:45.594526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:26:06.696111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:26:36.696141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:26:45.603486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:26:45.603533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:27:06.696122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:27:36.696151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:27:45.614335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:27:45.614386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:28:06.696059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:28:36.696075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:28:45.661120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:28:45.661182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:29:06.696242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:29:36.696106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:29:45.682806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:29:45.682833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:30:06.696011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:36.696051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:45.830113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:30:45.830145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:31:06.696218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:36.696057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:45.869630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:31:45.869660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:32:06.696008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:36.696233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:56.738549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:00.182602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:34:00.182647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:34:06.696185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:36.696236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:00.192691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:35:00.192730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:35:06.696078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:36.696341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:02.983799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:36:02.983880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:36:06.696057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:36.696496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:02.993554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:37:02.993647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:37:06.696266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:36.696316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:03.006254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:38:03.006319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:38:06.696191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:36.696353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:03.016939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:39:03.017025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:39:06.696204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:36.696338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:03.029712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:40:03.029769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:40:06.696037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:36.696578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:03.040873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:41:03.040956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:41:06.696251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:11.418078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:11.480752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:42:11.480778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:42:36.696115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:06.696065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:11.491582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:43:11.491606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:43:36.696254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:06.696173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:11.506830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:44:11.506870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:44:36.696067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:06.695990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:11.517533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:45:11.517589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:45:36.696033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:06.696068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:11.526827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:46:11.526873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:46:36.696027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:06.696026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:11.535221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:47:11.535266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:47:36.696089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:06.696170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:11.549557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:48:11.549609 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:48:36.696168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:06.696132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:11.559858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:49:11.559898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:49:36.696091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:06.696052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:11.571146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:50:11.571181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:50:36.696043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:06.696136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:11.581392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:51:11.581435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:51:36.696123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:06.696137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:11.593085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:52:11.593120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:52:36.696071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:06.696084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:11.604913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:53:11.604958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:53:36.695986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:06.695987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:11.622415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:54:11.622476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:54:36.696212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:06.696144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:11.631692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:55:11.631748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:55:36.696092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:06.696118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:11.643527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:56:11.643567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:56:36.696127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:06.695977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:11.653227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:57:11.653288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:57:36.696122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:06.696083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:11.665304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:11.665352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:36.696044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:06.696096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:11.674288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:11.674318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:36.696108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:06.696112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:11.683724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:11.683763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:36.696206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:06.696120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:11.693060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:11.693102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:36.696214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:06.696176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:11.713784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:11.713827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:36.696401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:06.696196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:11.724824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:11.724886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:36.696172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:06.696081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:11.735162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:11.735209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:36.696197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:06.696017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:11.745281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:11.745343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:36.696240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:06.696088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:11.756863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:11.756910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:36.696070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:06.696130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:11.767910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:11.767953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:36.695972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:06.696126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:11.778150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:11.778190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:36.696154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:06.696148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:11.788175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:11.788200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:36.696103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:06.696070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:11.800058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:11.800097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:36.696343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:06.696072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:11.810782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:11.810815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:36.696094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:06.696202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:11.822441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:11.822487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:36.696123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:06.696092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:11.832651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:11.832704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:36.696041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:06.696153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:11.848851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:11.848910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:36.696077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:06.696079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:11.859443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:11.860471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:36.696125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:06.696187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:11.872097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:11.872121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:36.696032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:06.696153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:11.920414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:11.920447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:36.696112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:06.695982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:36.696107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:38.826624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:38.826695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:06.696092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:36.695982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:38.836925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:38.836958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:06.696144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:36.696110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:38.846682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:38.846718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:06.696079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:36.696132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:38.855474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:38.855521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:06.696104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:36.696111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:38.865178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:38.865211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:06.695995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:36.696188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:38.879232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:38.879263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:06.696123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:36.696119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:38.888966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:38.889004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:06.696090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:36.696104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:38.898860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:38.898911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:06.696119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:36.696093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:38.909157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:38.909199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:06.696112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:36.696088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:38.918734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:38.918785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:06.696253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:36.696083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:38.929164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:38.929207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:06.696132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:36.696085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:38.955791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:38.955831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:06.696118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:36.696168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:38.969797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:38.969832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:06.696079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:36.696180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:38.979770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:38.979804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:06.696121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:36.696082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:38.988230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:38.988257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:06.696047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:36.696015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:38.996380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:38.996408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:06.695975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:36.696070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:39.005284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:39.005373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:06.696089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:36.696097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:39.014067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:39.014109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:06.696038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:36.696131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:39.023969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:39.024012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:06.696126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:36.696065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:39.032819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:39.032845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:06.696167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:36.696093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:39.043400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:39.043455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:06.696148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:36.696142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:39.053043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:39.053070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:06.696161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:36.696179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:39.062775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:39.062809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:06.696130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:36.696041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:39.072851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:39.072892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host