2022/04/02 03:09:51.020675 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/04/02 03:09:51.020864 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:09:51.020881 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:09:51.021232 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:09:51.021403 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:09:51.021722 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-5rn7d
2022/04/02 03:09:51.022068 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:09:51.022141 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:09:51.022962 beat.go:221: INFO filebeat start running.
2022/04/02 03:09:51.023070 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:09:51.027234 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:09:51.027325 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:09:51.027383 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:09:51.027407 registrar.go:236: INFO Starting Registrar
2022/04/02 03:09:51.027451 sync.go:41: INFO Start sending events to output
2022/04/02 03:09:51.027685 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:09:51.027685 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:09:51.027933 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/02 03:09:51.027970 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:10:11.030668 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/02 03:10:11.031179 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/02 03:10:11.031310 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/02 03:10:11.031367 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/02 03:10:11.031385 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/02 03:10:16.051806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:16.051883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:17.056869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:17.056917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:19.062508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:19.062605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:21.021591 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/04/02 03:10:23.069915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:23.070048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:31.076664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:31.076699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:47.095035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:47.095237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:51.022111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:11:19.115196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:11:19.115251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:11:21.021375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:11:51.021389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:12:19.134404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:12:19.134439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:12:21.021417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:12:51.021352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:13:19.156971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:13:19.157032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:13:21.021443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:13:51.021601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:14:19.176058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:14:19.176121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:14:21.021442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:14:51.021405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:15:16.046355 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:16.046505 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:16.046548 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:16.046595 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:19.201086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:15:19.201136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:15:21.021516 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/04/02 03:15:26.050554 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:51.021474 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/04/02 03:16:19.223936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:16:19.223989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:16:21.021398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:16:51.021425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:17:19.243345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:17:19.243402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:17:21.021676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:17:51.021483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:18:19.262664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:18:19.262719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:18:21.021404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:18:51.021449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:19:19.291681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:19:19.291746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:19:21.021399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:19:51.021469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:20:19.313433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:20:19.313499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:20:21.021374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:20:51.021618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:21:19.335875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:21:19.335948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:21:21.021376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:21:51.021428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:22:19.354056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:22:19.354104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:22:21.021467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:22:51.021375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:23:19.373518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:23:19.373560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:23:21.021403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:23:51.021478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:24:19.392565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:24:19.392605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:24:21.021536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:24:51.021446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:25:19.411754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:25:19.411793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:25:21.021501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:25:51.021410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:26:19.439743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:26:19.439784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:26:21.021341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:26:51.021406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:27:19.460695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:27:19.460840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:27:21.021342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:27:51.021561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:19.479464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:28:19.480002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:28:21.021401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:51.021387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:19.499857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:29:19.499894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:29:21.021527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:51.021409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:19.518062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:30:19.518124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:30:21.021445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:51.021330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:19.535740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:31:19.535798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:31:21.021345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:51.021437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:19.554521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:32:19.554662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:32:21.021439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:51.021551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:19.576784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:33:19.576840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:33:21.021410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:51.021463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:19.597083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:34:19.597141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:34:21.021452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:51.021428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:19.616330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:35:19.616390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:35:21.021409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:51.021491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:19.635192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:36:19.635235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:36:21.021335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:51.021447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:19.654858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:37:19.654961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:37:21.021427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:51.021413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:19.674798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:38:19.674866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:38:21.021488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:51.021406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:19.697339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:39:19.697392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:39:21.021501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:51.021531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:19.715539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:40:19.715594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:40:21.021479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:51.021459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:19.734846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:41:19.734910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:41:21.021542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:51.021548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:19.752107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:42:19.752158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:42:21.021482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:51.021370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:19.770317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:43:19.770361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:43:21.021512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:51.021372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:19.787516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:44:19.787565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:44:21.021430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:51.021403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:19.805689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:45:19.805732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:45:21.021593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:51.021503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:19.823187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:46:19.823221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:46:21.021418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:51.021470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:19.842406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:47:19.842769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:47:21.021553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:51.021389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:19.860492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:48:19.860533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:48:21.021305 metrics.go:34: INFO No non-zero metrics in the last 30s