2022/03/13 03:18:57.204813 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/13 03:18:57.204881 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/13 03:18:57.205009 logstash.go:90: INFO Max Retries set to: 3
2022/03/13 03:18:57.205110 metrics.go:23: INFO Metrics logging every 30s
2022/03/13 03:18:57.205159 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/13 03:18:57.205323 publish.go:295: INFO Publisher name: onap-vfc-vnfres-844dfc67b6-fb28r
2022/03/13 03:18:57.205581 async.go:63: INFO Flush Interval set to: 1s
2022/03/13 03:18:57.205607 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/13 03:18:57.208367 beat.go:221: INFO filebeat start running.
2022/03/13 03:18:57.208533 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/13 03:18:57.213281 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/13 03:18:57.213352 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/13 03:18:57.213395 crawler.go:38: INFO Loading Prospectors: 1
2022/03/13 03:18:57.213452 registrar.go:236: INFO Starting Registrar
2022/03/13 03:18:57.213650 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/13 03:18:57.213676 sync.go:41: INFO Start sending events to output
2022/03/13 03:18:57.214116 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/13 03:18:57.214505 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/13 03:18:57.214545 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/13 03:18:57.215218 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/13 03:19:27.205618 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/13 03:19:57.205465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:27.205509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:57.205535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:27.205981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:57.205700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:27.205571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:57.205400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:27.205490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:57.205438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:24:02.225934 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:24:27.205679 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/13 03:24:57.205392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:27.205428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:57.205552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:27.205554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:57.205519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:27.205473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:57.205624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:27.205571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:57.205459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:27.205527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:57.205479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:27.205657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:57.205486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:27.205468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:57.205477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:27.205589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:57.205393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:27.205425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:57.205442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:27.205530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:57.205535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:27.205438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:57.205504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:27.205486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:57.205411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:27.205416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:57.205469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:27.205630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:57.205474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:27.205576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:57.205458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:27.205444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:57.205490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:27.205528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:57.205510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:27.205409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:57.205551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:27.205564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:57.205445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:27.205410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:57.205495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:27.205472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:57.205481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:27.205477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:57.205840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:27.205589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:57.205673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:07.378734 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/13 03:48:12.335552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:12.335609 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:13.339584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:13.339634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:15.355915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:15.355967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:19.367500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:19.367648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:27.205445 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/13 03:48:27.383671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:27.383806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:43.391927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:43.392070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:57.205503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:15.399686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:15.399905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:27.206257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:57.205417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:15.419583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:15.419617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:27.205391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:57.205373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:15.439209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:15.439253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:27.205526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:57.205474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:15.463025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:15.463072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:27.205453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:57.205433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:12.397973 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:53:15.482225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:15.482274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:27.205434 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/13 03:53:57.205383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:15.501914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:15.501958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:27.205418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:57.205437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:17.522510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:17.522567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:27.205481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:57.205588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:17.542065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:17.542115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:27.205430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:57.205434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:17.561833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:17.561872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:27.205506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:57.205533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:17.583112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:17.583155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:27.205483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:57.205456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:17.607238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:17.607350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:27.205474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:57.205458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:17.627228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:17.627331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:27.205435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:57.205419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:17.646129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:17.646175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:27.205448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:57.205401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:17.665522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:17.665563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:27.205439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:57.205411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:17.684004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:17.684051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:27.205406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:57.205499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:17.702232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:17.702285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:27.205444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:57.205434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:17.721913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:17.722079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:27.205393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:57.205396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:17.741921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:17.741984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:27.205524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:57.207539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:17.771458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:17.771517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:27.205451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:57.205588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:17.793004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:17.793060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:27.205487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:57.205510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:17.811724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:17.811806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:27.205441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:57.207332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:17.830130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:17.830170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:27.205496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:57.205485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:17.849382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:17.849540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:27.205392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:57.206623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:17.869452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:17.869497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:27.205466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:57.205509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:17.889207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:17.889243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:27.205411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:57.205523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:17.907917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:17.907980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:27.205455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:57.205456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:17.928163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:17.928237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:27.206351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:57.205517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:17.947602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:17.947639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:27.205423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:57.205427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:17.967381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:17.967422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:27.205438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:57.205462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:17.986346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:17.986400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:27.206051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:57.205570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:18.006641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:18.006697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:27.205430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:57.205405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:18.025251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:18.025288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:27.205510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:57.205403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:18.045397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:18.045438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:27.205510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:57.205515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:18.063814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:18.063865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:27.205431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:57.205527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:18.085695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:18.085734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:27.205435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:57.205446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:18.107439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:18.107488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:27.205496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:57.205447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:18.127664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:18.127729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:27.205451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:57.205427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:18.147435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:18.147504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:27.205863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:57.205484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:18.166776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:18.166834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:27.205418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:57.205403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:18.185810 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:18.185878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:27.205487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:57.205865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:18.204518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:18.204572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:27.205487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:57.205502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:18.224041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:18.224252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:27.205526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:57.205504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:18.249337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:18.249376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:27.205405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:57.205478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:18.269348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:18.269408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:27.205475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:57.205389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:18.290028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:18.290065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:27.205551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:57.205544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:18.311032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:18.311194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:27.205489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:57.205645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:18.333041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:18.333273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:27.205530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:57.205407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:18.352890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:18.352941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:27.205462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:57.205458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:37:18.370414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:37:18.370461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host