By type
2022/03/05 03:12:41.402032 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:41.402092 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:12:41.402164 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:12:41.402240 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:12:41.402375 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-bhd9f
2022/03/05 03:12:41.402573 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:12:41.402594 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:12:41.403032 beat.go:221: INFO filebeat start running.
2022/03/05 03:12:41.403213 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:12:41.403354 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:12:41.547670 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:12:41.547860 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:12:41.547914 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:12:41.547935 registrar.go:236: INFO Starting Registrar
2022/03/05 03:12:41.548093 sync.go:41: INFO Start sending events to output
2022/03/05 03:12:41.548221 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:12:41.548174 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:12:41.548562 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/05 03:12:41.548634 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:13:01.550333 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/05 03:13:01.550567 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/05 03:13:01.550362 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/05 03:13:01.550578 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/05 03:13:01.550649 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/05 03:13:06.558474 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:06.558511 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:07.566432 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:07.566479 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:09.571310 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:09.571353 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:11.406317 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=76 registrar.writes=1
2022/03/05 03:13:13.591608 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.591643 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:21.602852 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:21.602899 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:37.641377 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:37.641415 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:41.406250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:14:09.654225 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:09.654268 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:11.406345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:14:41.407682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:15:09.661165 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:09.661207 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:11.406433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:15:41.406508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:16:09.667272 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:09.667319 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:11.406278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:16:41.406382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:17:09.677411 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:09.677466 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:11.406316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:17:41.406428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:18:06.563248 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:18:09.684408 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:09.684443 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:18:11.406313 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/05 03:18:41.406207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:19:09.691924 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:09.691963 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:11.406251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:19:41.406362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:20:09.699181 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:09.699223 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:11.406361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:20:41.406371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:21:09.708729 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:09.708928 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:11.406311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:21:41.406295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:22:09.718248 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:09.718291 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:11.406335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:22:41.406586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:23:09.731706 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:09.731747 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:11.406370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:23:41.406261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:24:09.738383 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:09.738440 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:11.406258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:24:41.406277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:25:09.746292 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:09.746335 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:11.406268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:25:41.406262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:26:09.754345 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:09.754417 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:11.406400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:26:41.406314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:27:09.843492 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:09.843565 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:11.406266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:27:41.406304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:28:09.850457 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:09.850514 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:11.406219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:28:41.407987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:29:09.858030 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:09.858064 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:11.406293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:29:41.414123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:09.865508 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:09.865539 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:11.407357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:41.415203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:09.874290 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:09.874326 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:11.406445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:41.406462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:09.890266 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:32:09.890730 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:11.406345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:41.408698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:09.899687 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:33:09.899756 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:33:11.406337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:41.406292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:09.908485 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:09.908601 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:11.406364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:41.406364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:09.918557 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:09.918642 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:11.406312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:41.406264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:09.926745 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:09.926800 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:11.406257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:41.406311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:09.934251 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:09.934286 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:11.406309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:41.406438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:09.947076 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:09.947111 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:11.406288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:41.406325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:09.965071 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:09.965110 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:11.406303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:41.406279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:09.973444 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:09.973530 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:11.406244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:41.406243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:09.981080 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:09.981135 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:11.406247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:41.406440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:09.987642 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:09.987692 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:11.406258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:41.406339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:09.996318 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:09.996351 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:11.406289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:41.406356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:10.003689 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:10.003912 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:11.406302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:41.406323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:10.023392 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:10.023435 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:11.406217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:41.406374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:10.035720 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:10.035760 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:11.406287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:41.406238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:10.045706 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:10.045741 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:11.406325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:41.406365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:10.053755 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:10.053803 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:11.406434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:41.406404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:10.061192 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:10.061232 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:11.406232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:41.406315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:10.074436 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:10.074483 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:11.406282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:41.406324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:10.081998 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:10.082044 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:11.406148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:41.406293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:10.089560 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:10.089611 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:11.406497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:41.406222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:10.096323 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:10.096364 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:11.406314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:41.406365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:10.104587 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:10.104641 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:11.406380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:41.406263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:10.114965 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:10.115011 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:11.406262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:41.406319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:10.123590 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:10.123639 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:11.406457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:41.406377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:10.130950 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:10.131005 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:11.406385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:41.406308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:10.137515 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:10.137585 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:11.406378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:41.406417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:10.153511 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:10.153552 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:11.406330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:41.406331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:10.162239 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:10.162288 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:11.406298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:41.406304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:10.170548 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:10.170605 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:11.406288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:41.406337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:10.177566 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:10.177609 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:11.406408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:41.406309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:10.187496 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:10.187539 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:11.406237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:41.406286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:10.194884 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:10.194939 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:11.406368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:41.406411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:10.203534 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:10.203586 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:11.406319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:41.406356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:10.211744 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:10.211790 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:11.406279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:41.406294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:10.218061 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:10.218099 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:11.406315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:41.406378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:10.226171 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:10.228966 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:11.406281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:41.406381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:10.237330 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:10.237372 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:11.406351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:41.406310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:10.245925 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:10.245982 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:11.406353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:41.406300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:10.254480 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:10.254517 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:11.406354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:41.406354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:10.262760 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:10.262811 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:11.406330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:41.406412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:10.271370 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:10.271412 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:11.406222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:41.406393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:10.282066 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:10.282108 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:11.406329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:41.406306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:10.289473 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:10.289499 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:11.406287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:41.406446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:10.297134 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:10.297211 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:11.406371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:41.406523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:10.601386 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:10.601461 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:11.406540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:41.406239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:11.409369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:37.817921 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:37.817968 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:18:41.408578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:11.406429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:37.847852 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:37.847891 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:41.406330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:11.406305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:37.863309 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:37.863342 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:41.406346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:11.406237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:37.870591 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:37.870651 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:41.406277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:11.406354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:37.877108 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:37.877151 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:41.406286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:11.406272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:37.887816 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:37.887858 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:41.406261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:11.406477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:37.895377 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:37.895426 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:41.406368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:11.406340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:37.903525 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:37.903570 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:41.414076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:11.406253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:37.910441 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:37.910482 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:41.406323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:11.407500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:37.918456 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:37.918500 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:41.406345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:11.406309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:37.925273 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:37.925326 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:41.406373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:11.406370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:37.933636 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:37.933707 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:41.406304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:11.406399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:37.943824 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:37.943866 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:41.406367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:11.406525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:37.951937 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:37.951968 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:41.406282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:11.406307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:37.960154 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:37.960199 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:41.406408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:11.406533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:37.968038 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:37.968101 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:41.406416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:11.406323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:37.978210 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:37.978248 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:41.406373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:11.406353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:37.985906 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:37.986064 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:41.406299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:11.409580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:37.994972 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:37.995029 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:41.406265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:11.406224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:38.003814 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:38.003853 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:41.406240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:11.406382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:38.013940 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:38.013991 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:41.406239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:11.406390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:38.021224 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:38.021258 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:41.406304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:11.406384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:38.030433 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:38.030467 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:41.406326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:11.406373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:38.039565 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:38.039598 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:41.406214 metrics.go:34: INFO No non-zero metrics in the last 30s