2022/01/06 03:05:02.265002 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/01/06 03:05:02.265038 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/06 03:05:02.265116 logstash.go:90: INFO Max Retries set to: 3
2022/01/06 03:05:02.265160 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/06 03:05:02.265268 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-kfs4l
2022/01/06 03:05:02.265305 metrics.go:23: INFO Metrics logging every 30s
2022/01/06 03:05:02.265432 async.go:63: INFO Flush Interval set to: 1s
2022/01/06 03:05:02.265447 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/06 03:05:02.265797 beat.go:221: INFO filebeat start running.
2022/01/06 03:05:02.265916 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/06 03:05:02.291619 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/06 03:05:02.291783 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/06 03:05:02.291860 crawler.go:38: INFO Loading Prospectors: 1
2022/01/06 03:05:02.292022 registrar.go:236: INFO Starting Registrar
2022/01/06 03:05:02.292058 sync.go:41: INFO Start sending events to output
2022/01/06 03:05:02.292219 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/06 03:05:02.292221 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/06 03:05:02.292404 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/06 03:05:02.292478 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/06 03:05:12.294803 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/06 03:05:12.294960 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/06 03:05:12.295088 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/06 03:05:12.295162 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/06 03:05:12.295284 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/06 03:05:17.312244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:17.312289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:18.316690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:18.316737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:20.324862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:20.324895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:24.334868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:24.334923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:32.265916 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=72 registrar.writes=1
2022/01/06 03:05:32.347103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:32.347144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:48.355106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:05:48.355158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:06:02.265928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:06:20.450906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:06:20.450992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:06:32.265708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:07:02.265726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:07:20.460668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:07:20.460706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:07:32.265704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:08:02.265709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:08:20.471526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:20.471584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:32.265720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:09:02.265717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:09:20.480610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:09:20.480673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:09:32.265762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:10:02.265913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:10:17.311428 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/06 03:10:20.494698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:10:20.494737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:10:32.265729 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/06 03:11:02.265703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:11:20.504756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:11:20.504802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:11:32.265743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:12:02.265881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:12:20.515295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:12:20.515351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:12:32.266201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:13:02.265648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:13:20.527310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:13:20.527360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:13:32.265757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:14:02.265732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:14:20.535598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:14:20.535624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:14:32.265811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:15:02.265625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:15:20.545904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:15:20.545966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:15:32.265788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:16:02.265792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:16:20.555391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:16:20.555459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:16:32.265700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:17:02.266860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:17:20.564056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:17:20.564125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:17:32.265775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:18:02.265766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:18:20.574069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:18:20.574100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:18:32.265782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:19:02.265819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:19:20.583704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:19:20.583768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:19:32.265790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:20:02.265825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:20:20.594772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:20:20.594827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:20:32.265690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:21:02.265675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:21:20.603966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:21:20.604031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:21:32.265848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:22:02.265817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:22:20.619044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:22:20.619076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:22:32.265801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:23:02.265736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:23:20.629249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:23:20.629293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:23:32.265655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:24:02.265704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:24:20.636991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:24:20.637038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:24:32.265663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:25:02.265624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:25:20.647513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:25:20.647556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:25:32.265769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:26:02.265666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:26:20.658716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:26:20.658751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:26:32.265704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:27:02.265824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:27:20.669450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:27:20.669508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:27:32.265670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:28:02.265792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:28:20.678983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:28:20.679049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:28:32.265847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:29:02.265844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:29:20.687794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:29:20.687842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:29:32.265857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:30:02.265837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:30:20.698635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:30:20.698680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:30:32.265717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:31:02.265722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:31:20.709277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:31:20.709330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:31:32.265649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:32:02.265748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:32:20.719534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:32:20.719559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:32:32.265747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:33:02.265767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:33:20.729541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:33:20.729599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:33:32.265716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:34:02.265618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:34:20.741458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:34:20.741489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:34:32.265724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:35:02.265679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:35:20.750915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:35:20.751073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:35:32.265711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:36:02.265758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:36:20.760269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:36:20.760303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:36:32.265763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:37:02.265839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:37:20.769281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:37:20.769323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:37:32.265784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:38:02.265794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:38:20.779285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:38:20.779337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:38:32.265856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:39:02.265742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:39:20.789004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:39:20.789053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:39:32.265670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:40:02.265725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:40:20.800800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:40:20.800881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:40:32.265598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:41:02.265796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:41:20.812241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:41:20.812320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:41:32.265838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:42:02.265740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:42:20.823760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:42:20.823824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:42:32.265553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:43:02.265760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:43:20.834086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:43:20.834136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:43:32.265706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:44:02.265697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:44:20.846513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:44:20.846571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:44:32.265818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:45:02.265635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:45:20.856750 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:45:20.856787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:45:32.265779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:46:02.265820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:46:20.866991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:46:20.867021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:46:32.265673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:47:02.265669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:47:20.876489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:47:20.876561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:47:32.265723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:48:02.265747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:48:20.885791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:48:20.885833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:48:32.265799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:49:02.265801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:49:20.894351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:49:20.894391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:49:32.265813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:50:02.265755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:50:20.902650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:50:20.902682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:50:32.265788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:51:02.265903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:51:20.912611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:51:20.912657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:51:32.265733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:52:02.265657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:52:20.922808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:52:20.922851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:52:32.265698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:53:02.265728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:53:20.932790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:53:20.932840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:53:32.265691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:54:02.265782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:54:20.943392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:54:20.943446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:54:32.265751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:55:02.265686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:55:20.952501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:55:20.952549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:55:32.265767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:56:02.265719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:56:20.962104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:56:20.962138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:56:32.265739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:57:02.265671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:57:20.971286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:57:20.971333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:57:32.265756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:58:02.265710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:58:20.980401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:58:20.980436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:58:32.265662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:59:02.265834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:59:20.989873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:59:20.989913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:59:32.265771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:00:02.265825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:00:20.999632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:00:20.999678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:00:32.265827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:01:02.265718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:01:21.008650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:01:21.008715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:01:32.265705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:02:02.265818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:02:21.020263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:02:21.020308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:02:32.265635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:03:02.265970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:03:21.029417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:03:21.029456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:03:32.265736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:04:02.265772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:04:21.038385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:04:21.038445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:04:32.265910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:05:02.265751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:05:21.048411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:05:21.048485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:05:32.265827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:06:02.265693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:06:21.060397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:06:21.060477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:06:32.265769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:07:02.265715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:07:21.071505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:07:21.071553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:07:32.265701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:08:02.265775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:08:21.081083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:08:21.081188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:08:32.265668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:09:02.265688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:09:21.090928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:09:21.090977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:09:32.265740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:10:02.265708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:10:21.099393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:10:21.099431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:10:32.265678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:11:02.265732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:11:21.108762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:11:21.108807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:11:32.265662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:12:02.265749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:12:21.121490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:12:21.121555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:12:32.265695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:13:02.265670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:13:21.130344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:13:21.130382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:13:32.265692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:14:02.265795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:14:21.139100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:14:21.139172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:14:32.265737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:15:02.265738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:15:21.147941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:15:21.147980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:15:32.265635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:16:02.265692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:16:21.158004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:16:21.158053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:16:32.265641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:17:02.265730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:17:21.168414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:17:21.168465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:17:32.265706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:18:02.265816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:18:21.177649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:18:21.177696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:18:32.265709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:19:02.265791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:19:21.185789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:19:21.185819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:19:32.265684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:20:02.265785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:20:21.196976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:20:21.197026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:20:32.265757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:21:02.265711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:21:21.208140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:21:21.208205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:21:32.265638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:22:02.265748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:22:21.220319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:22:21.220366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:22:32.265764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:23:02.265847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:23:21.230042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:23:21.230089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:23:32.265782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:24:02.265690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:24:21.240134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:24:21.240179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:24:32.265817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:25:02.265860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:25:21.249155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:25:21.249196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:25:32.265851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:26:02.265707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:26:21.257886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:26:21.257939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:26:32.265754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:27:02.265828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:27:21.267240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:27:21.267281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:27:32.265709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:28:02.265740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:28:21.277082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:28:21.277124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:28:32.265759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:29:02.265712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:29:21.293073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:29:21.293122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:29:32.265798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:30:02.265738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:30:21.304510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:30:21.304549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:30:32.265673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:31:02.265690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:31:21.314835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:31:21.314896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:31:32.265862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:32:02.265645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:32:21.324510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:32:21.324553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host