2022/03/05 03:11:12.312308 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:11:12.312378 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:11:12.312496 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:11:12.312592 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:11:12.312724 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-69q7z
2022/03/05 03:11:12.312985 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:11:12.313009 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:11:12.313497 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:11:12.313593 beat.go:221: INFO filebeat start running.
2022/03/05 03:11:12.313645 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:11:12.316888 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:11:12.316951 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:11:12.316987 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:11:12.317135 registrar.go:236: INFO Starting Registrar
2022/03/05 03:11:12.317121 sync.go:41: INFO Start sending events to output
2022/03/05 03:11:12.317210 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:11:12.317275 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:11:12.317356 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/05 03:11:12.317395 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:11:12.318956 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/05 03:11:12.319051 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/05 03:11:12.319261 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/05 03:11:12.319339 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/05 03:11:12.319418 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/05 03:11:17.340738 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:11:17.340826 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:11:18.349724 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:11:18.350016 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:11:20.353361 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:11:20.353665 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:11:24.368878 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:11:24.368942 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:11:32.382383 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:11:32.382422 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:11:42.313870 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:11:48.399541 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:11:48.399581 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:12.313722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:12:20.419607 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:20.419644 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:42.313858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:13:12.313723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:13:20.441788 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:20.441819 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:42.313752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:14:12.313920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:14:20.463393 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:20.463468 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:42.313755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:15:12.313755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:15:20.495607 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:20.495637 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:42.313767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:16:12.313793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:16:17.347695 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:16:20.515115 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:20.515160 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:42.313865 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/05 03:17:12.313781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:17:20.534755 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:20.534807 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:42.313763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:18:12.313733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:18:20.559532 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:20.559592 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:42.313765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:19:12.313906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:19:20.582424 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:20.582456 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:42.313786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:20:12.313683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:20:20.603531 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:20.603564 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:42.313798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:21:12.313758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:21:20.623885 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:20.623920 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:42.313785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:22:12.313950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:22:20.643585 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:20.643633 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:42.313832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:23:12.313822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:23:20.665315 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:20.665359 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:42.313800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:24:12.313755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:24:20.685653 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:20.685691 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:42.313901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:25:12.313868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:25:20.707576 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:20.707608 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:42.313781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:26:12.313805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:26:20.732502 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:20.732674 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:42.313792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:27:12.313792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:27:20.758437 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:20.758750 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:42.313784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:28:12.313846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:28:20.779159 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:20.779200 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:42.313791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:29:12.313953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:29:20.812043 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:20.812092 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:42.313693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:12.313734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:20.831577 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:20.831612 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:42.313807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:12.313810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:20.856089 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:20.856122 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:42.313751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:12.313780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:20.874585 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:20.874625 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:42.313885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:12.313740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:20.892799 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:20.892995 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:42.313768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:12.313780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:20.912913 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:20.912949 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:42.313729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:12.313932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:20.931669 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:20.931699 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:42.313745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:12.313684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:20.951227 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:20.951259 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:42.313788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:12.313772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:20.968982 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:20.969015 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:42.313838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:12.313942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:20.992294 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:20.992327 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:42.313830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:12.313780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:21.019819 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:21.019855 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:42.313806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:12.313790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:21.040116 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:21.040154 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:42.313820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:12.313814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:21.059230 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:21.059266 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:42.313851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:12.313749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:21.078640 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:21.078693 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:42.313767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:12.313769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:21.100967 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:21.101001 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:42.313742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:12.313763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:21.123372 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:21.123404 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:42.313914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:12.313972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:21.145619 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:21.145652 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:42.313748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:12.313784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:21.172555 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:21.172613 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:42.313835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:12.313776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:21.191600 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:21.191628 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:42.313881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:12.313861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:21.215633 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:21.215666 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:42.313844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:12.313747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:21.244072 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:21.244119 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:42.313734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:12.313710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:21.263347 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:21.263403 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:42.313973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:12.313807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:21.283532 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:21.283569 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:42.313868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:12.313886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:21.304710 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:21.304786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host