2022/03/26 03:14:29.968482 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/26 03:14:29.968566 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/26 03:14:29.968680 metrics.go:23: INFO Metrics logging every 30s
2022/03/26 03:14:29.968699 logstash.go:90: INFO Max Retries set to: 3
2022/03/26 03:14:29.969520 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/26 03:14:29.969790 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-wsdt7
2022/03/26 03:14:29.970201 async.go:63: INFO Flush Interval set to: 1s
2022/03/26 03:14:29.970229 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/26 03:14:29.970954 beat.go:221: INFO filebeat start running.
2022/03/26 03:14:29.971052 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/26 03:14:29.976276 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/26 03:14:29.976371 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/26 03:14:29.976442 crawler.go:38: INFO Loading Prospectors: 1
2022/03/26 03:14:29.976526 registrar.go:236: INFO Starting Registrar
2022/03/26 03:14:29.976593 sync.go:41: INFO Start sending events to output
2022/03/26 03:14:29.976684 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/26 03:14:29.976686 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/26 03:14:29.976806 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/26 03:14:29.976840 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/26 03:14:29.977606 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/26 03:14:59.969138 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/26 03:15:29.969171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:15:59.969256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:29.969121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:59.969013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:29.969187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:59.969031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:29.968964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:59.969079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:29.969129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:34.986799 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:19:59.969364 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/26 03:20:29.969132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:20:59.969591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:29.969040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:59.969005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:29.968989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:59.969048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:29.969069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:59.969015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:29.969257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:59.969019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:29.969123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:59.969056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:29.969109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:59.969006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:29.968989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:59.968944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:29.968996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:59.968999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:29.968973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:59.968976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:29.969010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:59.969169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:29.969079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:59.969041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:29.969167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:59.969052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:29.969169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:59.969054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:29.968971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:59.969023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:29.969078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:59.968991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:29.969078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:59.969099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:29.969064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:59.969034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:29.968999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:59.968983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:29.968991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:59.968937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:29.968965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:59.969915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:29.968967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:59.968934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:29.969015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:50.133035 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/26 03:42:55.098835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:55.098882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:56.103160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:56.103200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:58.106743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:58.106808 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:59.969049 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/26 03:43:02.113897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:02.113930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:10.121194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:10.121228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:26.140683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:26.140756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:29.969021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:43:58.156148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:58.156210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:59.968987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:29.968974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:58.172680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:44:58.172726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:44:59.969134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:29.969130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:58.190839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:45:58.190887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:45:59.969101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:29.969018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:58.208979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:46:58.209032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:46:59.968970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:29.969136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:58.225957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:47:58.226003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:47:59.969002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:29.968993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:58.243742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:48:58.243935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:48:59.969022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:29.968975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:58.265630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:49:58.265679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:49:59.968986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:29.969028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:58.283612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:50:58.283680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:50:59.969047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:25.157412 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:51:29.968994 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/26 03:51:58.302063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:51:58.302098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:51:59.968983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:29.968982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:58.319176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:52:58.319208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:52:59.968981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:29.969063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:58.336340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:53:58.336384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:53:59.969164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:29.969000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:58.353665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:54:58.353716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:54:59.969003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:29.969008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:58.370340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:55:58.370423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:55:59.968981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:29.969075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:58.388913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:56:58.388950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:56:59.968980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:29.968955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:58.405809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:57:58.405853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:57:59.969087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:29.969040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:58.423588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:58:58.423625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:58:59.968995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:29.970937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:58.440893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:59:58.440939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:59:59.969140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:29.969040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:58.458552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:00:58.458598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:00:59.969018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:29.969053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:58.476055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:01:58.476104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:01:59.969137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:29.968992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:58.494779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:02:58.494815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:02:59.969148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:29.969060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:58.514462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:03:58.514571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:03:59.968990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:29.968947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:58.532479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:04:58.532536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:04:59.968931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:29.968966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:58.550244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:05:58.550294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:05:59.968979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:29.968960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:58.567178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:06:58.567217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:06:59.969056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:29.968939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:58.586010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:07:58.586045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:07:59.968970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:29.971850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:58.604804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:08:58.604866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:08:59.969042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:29.968961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:58.624103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:09:58.624478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:09:59.969011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:29.968982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:58.643092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:10:58.643136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:10:59.968965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:29.970111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:58.664676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:11:58.664766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:11:59.968942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:29.969190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:58.682076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:12:58.682119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:12:59.968991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:29.969116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:58.712455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:13:58.712493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:13:59.968968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:29.969159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:58.734924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:14:58.734979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:14:59.969027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:29.969120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:58.756327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:15:58.756358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:15:59.969008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:29.969025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:58.793197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:16:58.793408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:16:59.970246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:29.968989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:58.811007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:17:58.811067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:17:59.969260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:29.968980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:58.828964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:18:58.829005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:18:59.968982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:29.969118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:58.845786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:19:58.845830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:19:59.969027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:29.968985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:58.863706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:20:58.863774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:20:59.969046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:29.969065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:58.884278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:21:58.884415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:21:59.969048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:29.968985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:58.901160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:22:58.901214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:22:59.969118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:29.968970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:58.919392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:23:58.919532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:23:59.968992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:29.969040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:58.936681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:24:58.936857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:24:59.969046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:29.968984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:58.954654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:25:58.954726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:25:59.968942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:29.969000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:58.970713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:26:58.970756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:26:59.968979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:29.968987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:58.988946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:27:58.989072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:27:59.969028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:29.968963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:59.006703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:28:59.006745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:28:59.969004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:29.968954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:59.022184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:29:59.022228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:29:59.969044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:29.969187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:59.038773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:30:59.038806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:30:59.969017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:29.968964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:59.056272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:31:59.056313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:31:59.969117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:29.969006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:59.073068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:32:59.073120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:32:59.969030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:29.969077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:59.091839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:33:59.091894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:33:59.969255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:29.969084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:59.109507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:34:59.109568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:34:59.969040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:29.969076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:59.124477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:35:59.124530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:35:59.969495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:29.968962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:59.145159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:36:59.145205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:36:59.969018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:29.968976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:59.163199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:37:59.163321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:37:59.968976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:29.969329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:59.182185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:38:59.182249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:38:59.969113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:29.969042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:59.202549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:39:59.202593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:39:59.969247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:29.969045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:59.225180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:40:59.225235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:40:59.969052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:29.969032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:59.247941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:41:59.248006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:41:59.969024 metrics.go:34: INFO No non-zero metrics in the last 30s