By type
2022/03/14 03:18:12.398359 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/14 03:18:12.398437 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/14 03:18:12.398532 metrics.go:23: INFO Metrics logging every 30s
2022/03/14 03:18:12.398638 logstash.go:90: INFO Max Retries set to: 3
2022/03/14 03:18:12.398737 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/14 03:18:12.398881 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-5l7jg
2022/03/14 03:18:12.401682 async.go:63: INFO Flush Interval set to: 1s
2022/03/14 03:18:12.401728 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/14 03:18:12.402803 beat.go:221: INFO filebeat start running.
2022/03/14 03:18:12.402969 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/14 03:18:12.408244 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/14 03:18:12.408351 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/14 03:18:12.408418 crawler.go:38: INFO Loading Prospectors: 1
2022/03/14 03:18:12.409055 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/14 03:18:12.409196 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/14 03:18:12.409226 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/14 03:18:12.409257 registrar.go:236: INFO Starting Registrar
2022/03/14 03:18:12.409294 sync.go:41: INFO Start sending events to output
2022/03/14 03:18:12.409339 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/14 03:18:12.410051 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/14 03:18:42.399425 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/14 03:19:12.398894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:42.398945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:12.398864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:42.398981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:12.398836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:42.398951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:12.399009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:42.398896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:12.399013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:17.421316 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/14 03:23:42.399083 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/14 03:24:12.398897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:42.398893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:12.398978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:42.398936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:12.399004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:42.398939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:12.398919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:42.398948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:12.398955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:42.398822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:12.398879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:42.398930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:12.398894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:42.402662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:12.398960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:42.398883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:12.398879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:42.398901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:12.398883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:42.398979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:12.398882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:42.398857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:12.398895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:42.398882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:12.398983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:42.398958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:12.398900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:42.398905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:12.398919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:42.398875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:12.398872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:42.398837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:12.398909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:42.398849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:12.398869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:42.398941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:12.398890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:42.398951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:12.398915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:42.398847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:12.398855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:42.398832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:12.398936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:42.398829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:12.398841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:42.398898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:12.398807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:42.398867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:52.580255 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/14 03:47:57.550601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:57.550651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:58.556408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:58.556503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:00.560274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:00.560313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:04.567460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:04.567528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:12.398839 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/14 03:48:12.573360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:12.573411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:28.595226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:28.595273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:42.398845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:00.620189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:00.620243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:12.398869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:42.398857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:00.639580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:00.639626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:12.398912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:42.398858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:00.661455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:00.661514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:12.398973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:42.398850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:00.683905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:00.683978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:12.399173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:42.398887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:57.603037 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/14 03:53:00.702923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:00.702976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:12.399022 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/14 03:53:42.398930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:00.722811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:00.722874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:12.398912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:42.398857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:00.742186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:00.742248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:12.398842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:42.398944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:00.761164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:00.761240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:12.398825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:42.399020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:00.781521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:00.781568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:12.398944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:42.399028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:00.805963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:00.806280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:12.399106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:42.398949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:00.826913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:00.826958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:12.398861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:42.398849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:00.848050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:00.848109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:12.398866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:42.398845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:00.869809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:00.869871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:12.398881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:42.398915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:00.892206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:00.892240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:12.398942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:42.400267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:00.913891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:00.914044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:12.399113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:42.398864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:00.936232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:00.936288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:12.398869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:42.398867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:00.959777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:00.959821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:12.398976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:42.401116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:00.980386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:00.980438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:12.399005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:42.398829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:01.001498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:01.001531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:12.398921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:42.398938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:01.023386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:01.023418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:12.398903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:42.398844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:01.042979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:01.043030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:12.399795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:42.398876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:01.062220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:01.062338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:12.398906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:42.400830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:01.080634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:01.080692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:12.398834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:42.399054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:01.101547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:01.101586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:12.399088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:42.398896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:01.129381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:01.129974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:12.398832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:42.398857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:01.149741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:01.149781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:12.399498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:42.398883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:01.168156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:01.168224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:12.398894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:42.398994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:01.191445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:01.191514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:12.398921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:42.398875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:01.210513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:01.210648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:12.398866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:42.398885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:01.231631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:01.231660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:12.398901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:42.398872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:01.253280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:01.253342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:12.398942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:42.398835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:01.272593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:01.272636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:12.398904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:42.398874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:01.292262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:01.292304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:12.398872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:42.398865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:01.313582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:01.313625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:12.398909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:42.398943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:01.336786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:01.336837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:12.398879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:42.399031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:01.357714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:01.357764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:12.398857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:42.398883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:01.376160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:01.376211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:12.398873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:42.398813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:01.395757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:01.395797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:12.398906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:42.398786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:01.415945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:01.415990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:12.398950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:42.398909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:01.443415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:01.443474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:12.398883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:42.398885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:01.460403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:01.460530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:12.398819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:42.402397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:01.477889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:01.477931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:12.399081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:42.399295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:01.498511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:01.498569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:12.399293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:42.400101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:01.517818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:01.517887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:12.398837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:42.398853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:01.544167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:01.544379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:12.398921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:42.398949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:01.566302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:01.566387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:12.398925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:42.398886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:01.588343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:01.588536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:12.398825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:42.398971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:36:01.608787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:01.608833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:12.398849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:36:42.398838 metrics.go:34: INFO No non-zero metrics in the last 30s