By type
2022/03/30 03:17:00.985045 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/30 03:17:00.985146 metrics.go:23: INFO Metrics logging every 30s
2022/03/30 03:17:00.985220 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/30 03:17:00.985423 logstash.go:90: INFO Max Retries set to: 3
2022/03/30 03:17:00.985810 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/30 03:17:00.986162 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-q8w7x
2022/03/30 03:17:00.986600 async.go:63: INFO Flush Interval set to: 1s
2022/03/30 03:17:00.986721 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/30 03:17:00.987518 beat.go:221: INFO filebeat start running.
2022/03/30 03:17:00.987593 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/30 03:17:00.994511 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/30 03:17:00.994662 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/30 03:17:00.994753 crawler.go:38: INFO Loading Prospectors: 1
2022/03/30 03:17:00.994796 sync.go:41: INFO Start sending events to output
2022/03/30 03:17:00.994961 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/30 03:17:00.994789 registrar.go:236: INFO Starting Registrar
2022/03/30 03:17:00.995143 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/30 03:17:00.995321 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/30 03:17:00.995388 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/30 03:17:00.996269 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/30 03:17:30.985536 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/30 03:18:00.985564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:18:30.985514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:19:00.985689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:19:30.985569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:20:00.985505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:20:30.985580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:21:00.985603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:21:30.985600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:22:00.985492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:22:06.008852 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/30 03:22:30.985628 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/30 03:23:00.985562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:23:30.985587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:24:00.985654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:24:30.985573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:25:00.985566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:25:30.985571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:26:00.985820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:26:30.985666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:27:00.985495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:27:30.985593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:28:00.985514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:28:30.985572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:29:00.985573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:29:30.985561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:30:00.985535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:30:30.985515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:31:00.985469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:31:30.985759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:32:00.985607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:32:30.985450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:33:00.985513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:33:30.985527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:34:00.985554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:34:30.985475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:35:00.985636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:35:30.985637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:36:00.985509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:36:30.985476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:37:00.986062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:37:30.985580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:38:00.985535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:38:30.985521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:39:00.985666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:39:30.985471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:40:00.985494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:40:30.985471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:41:00.985715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:41:30.985477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:42:00.985487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:42:30.985453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:43:00.985777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:43:30.985558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:44:00.985568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:44:30.985521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:45:00.985522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:45:30.985608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:46:00.985499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:46:30.985603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:47:00.985544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:47:21.136693 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/30 03:47:26.110201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:26.110245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:27.115297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:27.115347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:29.119998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:29.120153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:30.985539 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/30 03:47:33.126859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:33.126891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:41.143185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:41.143243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:57.161537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:57.161580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:48:00.985522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:48:29.180298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:48:29.180336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:48:30.985514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:49:00.985468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:49:29.197523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:49:29.197563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:49:30.985602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:50:00.985553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:50:29.216020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:50:29.216062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:50:30.985502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:51:00.985653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:51:29.234204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:51:29.234238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:51:30.985590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:52:00.985485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:52:29.252538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:52:29.252586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:52:30.985586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:53:00.985465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:53:29.271056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:53:29.271102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:53:30.985542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:54:00.985505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:54:29.290299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:54:29.290373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:54:30.985571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:55:00.985502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:55:11.155888 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/30 03:55:29.313151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:55:29.313215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:55:30.985634 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/30 03:56:00.985498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:56:29.331732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:56:29.331783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:56:30.985480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:57:00.985511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:57:29.350455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:57:29.350492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:57:30.985581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:58:00.985499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:58:29.370134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:58:29.370196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:58:30.985634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:59:00.985498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:59:29.389790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:59:29.389845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:59:30.985575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:00:00.985471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:00:29.409540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:00:29.409614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:00:30.985510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:01:00.985445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:01:29.428884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:01:29.428938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:01:30.985483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:02:00.985489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:02:29.451802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:02:29.451846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:02:30.985455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:03:00.985513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:03:29.472655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:03:29.472691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:03:30.985427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:04:00.985641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:04:29.491348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:04:29.491407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:04:30.985592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:05:00.985531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:05:29.507292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:05:29.507337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:05:30.985519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:06:00.985521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:06:29.527490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:06:29.527675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:06:30.985728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:07:00.985515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:07:29.545245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:07:29.545297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:07:30.985600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:08:00.985471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:08:29.562392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:08:29.562429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:08:30.985514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:09:00.985501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:09:29.583036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:09:29.583084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:09:30.985426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:10:00.985505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:10:29.604857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:10:29.604909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:10:30.985504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:11:00.985518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:11:29.626302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:11:29.626382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:11:30.985682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:12:00.985494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:12:29.645427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:12:29.645463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:12:30.985478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:13:00.985486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:13:29.665230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:13:29.665267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:13:30.985504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:14:00.985473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:14:29.683100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:14:29.683245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:14:30.985485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:15:00.985515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:15:29.722122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:15:29.722170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:15:30.985511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:16:00.985639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:16:29.742355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:16:29.742398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:16:30.985479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:17:00.985549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:17:29.763315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:17:29.763373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:17:30.985542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:18:00.985526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:18:29.783094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:18:29.783148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:18:30.985533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:19:00.985576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:19:29.804231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:19:29.804264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:19:30.985553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:20:00.985482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:20:29.821023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:20:29.821061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:20:30.985511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:21:00.985537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:21:29.837852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:21:29.837910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:21:30.985549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:22:00.985575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:22:29.864015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:22:29.864054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:22:30.985620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:23:00.985501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:23:29.884495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:23:29.884660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:23:30.985569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:24:00.985563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:24:29.904571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:24:29.904652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:24:30.985646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:25:00.985551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:25:29.923214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:25:29.923253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:25:30.985463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:26:00.985501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:26:29.941616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:26:29.941739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:26:30.985553 metrics.go:34: INFO No non-zero metrics in the last 30s