2022/03/10 06:27:18.109548 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/10 06:27:18.109596 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 06:27:18.109665 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 06:27:18.109670 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 06:27:18.109774 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 06:27:18.109885 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-c5l6t
2022/03/10 06:27:18.110049 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 06:27:18.110067 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 06:27:18.110429 beat.go:221: INFO filebeat start running.
2022/03/10 06:27:18.110491 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 06:27:18.237668 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 06:27:18.237768 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 06:27:18.237814 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 06:27:18.237847 registrar.go:236: INFO Starting Registrar
2022/03/10 06:27:18.238014 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 06:27:18.237952 sync.go:41: INFO Start sending events to output
2022/03/10 06:27:18.238020 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 06:27:18.238116 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/10 06:27:18.238136 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 06:27:18.238731 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/10 06:27:18.238772 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/10 06:27:18.238808 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/10 06:27:18.238851 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/10 06:27:18.238789 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/10 06:27:18.280617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:18.280659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:19.284930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:19.284973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:21.290343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:21.290400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:25.296947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:25.296976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:33.303666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:33.303705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:48.110032 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=2043 registrar.writes=1
2022/03/10 06:27:49.310136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:27:49.310167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:28:18.109938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:28:21.316989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:28:21.317100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:28:48.109943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:29:18.109910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:29:21.324629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:29:21.324670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:29:48.109880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:30:18.109886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:30:21.332109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:30:21.332143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:30:48.109930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:31:18.109940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:31:21.338773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:31:21.338818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:31:48.109956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:32:18.109849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:32:21.346541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:32:21.347596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:32:23.247061 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/10 06:32:48.109984 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/10 06:33:18.109957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:33:21.355307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:33:21.355346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:33:48.110033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:34:18.109908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:34:21.362117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:34:21.362156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:34:48.109990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:35:18.109927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:35:21.371375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:35:21.371415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:35:48.109894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:36:18.109936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:36:21.378976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:36:21.379007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:36:48.109911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:37:18.109875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:37:21.387239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:37:21.387286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:37:48.109902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:38:18.109958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:38:21.395117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:38:21.395159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:38:48.109861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:39:18.109911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:39:21.405817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:39:21.405866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:39:48.109934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:40:18.109863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:40:21.413321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:40:21.413360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:40:48.109909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:41:18.110818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:41:21.421583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:41:21.421618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:41:48.109992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:42:18.110062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:42:21.428825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:42:21.428861 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:42:48.109948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:43:18.109970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:43:21.440820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:43:21.440865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:43:48.109978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:44:18.109988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:44:21.448618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:44:21.448652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:44:48.109943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:45:18.109930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:45:21.457353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:45:21.457384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:45:48.109932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:46:18.109931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:46:21.464110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:46:21.464143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:46:48.109944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:47:18.109904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:47:21.472740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:47:21.472782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:47:48.109915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:48:18.110005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:48:21.478739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:48:21.478774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:48:48.109905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:49:18.109944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:49:21.488035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:49:21.488084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:49:48.109918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:50:18.109963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:50:21.494700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:50:21.494735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:50:48.109919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:51:18.109945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:51:21.503893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:51:21.503922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:51:48.109983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:52:18.110053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:52:21.510589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:52:21.510641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:52:48.110058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:53:18.109944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:53:21.519635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:53:21.519668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:53:48.109919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:54:18.109906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:54:21.527891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:54:21.527930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:54:48.109931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:55:18.109944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:55:21.535361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:55:21.535394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:55:48.109985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:56:18.109914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:56:21.542889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:56:21.542943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:56:48.109938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:57:18.109940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:57:21.554881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:57:21.554925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:57:48.109954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:58:18.109907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:58:21.564207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:58:21.564245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:58:48.109946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:59:18.109932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 06:59:21.573573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:59:21.573600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 06:59:48.109917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:00:18.109910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:00:21.579627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:00:21.579670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:00:48.109918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:01:18.109920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:01:21.588652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:01:21.588845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:01:48.109954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:02:18.109979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:02:21.596891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:02:21.596933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:02:48.109931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:03:18.109981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:03:21.606317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:03:21.606350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:03:48.109925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:04:18.109860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:04:21.613605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:04:21.613637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:04:48.109902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:05:18.109971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:05:21.621639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:05:21.621666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:05:48.109890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:06:18.109919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:06:21.629421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:06:21.629467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:06:48.109877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:07:18.109902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:07:21.640908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:07:21.640934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:07:48.109881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:08:18.109887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:08:21.647822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:08:21.647864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:08:48.109887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:09:18.109916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:09:21.658239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:09:21.658266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:09:48.109940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:10:18.109968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:10:21.664942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:10:21.664973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:10:48.109945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:11:18.110031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:11:21.677055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:11:21.677085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:11:48.109900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:12:18.110049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:12:21.683684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:12:21.683716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:12:48.109942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:13:18.109941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:13:21.692587 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:13:21.692617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:13:48.109901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:14:18.109966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:14:21.699598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:14:21.699630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:14:48.109887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:15:18.109912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:15:21.709821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:15:21.709855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:15:48.109904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:16:18.109909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:16:21.716715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:16:21.716773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:16:48.109875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:17:18.109903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:17:21.730571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:17:21.730605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:17:48.109869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:18:18.109871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:18:21.737343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:18:21.737373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:18:48.109937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:19:18.109924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 07:19:21.744516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 07:19:21.744548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host