By type
2022/03/11 03:18:37.362355 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/11 03:18:37.362502 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/11 03:18:37.362616 logstash.go:90: INFO Max Retries set to: 3
2022/03/11 03:18:37.362764 metrics.go:23: INFO Metrics logging every 30s
2022/03/11 03:18:37.362861 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/11 03:18:37.363023 publish.go:295: INFO Publisher name: onap-vfc-generic-vnfm-driver-757795dcf7-ztjxz
2022/03/11 03:18:37.363347 async.go:63: INFO Flush Interval set to: 1s
2022/03/11 03:18:37.363416 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/11 03:18:37.363946 beat.go:221: INFO filebeat start running.
2022/03/11 03:18:37.364089 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/11 03:18:37.367874 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/11 03:18:37.367928 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/11 03:18:37.368143 crawler.go:38: INFO Loading Prospectors: 1
2022/03/11 03:18:37.368313 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/11 03:18:37.368436 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/11 03:18:37.368569 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/11 03:18:37.368595 registrar.go:236: INFO Starting Registrar
2022/03/11 03:18:37.368693 sync.go:41: INFO Start sending events to output
2022/03/11 03:18:37.368800 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/11 03:18:37.369458 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/11 03:19:07.363417 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/11 03:19:37.363177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:07.363106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:37.363146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:07.363129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:37.363190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:07.363156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:37.363160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:07.363171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:37.363094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:42.379164 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:24:07.363311 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/11 03:24:37.363142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:07.363204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:37.363117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:07.363320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:37.363120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:07.363318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:37.363195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:07.363385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:37.363113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:07.363505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:37.363129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:07.363197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:37.363118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:07.363080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:37.363157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:07.363514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:37.363492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:07.363366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:37.363155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:07.363196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:37.363297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:07.363161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:37.363141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:07.363120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:37.363115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:07.363249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:37.363102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:07.363107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:37.363077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:07.363196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:37.363167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:07.366986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:37.363123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:07.363255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:37.363102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:07.363087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:37.363175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:07.363193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:37.365769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:07.363224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:37.363182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:07.363199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:37.363067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:07.363096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:37.363118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:07.363207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:37.363138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:47.541273 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/11 03:47:52.501970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:52.502024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:53.505394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:53.505511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:55.511172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:55.511227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:59.517705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:59.517750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:07.363147 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/11 03:48:07.525903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:07.525934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:23.547064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:23.547109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:37.363099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:48:55.571863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:55.571903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:07.363146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:37.363146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:55.592583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:55.592640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:07.363441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:37.363161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:55.614966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:55.615013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:07.363056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:37.363455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:55.635460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:55.635614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:07.363120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:37.363255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:52.555947 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:52:55.661365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:55.661441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:07.363884 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/11 03:53:37.363097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:55.684724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:55.684779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:07.363171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:37.363066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:55.703396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:55.703439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:07.363155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:37.363138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:55.723164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:55.723205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:07.363069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:37.363088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:55.744235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:55.744273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:07.363141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:37.363098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:55.763104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:55.763144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:07.363093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:37.363235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:55.779805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:55.779864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:07.363094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:37.363051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:55.799042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:55.799082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:07.363050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:37.363089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:55.816973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:55.817013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:07.363234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:37.363165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:55.838744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:55.838813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:07.363179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:37.363095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:55.860472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:55.860515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:07.363141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:37.363127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:55.879974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:55.880043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:07.363048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:37.363132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:55.899413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:55.899593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:07.363210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:37.363095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:55.918079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:55.918141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:07.363054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:37.363069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:55.938649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:55.938695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:07.363168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:37.363177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:55.957756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:55.957790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:07.363049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:37.363161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:55.977688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:55.977746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:07.363130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:37.363160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:55.999242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:55.999287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:07.363210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:37.363262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:56.019282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:56.019328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:07.363148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:37.363212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:56.038550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:56.038608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:07.363147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:37.363288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:56.059498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:56.059535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:07.363069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:37.363108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:56.077696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:56.077742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:07.363056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:37.363079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:56.095571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:56.095616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:07.369821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:37.363034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:56.114280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:56.114324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:07.363084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:37.363043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:56.138576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:56.138615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:07.363066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:37.363117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:56.157856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:56.157909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:07.363189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:37.363274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:56.176999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:56.177041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:07.363293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:37.363119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:56.197279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:56.197320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:07.363069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:37.363091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:56.216005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:56.216047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:07.363124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:37.363106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:56.235364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:56.235414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:07.363306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:37.363053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:56.254334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:56.254374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:07.363162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:37.363102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:56.274177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:56.274215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:07.363067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:37.363028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:56.291023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:56.291062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:07.363136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:37.363060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:56.310052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:56.310096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:07.363060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:37.363023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:56.330076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:56.330145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:07.365668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:37.363037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:56.350419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:56.350464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:07.363027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:37.362981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:56.369350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:56.369490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:07.363045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:37.363287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:56.390717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:56.390769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:07.363166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:37.363146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:56.411976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:56.412023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:07.363113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:37.365624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:56.433602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:56.433766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:07.363069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:37.363073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:56.454121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:56.454174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:33:07.363133 metrics.go:34: INFO No non-zero metrics in the last 30s