Results

          2022/03/15 10:22:26.171442 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/15 10:22:26.171486 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/15 10:22:26.171567 logstash.go:90: INFO Max Retries set to: 3
2022/03/15 10:22:26.171621 metrics.go:23: INFO Metrics logging every 30s
2022/03/15 10:22:26.171620 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/15 10:22:26.171752 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-tpjd7
2022/03/15 10:22:26.171971 async.go:63: INFO Flush Interval set to: 1s
2022/03/15 10:22:26.171997 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/15 10:22:26.172450 beat.go:221: INFO filebeat start running.
2022/03/15 10:22:26.172527 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/15 10:22:26.176768 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/15 10:22:26.176814 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/15 10:22:26.176853 crawler.go:38: INFO Loading Prospectors: 1
2022/03/15 10:22:26.176871 registrar.go:236: INFO Starting Registrar
2022/03/15 10:22:26.176904 sync.go:41: INFO Start sending events to output
2022/03/15 10:22:26.177037 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/15 10:22:26.177125 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/15 10:22:26.177157 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/15 10:22:26.177194 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/15 10:22:46.179391 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/15 10:22:46.179562 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/15 10:22:46.179730 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/15 10:22:46.179795 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/15 10:22:46.179886 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/15 10:22:51.200038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:22:51.200084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:22:52.210331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:22:52.210375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:22:54.214194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:22:54.214240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:22:56.171925 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=64 registrar.writes=1
2022/03/15 10:22:58.221327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:22:58.221367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:23:06.229222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:23:06.229268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:23:22.247817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:23:22.247857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:23:26.172023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:23:54.266542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:23:54.266587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:23:56.171966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:24:26.171940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:24:54.290574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:24:54.290629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:24:56.171984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:25:26.172063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:25:54.311938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:25:54.311976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:25:56.171946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:26:26.172080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:26:54.330798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:26:54.330858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:26:56.172037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:27:26.172053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:27:51.189170 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/15 10:27:51.189261 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/15 10:27:51.189184 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/15 10:27:51.189191 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/15 10:27:54.354224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:27:54.354279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:27:56.172052 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/15 10:27:59.195691 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/15 10:28:26.171968 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/15 10:28:54.372851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:28:54.372928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:28:56.171892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:29:26.171917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:29:54.391422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:29:54.391659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:29:56.171904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:30:26.172000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:30:54.409379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:30:54.409419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:30:56.171989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:31:26.171908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:31:54.427840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:31:54.427889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:31:56.171954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:32:26.172011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:32:54.445350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:32:54.445391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:32:56.171968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:33:26.171921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:33:54.463236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:33:54.463285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:33:56.171936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:34:26.172043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:34:54.477816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:34:54.477851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:34:56.172002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:35:26.174277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:35:54.497182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:35:54.497217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:35:56.171988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:36:26.172022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:36:54.514598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:36:54.514643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:36:56.172002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:37:26.171933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:37:54.532115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:37:54.532150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:37:56.171994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:38:26.172011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:38:54.553757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:38:54.553794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:38:56.171963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:39:26.171923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:39:54.571020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:39:54.571073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:39:56.171991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:40:26.172000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:40:54.588100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:40:54.588147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:40:56.171911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:41:26.171973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:41:54.605651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:41:54.605702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:41:56.171890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:42:26.171984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:42:54.622125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:42:54.622167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:42:56.172239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:43:26.171944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:43:54.638817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:43:54.638860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:43:56.171901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:44:26.171953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:44:54.656716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:44:54.656766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:44:56.172032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:45:26.171945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:45:54.673802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:45:54.673850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:45:56.171974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:46:26.171931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:46:54.695473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:46:54.695512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:46:56.171960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:47:26.172012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:47:54.713529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:47:54.713577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:47:56.171925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:48:26.171901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:48:54.732245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:48:54.732311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:48:56.171931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:49:26.171935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:49:54.748866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:49:54.748903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:49:56.171982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:50:26.171958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:50:54.766517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:50:54.766570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:50:56.172001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:51:26.171963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:51:54.786697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:51:54.786736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:51:56.171940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:52:26.172039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:52:54.805715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:52:54.805753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:52:56.171978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:53:26.171916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:53:54.823042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:53:54.823100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:53:56.171995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:54:26.171950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:54:54.841316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:54:54.841377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:54:56.171974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:55:26.171913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:55:54.857607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:55:54.857769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:55:56.171902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:56:26.171939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:56:54.875664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:56:54.875713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:56:56.172048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:57:26.171978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:57:54.893011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:57:54.893077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:57:56.171971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:58:26.171897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:58:54.911404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:58:54.911451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:58:56.171969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:59:26.171969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 10:59:54.930324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:59:54.930361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 10:59:56.171943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:00:26.171943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:00:54.947980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:00:54.948145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:00:56.172023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:01:26.172154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:01:54.965572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:01:54.965614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:01:56.171919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:02:26.171946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:02:54.984085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:02:54.984164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:02:56.172018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:03:26.171899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:03:55.000853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:03:55.000896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:03:56.171955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:04:26.171926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:04:55.018292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:04:55.018351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:04:56.171932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:05:26.171936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:05:55.037322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:05:55.037379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:05:56.172437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:06:26.171958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:06:55.041300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:06:55.041335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:06:56.171864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:07:26.171919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:07:55.045902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:07:55.045947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:07:56.172011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:08:26.171958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:08:55.052616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:08:55.052666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:08:56.172026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:09:26.172053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:09:55.058092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:09:55.058127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:09:56.171987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:10:26.171955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:10:55.062665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:10:55.062727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:10:56.171978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:11:26.171949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:11:55.069512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:11:55.069792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:11:56.171972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:12:26.172006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:12:55.075333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:12:55.075368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:12:56.171886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:13:26.172057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:13:55.081815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:13:55.081850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:13:56.171931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:14:26.171940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:14:55.089687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:14:55.089748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:14:56.172101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:15:26.172222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:15:55.095859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:15:55.095888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:15:56.171929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:16:26.171944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:16:55.101835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:16:55.101867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:16:56.171984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:17:26.171902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:17:55.107330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:17:55.107362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:17:56.171956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:18:26.171982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:18:55.114800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:18:55.115399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:18:56.171960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:19:26.172024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:19:55.121146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:19:55.121191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:19:56.172062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:20:26.171898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:20:55.127912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:20:55.127961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:20:56.171867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:21:26.171909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:21:55.134389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:21:55.134619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:21:56.171963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:22:26.172094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:22:55.142029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:22:55.142076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:22:56.171961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:23:26.171895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:23:55.147528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:23:55.147573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:23:56.171899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:24:26.171944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:24:55.151859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:24:55.151903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:24:56.172030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:25:26.171988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:25:55.158408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:25:55.158453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:25:56.171990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:26:26.172041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:26:55.163468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:26:55.163501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:26:56.171913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:27:26.172001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:27:55.169671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:27:55.169705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:27:56.171927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:28:26.171903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:28:55.175751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:28:55.175791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:28:56.171911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:29:26.171994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:29:55.181540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:29:55.181590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:29:56.171974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:30:26.172058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:30:55.197315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:30:55.197355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:30:56.171991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:31:26.172003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:31:55.202707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:31:55.202746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:31:56.171977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:32:26.171891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:32:55.208543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:32:55.208593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:32:56.171931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:33:26.171951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:33:55.214280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:33:55.214409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:33:56.171965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:34:26.171915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:34:55.220739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:34:55.220785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:34:56.172154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:35:26.171962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:35:55.227473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:35:55.227513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:35:56.171965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:36:26.171984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:36:55.233087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:36:55.233123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:36:56.171988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:37:26.171917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:37:55.239857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:37:55.240034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:37:56.171945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:38:26.172111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:38:55.245979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:38:55.246029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:38:56.171886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:39:26.171904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:39:55.251982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:39:55.252031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:39:56.171922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:40:26.171925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:40:55.256703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:40:55.256737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:40:56.171955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:41:26.171943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:41:55.262071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:41:55.262120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:41:56.171962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:42:26.172058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:42:55.268623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:42:55.268672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:42:56.172034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:43:26.171944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:43:55.274321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:43:55.274355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:43:56.171987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:44:26.171978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:44:55.282075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:44:55.282122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:44:56.171969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:45:26.171935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:45:55.289233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:45:55.289421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:45:56.171944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:46:26.171885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:46:55.294702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:46:55.294745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:46:56.171935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:47:26.171929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:47:55.301402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:47:55.301455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:47:56.171894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:48:26.171960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:48:55.308551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:48:55.308609 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:48:56.172002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:49:26.172045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:49:55.315093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:49:55.315145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:49:56.171912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:50:26.171918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:50:55.320186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:50:55.320220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:50:56.171867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:51:26.171997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:51:55.325127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:51:55.325183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:51:56.171966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:52:26.172035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:52:55.331181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:52:55.331222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:52:56.171917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:53:26.171994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:53:55.336786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:53:55.336820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:53:56.171942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:54:26.171926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 11:54:55.344093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:54:55.344154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 11:54:56.171928 metrics.go:34: INFO No non-zero metrics in the last 30s