Results

          2022/03/26 03:14:49.638832 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:49.638884 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/26 03:14:49.639006 metrics.go:23: INFO Metrics logging every 30s
2022/03/26 03:14:49.639023 logstash.go:90: INFO Max Retries set to: 3
2022/03/26 03:14:49.639142 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/26 03:14:49.639275 publish.go:295: INFO Publisher name: onap-vfc-vnfmgr-8594ffd488-sx49t
2022/03/26 03:14:49.639522 async.go:63: INFO Flush Interval set to: 1s
2022/03/26 03:14:49.639545 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/26 03:14:49.640050 beat.go:221: INFO filebeat start running.
2022/03/26 03:14:49.640174 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/26 03:14:49.644712 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/26 03:14:49.644770 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/26 03:14:49.644838 crawler.go:38: INFO Loading Prospectors: 1
2022/03/26 03:14:49.645016 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/26 03:14:49.645108 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/26 03:14:49.645128 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/26 03:14:49.645149 registrar.go:236: INFO Starting Registrar
2022/03/26 03:14:49.645176 sync.go:41: INFO Start sending events to output
2022/03/26 03:14:49.645247 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/26 03:14:49.645808 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/26 03:15:19.639424 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:49.639355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:19.645083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:49.640622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:19.639362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:49.639672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:19.639470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:49.639315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:19.639417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:49.639420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:54.666011 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:20:19.639479 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:49.639462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:19.639421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:49.639405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:19.639356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:49.639453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:19.639324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:49.639461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:19.639403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:49.639483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:19.639542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:49.639351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:19.639455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:49.639424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:19.639324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:49.639341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:19.639286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:49.639431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:19.639419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:49.639862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:19.639275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:49.639327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:19.639322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:49.639481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:19.639452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:49.639300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:19.639444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:49.639611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:19.639346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:49.639353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:19.639333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:49.639465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:19.639309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:49.639605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:19.639815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:49.639373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:19.639346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:49.639452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:19.639314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:49.639317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:19.639408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:49.639444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:19.639394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:49.639527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:19.639366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:49.639516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:49.857487 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/26 03:42:54.858743 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:54.858791 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:55.862909 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.862982 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:57.865827 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:57.865860 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:01.880099 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:01.880151 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:09.890058 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:09.890099 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:19.639428 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:25.911835 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:25.911899 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:49.639366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:43:57.929289 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:57.929326 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:19.639328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:49.639432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:57.947532 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:57.947577 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:19.639368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:49.639467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:57.969168 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:57.969207 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:19.639313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:49.639289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:57.989918 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:57.990038 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:19.639359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:49.639424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:58.008868 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.008903 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:19.639462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:49.639360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:58.028480 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.028615 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:19.639351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:49.639310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:58.050101 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.050135 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:19.639469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:49.639321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:58.069087 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.069133 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:19.639324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:24.897938 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:51:49.639422 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.088576 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.088622 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:19.639416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:49.639329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:58.108094 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.108393 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:19.639478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:49.639491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:58.127035 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.127099 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:19.639349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:49.639369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:58.145340 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.145390 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:19.639450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:49.639583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:58.163203 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.163245 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:19.639433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:49.639475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:58.181682 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.181711 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:19.639331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:49.639430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:58.200021 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.200057 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:19.639342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:49.639443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:58.220253 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.220293 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:19.639351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:49.639335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:58.239030 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.239075 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:19.639359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:49.639541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:58.257801 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.257866 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:19.639449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:49.639422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:58.276311 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.276360 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:19.639489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:49.639323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:58.295007 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.295045 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:19.639397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:49.639398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:58.313395 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.313437 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:19.639321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:49.639355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:58.335478 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.335516 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:19.639460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:49.639329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:58.354616 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.354653 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:19.639350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:49.639304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:58.373383 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.373423 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:19.639357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:49.639316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:58.392117 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.392228 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:19.639345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:49.640229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:58.411849 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.411898 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:19.643727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:49.639562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:58.428226 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.428276 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:19.639293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:49.639467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:58.446158 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.446196 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:19.639608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:49.639469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:58.463827 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.463958 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:19.640311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:49.639408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:58.481719 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.481760 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:19.639293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:49.639323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:58.500111 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.500166 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:19.639476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:49.639284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:58.518470 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.518512 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:19.639294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:49.639332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:58.536672 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.536729 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:19.639449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:49.639335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:58.559365 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.559509 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:19.639463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:49.639531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:58.577488 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.577522 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:19.639339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:49.639354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:58.597230 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.597268 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:19.639393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:49.639517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:58.617208 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.617248 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:19.639328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:49.639397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:58.636689 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.636733 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:19.640313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:49.639349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:58.656593 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.656632 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:19.639289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:49.639295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:58.675193 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.675236 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:19.639328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:49.639322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:58.693307 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.693441 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:19.639521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:49.639424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:58.711784 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.711826 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:19.639519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:49.639458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:58.730009 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.730042 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:19.639339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:49.639722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:58.746703 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.746744 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:19.639469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:49.639461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:58.765950 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.766012 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:19.639431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:49.639335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:58.786635 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:58.786675 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:19.639536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:49.639324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:58.807199 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:58.807342 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:19.639332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:49.639341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:58.825966 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:58.826005 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:19.639369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:49.639444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:58.843675 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:58.843789 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:19.639346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:49.639351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:58.861698 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:58.861743 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:19.639367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:49.639363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:58.879948 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:58.879989 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:19.639348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:49.639330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:58.898586 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:58.898639 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:19.639423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:49.639507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:58.915092 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:58.915139 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:19.639344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:49.639487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:58.938364 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:58.938406 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:19.639360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:49.639314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:58.956666 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:58.956711 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:19.639407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:49.639425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:58.974668 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:58.974862 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:19.639443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:49.639336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:58.993139 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:58.993608 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:19.639466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:49.639341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:59.010287 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.010338 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:19.639447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:49.639347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:59.028371 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.028470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host