By type
2022/03/31 03:24:40.771610 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/31 03:24:40.771668 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/31 03:24:40.771785 logstash.go:90: INFO Max Retries set to: 3
2022/03/31 03:24:40.771879 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/31 03:24:40.772007 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-cwqbx
2022/03/31 03:24:40.772239 async.go:63: INFO Flush Interval set to: 1s
2022/03/31 03:24:40.772262 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/31 03:24:40.772611 beat.go:221: INFO filebeat start running.
2022/03/31 03:24:40.772662 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/31 03:24:40.773601 metrics.go:23: INFO Metrics logging every 30s
2022/03/31 03:24:40.778609 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/31 03:24:40.778711 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/31 03:24:40.778747 crawler.go:38: INFO Loading Prospectors: 1
2022/03/31 03:24:40.778951 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/31 03:24:40.779034 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/31 03:24:40.779090 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/31 03:24:40.779102 registrar.go:236: INFO Starting Registrar
2022/03/31 03:24:40.779134 sync.go:41: INFO Start sending events to output
2022/03/31 03:24:40.779181 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/31 03:24:40.779790 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/31 03:25:10.774120 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/03/31 03:25:40.773931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:26:10.773986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:26:40.773950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:27:10.773942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:27:40.774134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:28:10.773898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:28:40.774027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:29:10.773947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:29:40.773906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:29:45.798736 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/31 03:30:10.774001 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/31 03:30:40.773931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:31:10.773964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:31:40.773895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:32:10.773978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:32:40.773964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:33:10.773881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:33:40.773968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:34:10.773914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:34:40.773936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:35:10.774087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:35:40.773903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:36:10.773906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:36:40.773910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:37:10.773880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:37:40.773961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:38:10.773891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:38:40.773902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:39:10.773965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:39:40.773906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:40:10.774006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:40:40.773942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:41:10.773956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:41:40.774003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:42:10.773890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:42:40.773941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:43:10.773962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:43:40.773935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:44:10.774017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:44:40.773982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:45:10.773872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:45:40.773880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:46:10.774003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:46:40.773940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:47:10.773876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:47:40.773998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:48:10.773932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:48:40.773864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:49:10.774138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:49:40.774100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:50:10.773867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:50:40.773931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:51:10.773851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:51:40.773917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:51:50.926207 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/31 03:51:55.951556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:51:55.951597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:51:56.955022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:51:56.955112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:51:58.958672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:51:58.958721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:02.967819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:02.968232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:10.774011 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/03/31 03:52:10.974204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:10.974352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:26.993881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:26.993936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:40.773912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:52:59.011663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:59.011704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:53:10.773959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:53:40.773949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:53:59.029425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:53:59.029496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:54:10.773880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:54:40.773874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:54:59.048614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:54:59.048679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:55:10.773886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:55:40.773870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:55:59.065822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:55:59.065872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:56:10.775067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:56:40.773876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:56:55.940287 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/31 03:56:59.084819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:56:59.084868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:57:10.773894 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/31 03:57:40.774007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:57:59.101935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:57:59.102072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:58:10.773922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:58:40.774121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:58:59.120265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:58:59.120345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:59:10.773987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:59:40.773989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:59:59.136764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:59:59.136806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:00:10.773860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:00:40.773874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:00:59.154329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:00:59.154376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:01:10.773947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:01:40.773871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:01:59.171149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:01:59.171234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:02:10.775391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:02:40.773891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:02:59.201726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:02:59.201772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:03:10.774793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:03:40.773891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:03:59.220922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:03:59.221007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:04:10.773951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:04:40.773909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:04:59.240472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:04:59.240538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:05:10.773978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:05:40.773949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:05:59.259103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:05:59.259146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:06:10.773913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:06:40.773965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:07:01.279119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:07:01.279232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:07:10.773924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:07:40.773978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:08:01.296414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:08:01.296455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:08:10.773934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:08:40.774096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:09:01.315307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:09:01.315349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:09:10.773930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:09:40.773906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:10:01.338843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:10:01.338889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:10:10.774020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:10:40.773979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:11:01.357231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:11:01.357268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:11:10.774099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:11:40.773953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:12:01.377482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:12:01.377790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:12:10.774020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:12:40.774032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:13:01.396526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:13:01.396576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:13:10.773918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:13:40.773928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:14:01.422506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:14:01.422549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:14:10.773931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:14:40.774107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:15:01.439717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:15:01.439753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:15:10.773887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:15:40.773914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:16:01.467399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:16:01.467502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:16:10.773972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:16:40.773887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:17:01.485440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:17:01.485563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:17:10.773855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:17:40.774046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:18:01.504209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:18:01.504433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:18:10.774014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:18:40.773852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:19:01.522853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:19:01.522884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:19:10.774020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:19:40.773947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:20:01.541568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:20:01.541627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:20:10.773945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:20:40.773914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:21:01.559294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:21:01.559349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:21:10.773944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:21:40.773973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:22:01.576845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:22:01.576884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:22:10.773892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:22:40.774959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:23:01.597940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:23:01.598000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:23:10.773892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:23:40.773898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:24:01.615265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:24:01.615306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:24:10.773918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:24:40.773941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:25:01.632815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:25:01.632853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:25:10.773957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:25:40.773961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:26:01.649489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:26:01.649526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:26:10.774076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:26:40.773928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:27:01.667827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:27:01.667880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:27:10.774009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:27:40.773921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:28:01.684299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:28:01.684340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:28:10.774027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:28:40.773964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:29:01.700889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:29:01.700931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:29:10.773957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:29:40.773999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:30:01.718993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:30:01.719030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:30:10.773946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:30:40.773885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:31:01.736358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:31:01.736518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:31:10.773966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:31:40.773961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:32:01.752959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:32:01.752999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:32:10.773899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:32:40.774040 metrics.go:34: INFO No non-zero metrics in the last 30s