Results

          2022/03/26 03:14:33.861883 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:33.861949 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/26 03:14:33.862131 metrics.go:23: INFO Metrics logging every 30s
2022/03/26 03:14:33.862153 logstash.go:90: INFO Max Retries set to: 3
2022/03/26 03:14:33.862238 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/26 03:14:33.862903 publish.go:295: INFO Publisher name: onap-vfc-vnfres-844dfc67b6-nvhhj
2022/03/26 03:14:33.863190 async.go:63: INFO Flush Interval set to: 1s
2022/03/26 03:14:33.863208 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/26 03:14:33.865614 beat.go:221: INFO filebeat start running.
2022/03/26 03:14:33.865777 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/26 03:14:33.869550 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/26 03:14:33.869699 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/26 03:14:33.869795 crawler.go:38: INFO Loading Prospectors: 1
2022/03/26 03:14:33.869932 registrar.go:236: INFO Starting Registrar
2022/03/26 03:14:33.870097 sync.go:41: INFO Start sending events to output
2022/03/26 03:14:33.870221 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/26 03:14:33.870429 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/26 03:14:33.870665 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/26 03:14:33.870743 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/26 03:14:33.871837 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/26 03:15:03.862757 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:33.863048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:03.862467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:33.862478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:03.862422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:33.862462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:03.863018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:33.862620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:03.862495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:33.862495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:38.880505 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/26 03:20:03.862626 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:33.862507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:03.862495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:33.862440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:03.862436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:33.862549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:03.862497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:33.862530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:03.862507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:33.862653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:03.862579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:33.862575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:03.862887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:33.862469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:03.862390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:33.862413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:03.862465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:33.862506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:03.862615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:33.862571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:03.862598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:33.862461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:03.862593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:33.862453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:03.862564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:33.862462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:03.862427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:33.862436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:03.862579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:33.862470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:03.862524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:33.862501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:03.862420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:33.862541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:03.862649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:33.862463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:03.862434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:33.862630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:03.862523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:33.862473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:03.862552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:33.863140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:03.862413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:33.862402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:03.862456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:33.862568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:54.038522 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/26 03:42:59.009838 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:59.009875 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:00.014553 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:00.014687 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:02.019013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:02.019048 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:03.862397 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:06.025366 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:06.025463 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:14.037127 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:14.037163 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:30.054948 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:30.055042 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:33.862467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:02.074878 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:02.074910 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:03.862386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:33.862461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:02.094758 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:02.094806 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:03.862721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:33.862527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:02.112581 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:02.112777 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:03.862439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:33.862432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:02.131438 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:02.131496 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:03.862514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:33.862902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:02.153141 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:02.153202 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:03.862526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:33.862419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:03.862380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:04.174383 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:04.174421 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:33.862379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:03.863099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:04.191642 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:04.191678 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:33.862439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:03.862524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:04.208269 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:04.208315 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:29.060862 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/26 03:51:33.862716 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:52:03.862412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:04.225792 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:04.225840 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:33.862561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:03.862484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:04.244774 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:04.244827 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:33.862467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:03.862374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:04.262922 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:04.262958 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:33.862648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:03.862411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:04.280912 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:04.280946 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:33.862629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:03.862409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:04.299152 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:04.299186 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:33.862482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:03.862427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:04.320441 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:04.320713 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:33.862486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:03.862867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:04.339089 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:04.339138 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:33.862501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:03.862372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:04.370438 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:04.370486 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:33.862461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:03.863902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:04.391999 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:04.392051 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:33.862719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:03.862400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:04.410219 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:04.410485 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:33.862469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:03.862492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:04.427676 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:04.427721 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:33.864198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:03.862625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:04.446376 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:04.446423 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:33.862539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:03.862874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:04.465161 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:04.465201 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:33.862769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:03.862431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:04.481739 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:04.481775 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:33.862403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:03.862500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:04.500474 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:04.500748 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:33.862667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:03.862459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:04.516562 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:04.516598 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:33.862382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:03.862393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:04.533536 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:04.533593 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:33.862491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:03.862435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:04.552508 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:04.552557 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:33.862488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:03.862497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:04.570961 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:04.571050 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:33.862468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:03.862439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:04.590409 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:04.590457 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:33.862509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:03.862652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:04.608994 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:04.609071 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:33.862412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:03.862564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:04.627852 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:04.627889 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:33.862515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:03.862433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:04.648634 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:04.648761 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:33.862432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:03.862451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:04.665308 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:04.665345 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:33.862692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:03.862454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:04.685632 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:04.685683 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:33.862448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:03.862439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:04.702969 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:04.703018 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:33.862448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:03.862520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:04.720188 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:04.720251 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:33.862439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:03.864098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:04.738450 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:04.738526 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:33.862404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:03.862455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:04.756161 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:04.756198 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:33.862533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:03.862454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:04.780624 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:04.780676 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:33.862500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:03.863022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:04.797398 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:04.797436 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:33.862418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:03.862419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:04.817527 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:04.817586 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:33.862413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:03.862618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:04.834510 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:04.834550 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:33.864641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:03.862369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:04.852100 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:04.852140 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:33.862495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:03.862438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:04.876690 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:04.876746 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:33.862448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:03.862378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:04.898082 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:04.898134 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:33.862535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:03.862640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:04.917830 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:04.917886 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:33.862405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:03.862459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:04.934879 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:04.934927 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:33.862531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:03.862445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:04.955887 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:04.955934 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:33.862553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:03.862545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:04.974175 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:04.974324 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:33.862491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:03.862500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:04.992010 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:04.992053 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:33.862351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:03.862449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:05.009307 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:05.009340 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:33.862510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:03.862383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:05.027984 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:05.028040 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:33.862442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:03.862461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:05.046035 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:05.046077 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:33.862514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:03.862547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:05.066264 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:05.066307 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:33.862515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:03.862420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:05.086098 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:05.086149 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:33.862477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:03.869351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:05.103990 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:05.104046 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:33.862448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:03.862414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:05.129913 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:05.130106 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:33.862558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:03.868472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:05.148227 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:05.148272 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:33.862450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:03.862393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:05.166817 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:05.166864 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:33.862494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:42:03.862873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:42:05.186072 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:42:05.186120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host