2022/03/05 03:29:12.738471 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/05 03:29:12.738575 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:29:12.738741 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:29:12.738873 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:29:12.739041 publish.go:295: INFO Publisher name: onap-vfc-vnflcm-84bd7747bf-dbmwv
2022/03/05 03:29:12.739383 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:29:12.739411 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:29:12.740410 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:29:12.740862 beat.go:221: INFO filebeat start running.
2022/03/05 03:29:12.741072 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:29:12.746624 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:29:12.746799 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:29:12.746865 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:29:12.747260 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:29:12.747471 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/05 03:29:12.747583 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:29:12.747668 registrar.go:236: INFO Starting Registrar
2022/03/05 03:29:12.747757 sync.go:41: INFO Start sending events to output
2022/03/05 03:29:12.747801 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:29:12.748402 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/05 03:29:42.741138 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/05 03:30:12.741815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:42.744034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:12.743998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:42.740948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:12.740859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:42.741160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:12.740836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:42.740783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:12.741520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:17.780530 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/05 03:34:42.742353 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/05 03:35:12.740776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:42.740779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:12.740918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:42.740838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:12.740861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:42.740817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:12.740791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:42.741164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:12.740877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:42.740881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:12.741224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:42.740808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:12.740783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:42.741152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:12.742966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:42.740880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:12.740815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:42.740793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:12.741092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:42.740893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:12.740909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:42.740889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:12.740799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:42.740893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:12.740945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:42.742046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:12.740754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:42.741318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:12.746245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:42.744051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:12.747890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:42.741566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:12.745538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:42.740790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:12.747351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:42.740851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:12.740876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:42.741048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:12.742363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:42.740835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:12.741354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:42.741446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:12.740900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:42.740849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:12.740949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:42.740977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:12.743325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:33.069536 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/05 03:58:38.074867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:38.074927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:39.085083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:39.085146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:41.091452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:41.091514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:42.741394 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/05 03:58:45.097807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:45.097860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:53.103965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:53.104007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:09.124141 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:09.124361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:12.740971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:41.153224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:41.153353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:42.740812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:12.741594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:41.179947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:41.180160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:42.740892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:12.741069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:41.211045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:41.211284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:42.741541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:12.740765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:41.233981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:41.234348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:42.741227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:12.740897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:38.094126 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/05 04:03:41.261228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:41.261301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:42.740956 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/05 04:04:12.740837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:41.285260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:41.285321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:42.740884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:12.740874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:41.309390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:41.309453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:42.741053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:12.740817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:41.337859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:41.338063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:42.740916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:12.742836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:41.364206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:41.364277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:42.740822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:12.741812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:41.386142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:41.386452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:42.744807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:12.740796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:41.414316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:41.414384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:42.741175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:12.740949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:41.445138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:41.445205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:42.740785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:12.740792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:41.474672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:41.474755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:42.741840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:12.740797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:41.502821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:41.502886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:42.740934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:12.741463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:41.526961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:41.527025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:42.741279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:12.741076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:41.553462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:41.553972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:42.740889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:12.741454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:41.594762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:41.594864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:42.740977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:12.740845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:41.617997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:41.618100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:42.740922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:12.740930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:41.638211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:41.638297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:42.745483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:12.743494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:41.680899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:41.680958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:42.740927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:12.740859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:41.703616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:41.703665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:42.740982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:12.741016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:41.729230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:41.729303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:42.741099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:12.740906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:41.750673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:41.750838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:42.740863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:12.740977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:41.770577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:41.770696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:42.741479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:12.741048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:41.828201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:41.828256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:42.745687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:12.740833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:41.851657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:41.851755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:42.740865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:12.746506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:41.879135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:41.879391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:42.740829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:12.740778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:41.926188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:41.926260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:42.740784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:12.740862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:41.954843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:41.954912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:42.743863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:12.741304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:41.996671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:41.996946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:42.740991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:12.740998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:42.024827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:42.024928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:42.741030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:12.741039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:42.049823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:42.049889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:42.740869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:12.740740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:42.075868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:42.076278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:42.741285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:12.740810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:42.101070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:42.101146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:42.741261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:12.740901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:42.126381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:42.126502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:42.740822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:12.740736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:42.161182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:42.161258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:42.740810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:12.750090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:42.182650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:42.182715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:42.740797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:12.741306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:42.204610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:42.204672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:42.740958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:12.740863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:42.223475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:42.223685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:42.740832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:12.747678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:42.246671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:42.246713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:42.741210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:12.740860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:42.273451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:42.273505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:42.740795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:12.740851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:42.299758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:42.299820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:42.741184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:12.740977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:42.325175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:42.325231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:42.741807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:12.741668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:42.346433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:42.346498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:42.742441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:12.741988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:42.371490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:42.371562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:42.741472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:12.740972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:42.392179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:42.392392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:42.741180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:12.740792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:42.413969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:42.414043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:42.741947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:12.741262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:42.439226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:42.439353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:42.744008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:12.740797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:42.471196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:42.471266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:42.741229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:12.742664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:42.512602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:42.512723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:42.740699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:12.740872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:42.534226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:42.534290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:42.750700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:12.744009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:42.560289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:42.560599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:42.742026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:12.741265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:42.584054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:42.584117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:42.740810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:12.750093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:42.616311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:42.616393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:42.742748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:12.740930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:42.647372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:42.647427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:42.740785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:12.742023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:42.687939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:42.688010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:42.742328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:55:12.740791 metrics.go:34: INFO No non-zero metrics in the last 30s