Results

          2022/03/10 03:15:40.827296 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/10 03:15:40.827341 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 03:15:40.827421 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 03:15:40.827508 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 03:15:40.827622 publish.go:295: INFO Publisher name: onap-vfc-vnflcm-84bd7747bf-96plb
2022/03/10 03:15:40.827813 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 03:15:40.827836 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 03:15:40.828319 beat.go:221: INFO filebeat start running.
2022/03/10 03:15:40.828322 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 03:15:40.828412 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 03:15:40.832201 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 03:15:40.832248 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 03:15:40.832284 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 03:15:40.832305 registrar.go:236: INFO Starting Registrar
2022/03/10 03:15:40.832333 sync.go:41: INFO Start sending events to output
2022/03/10 03:15:40.832426 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 03:15:40.832483 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 03:15:40.832511 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/10 03:15:40.832541 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 03:15:40.833104 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/10 03:16:10.828793 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/10 03:16:40.828818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:10.828882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:40.828614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:10.828817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:40.828623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:10.828773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:40.828635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:10.828694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:40.828759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:45.842606 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:21:10.828702 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/10 03:21:40.828683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:10.828812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:40.828676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:10.828752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:40.828718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:10.828761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:40.828672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:10.828784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:40.828643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:10.828736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:40.828716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:10.828780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:40.828706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:10.828605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:40.828663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:10.828708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:40.828632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:10.828748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:40.828728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:10.828663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:40.828630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:10.828719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:40.828650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:10.828639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:40.828612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:10.828679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:40.828659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:10.828639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:40.828672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:10.828628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:40.828683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:10.828608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:40.828625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:10.828615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:40.828656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:10.828662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:40.828637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:10.828597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:40.828860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:10.828636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:40.828665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:10.828694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:40.828693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:10.828668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:40.828678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:10.828715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:40.828769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:40.979605 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/10 03:44:45.997098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:45.997137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:47.002882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:47.002920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:49.008736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:49.008959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:53.015964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:53.016007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:01.036085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:01.036131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:10.828996 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 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/10 03:45:17.041153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:17.041212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:40.829007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:45:49.060300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:49.060337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:46:10.828691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:40.828678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:49.066556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:46:49.066589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:47:10.828682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:40.828740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:49.073040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:47:49.073092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:48:10.828687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:40.828671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:49.080490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:48:49.080520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:49:10.828586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:40.828718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:45.998057 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:49:49.089113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:49:49.089163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:50:10.828682 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/10 03:50:40.828716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:50:49.096098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:50:49.096143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:51:10.828706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:40.828599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:49.103423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:51:49.103472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:52:10.828664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:40.828727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:49.110559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:52:49.110592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:53:10.828744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:40.828731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:49.117606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:53:49.117659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:54:10.828768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:40.828685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:49.125090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:54:49.125211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:55:10.828704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:40.828627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:49.132362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:55:49.132400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:56:10.828665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:40.828665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:49.139136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:56:49.139174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:57:10.828655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:40.828691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:49.148414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:57:49.148463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:58:10.828663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:40.828667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:49.155691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:58:49.155723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:59:10.828663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:40.828678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:49.161834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:59:49.161913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:00:10.828755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:40.828698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:49.169370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:00:49.169421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:01:10.828624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:40.828854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:49.176348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:01:49.176385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:02:10.828635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:40.828674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:49.182536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:02:49.182566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:03:10.828683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:40.828679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:49.188661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:03:49.188696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:04:10.828627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:40.828648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:49.195940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:04:49.196249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:05:10.828627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:40.828657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:49.203234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:05:49.203439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:06:10.828739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:40.828741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:49.210451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:06:49.210497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:07:10.828703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:40.828739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:49.216837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:07:49.216879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:08:10.828716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:40.828688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:49.224161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:08:49.224193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:09:10.828801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:40.830868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:49.232191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:09:49.232233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:10:10.828712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:40.828631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:49.238474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:10:49.238505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:11:10.828680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:40.828845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:49.245122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:11:49.245227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:12:10.828668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:40.829054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:49.251511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:12:49.251544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:13:10.828656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:40.828716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:49.258133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:13:49.258178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:14:10.828737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:40.828638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:49.267575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:14:49.267605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:15:10.828615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:40.828616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:49.275521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:15:49.275567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:16:10.828700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:40.828701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:49.281979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:16:49.282033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:17:10.828765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:40.828657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:49.289336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:17:49.289387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:18:10.828672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:40.828669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:49.295928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:18:49.295968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:19:10.828753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:40.828667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:49.304399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:19:49.304439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:20:10.828756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:40.828717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:49.312791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:20:49.312848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:21:10.828661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:40.828656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:49.319368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:21:49.319562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:22:10.828802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:40.828655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:49.326830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:22:49.326864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:23:10.828610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:40.828672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:49.333099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:23:49.333131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:24:10.828638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:40.828647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:49.340246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:24:49.340415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:25:10.828730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:40.828636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:49.347888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:25:49.347934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:26:10.828689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:40.829031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:49.355452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:26:49.355499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:27:10.828719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:40.828664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:49.362033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:27:49.362064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:28:10.828717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:40.828711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:49.368283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:28:49.368319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:29:10.828716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:40.828671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:49.375436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:29:49.375518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:30:10.828632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:40.828704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:49.382912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:30:49.382941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:31:10.828717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:40.828732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:49.390346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:31:49.390379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:32:10.828641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:40.828719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:49.397914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:32:49.397952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:33:10.830031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:40.828729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:49.405800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:33:49.405840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:34:10.828700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:40.828661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:49.412444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:34:49.412484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:35:10.828651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:40.828617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:49.418708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:35:49.418739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:36:10.828688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:40.828642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:49.425836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:36:49.425891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:37:10.828600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:40.828698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:49.434452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:37:49.434499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:38:10.828665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:40.828630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:49.441520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:38:49.441563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:39:10.828647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:39:40.828647 metrics.go:34: INFO No non-zero metrics in the last 30s