2022/02/07 02:43:17.854105 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/02/07 02:43:17.854154 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/07 02:43:17.854231 logstash.go:90: INFO Max Retries set to: 3
2022/02/07 02:43:17.854299 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/07 02:43:17.854411 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-5vsbz
2022/02/07 02:43:17.854635 async.go:63: INFO Flush Interval set to: 1s
2022/02/07 02:43:17.854659 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/07 02:43:17.855276 beat.go:221: INFO filebeat start running.
2022/02/07 02:43:17.855338 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/07 02:43:17.855449 metrics.go:23: INFO Metrics logging every 30s
2022/02/07 02:43:18.121500 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/07 02:43:18.121567 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/07 02:43:18.121640 crawler.go:38: INFO Loading Prospectors: 1
2022/02/07 02:43:18.121665 registrar.go:236: INFO Starting Registrar
2022/02/07 02:43:18.121732 sync.go:41: INFO Start sending events to output
2022/02/07 02:43:18.121835 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/07 02:43:18.121874 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/07 02:43:18.121966 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/02/07 02:43:18.122014 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/07 02:43:38.127079 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/02/07 02:43:38.127186 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/02/07 02:43:38.127327 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/02/07 02:43:38.127389 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/02/07 02:43:38.127430 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/02/07 02:43:43.134370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:43.134396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:44.137468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:44.137508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:46.141061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:46.141161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:47.855815 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/02/07 02:43:50.149076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:50.149123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:58.170557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:43:58.170587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:14.177524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:14.177570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:17.855822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:44:46.183817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:46.183844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:47.855735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:45:17.855816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:45:46.190002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:45:46.190201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:45:47.855807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:46:17.855843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:46:46.197384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:46:46.197425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:46:47.855833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:47:17.855781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:47:46.205335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:47:46.205370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:47:47.855775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:48:17.855786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:48:43.137850 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/07 02:48:46.212671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:48:46.212783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:48:47.855781 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/07 02:49:17.855855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:49:46.218919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:49:46.218955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:49:47.855849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:50:17.855708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:50:46.225187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:50:46.225223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:50:47.855909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:51:17.855742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:51:46.231743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:51:46.231770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:51:47.855887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:52:17.855837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:52:46.237522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:52:46.237550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:52:47.855698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:53:17.855721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:53:46.244512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:53:46.244544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:53:47.855866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:54:17.855711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:54:46.252674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:54:46.252723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:54:47.855841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:55:17.855774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:55:46.261108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:55:46.261168 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:55:47.855887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:56:17.855787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:56:46.268709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:56:46.268759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:56:47.855889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:57:17.855766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:57:46.276722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:57:46.276750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:57:47.855767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:58:17.855782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:58:46.283830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:58:46.283861 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:58:47.855735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:59:17.855759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:59:46.290276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:59:46.290324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:59:47.855740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:00:17.855744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:00:46.297434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:00:46.297468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:00:47.855755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:01:17.855845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:01:46.303876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:01:46.303912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:01:47.855748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:02:17.855759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:02:46.310737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:02:46.310765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:02:47.855724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:03:17.855768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:03:46.318399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:03:46.318431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:03:47.855765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:04:17.855782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:04:46.325233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:04:46.325264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:04:47.855763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:05:17.855816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:05:46.332307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:05:46.332338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:05:47.855769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:06:17.855770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:06:46.339032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:06:46.339069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:06:47.855812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:07:17.855774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:07:46.345493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:07:46.345528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:07:47.855788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:08:17.855783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:08:46.352763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:08:46.352797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:08:47.855820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:09:17.855708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:09:46.360647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:09:46.360684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:09:47.855859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:10:17.855911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:10:46.367716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:10:46.367752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:10:47.855802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:11:17.855854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:11:46.375227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:11:46.375256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:11:47.855812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:12:17.855762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:12:46.382470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:12:46.382514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:12:47.855859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:13:17.855769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:13:46.389149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:13:46.389191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:13:47.855719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:14:17.855811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:14:46.395773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:14:46.395800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:14:47.855847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:15:17.855812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:15:46.403210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:15:46.403246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:15:47.855762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:16:17.855866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:16:46.409964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:16:46.409992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:16:47.855759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:17:17.855763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:17:46.416359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:17:46.416391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:17:47.855729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:18:17.855890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:18:46.423502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:18:46.423528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:18:47.855825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:19:17.855747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:19:46.430747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:19:46.430783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:19:47.855787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:20:17.855748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:20:46.437336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:20:46.437439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:20:47.855742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:21:17.855792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:21:46.444704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:21:46.444735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:21:47.855855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:22:17.855764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:22:46.451014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:22:46.451052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:22:47.855761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:23:17.855788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:23:46.458118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:23:46.458158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:23:47.855755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:24:17.855775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:24:46.465532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:24:46.465556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:24:47.855875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:25:17.855839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:25:46.472397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:25:46.472650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:25:47.855769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:26:17.855841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:26:46.480055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:26:46.480133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:26:47.855799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:27:17.855743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:27:46.486747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:27:46.486774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:27:47.855840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:28:17.855816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:28:46.494780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:28:46.494834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:28:47.855839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:29:17.855779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:29:46.504111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:29:46.504148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:29:47.855729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:30:17.855759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:30:46.511328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:30:46.511360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:30:47.855749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:31:17.855847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:31:46.518595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:31:46.518628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:31:47.855796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:32:17.855783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:32:46.525179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:32:46.525225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:32:47.855743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:33:17.855906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:33:46.531812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:33:46.531838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:33:47.855750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:34:17.855755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:34:46.539350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:34:46.539396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:34:47.855765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:35:17.855819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:35:46.546193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:35:46.546229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:35:47.855838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:36:17.855779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:36:46.553221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:36:46.553256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:36:47.855805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:37:17.855805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:37:46.559903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:37:46.559946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:37:47.855778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:38:17.855791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:38:46.566119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:38:46.566158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:38:47.855743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:39:17.855759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:39:46.572717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:39:46.572746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:39:47.855796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:40:17.855839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:40:46.578880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:40:46.578904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:40:47.855749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:41:17.855751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:41:46.584933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:41:46.584970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:41:47.855793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:42:17.855840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:42:46.591568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:42:46.591701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:42:47.855735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:43:17.855779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:43:46.598572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:43:46.598764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:43:47.855798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:44:17.855841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:44:46.607434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:44:46.607481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:44:47.855814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:45:17.855792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:45:46.620508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:45:46.620537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:45:47.855730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:46:17.855792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:46:46.627716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:46:46.627837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:46:47.855716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:47:17.855744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:47:46.634531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:47:46.634568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:47:47.855752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:48:17.855779 metrics.go:34: INFO No non-zero metrics in the last 30s