By type
2022/04/02 03:26:24.804594 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/04/02 03:26:24.804840 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:26:24.805072 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:26:24.805317 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:26:24.805840 publish.go:295: INFO Publisher name: onap-vfc-vnflcm-84bd7747bf-cfxk7
2022/04/02 03:26:24.806283 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:26:24.806368 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:26:24.807618 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:26:24.807638 beat.go:221: INFO filebeat start running.
2022/04/02 03:26:24.807863 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:26:24.833503 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:26:24.833647 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:26:24.833815 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:26:24.834038 registrar.go:236: INFO Starting Registrar
2022/04/02 03:26:24.834159 sync.go:41: INFO Start sending events to output
2022/04/02 03:26:24.834344 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:26:24.834698 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:26:24.834887 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/02 03:26:24.834920 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:26:24.835933 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/04/02 03:26:54.808486 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/04/02 03:27:24.808090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:27:54.808357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:24.808246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:54.808137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:24.808245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:54.808022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:24.808029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:54.808292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:24.808153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:29.853948 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:31:54.812981 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/04/02 03:32:24.808096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:54.808223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:24.807982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:54.808148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:24.808053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:54.808402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:24.808051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:54.807954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:24.808231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:54.809660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:24.807996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:54.808054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:24.808081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:54.808381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:24.808027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:54.808078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:24.810685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:54.808010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:24.808318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:54.808069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:24.808007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:54.808034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:24.808320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:54.808025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:24.808036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:54.808059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:24.812590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:54.808018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:24.808059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:54.808114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:24.808438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:54.808044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:24.808744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:54.808003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:24.808062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:54.808081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:24.808006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:54.808047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:24.808136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:54.808058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:24.811207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:54.812382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:24.808147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:54.808000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:05.079421 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/04/02 03:54:10.072554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:10.072654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:11.078458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:11.078589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:13.083993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:13.084048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:17.092948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:17.093021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:24.808068 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/04/02 03:54:25.102595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:25.102644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:41.130310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:41.130388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:54.808073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:13.152514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:13.152611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:24.808095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:54.808239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:13.171965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:13.172003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:24.809904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:54.808042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:13.193532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:13.193578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:24.808121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:54.808348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:13.215233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:13.215309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:24.807983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:54.808157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:10.120165 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:59:13.234506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:13.234551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:24.808534 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/04/02 03:59:54.808124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:13.257411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:13.257459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:24.808162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:54.808131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:13.276525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:13.276595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:24.808348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:54.808045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:13.301915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:13.301973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:24.808043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:54.808718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:13.321533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:13.321585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:24.809342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:54.808118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:13.343712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:13.343762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:24.808110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:54.808030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:13.363400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:13.363570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:24.808287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:54.808014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:13.385000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:13.385065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:24.808058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:54.808075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:13.404964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:13.405017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:24.808104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:54.808043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:13.425833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:13.425871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:24.808062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:54.815078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:13.461853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:13.461945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:24.808249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:54.808173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:13.483695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:13.483746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:24.808013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:54.808046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:13.511655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:13.511765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:24.808035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:54.808092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:13.536645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:13.536702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:24.808073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:54.808245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:13.559665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:13.559826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:24.808037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:54.808162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:13.581971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:13.582039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:24.808412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:54.808115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:13.602193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:13.602510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:24.808172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:54.808078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:13.627761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:13.627864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:24.808004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:54.808007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:13.650628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:13.650688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:24.808009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:54.808082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:13.668961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:13.669025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:24.808111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:54.808482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:13.701939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:13.702004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:24.808104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:54.807992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:13.723367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:13.723564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:24.808104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:54.808064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:13.743521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:13.743562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:24.808105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:54.808045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:13.770441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:13.770489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:24.808102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:54.808170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:13.797618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:13.797754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:24.808501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:54.808139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:13.818942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:13.818996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:24.808000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:54.808609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:13.847478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:13.847546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:24.808116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:54.808082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:13.869732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:13.869801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:24.808343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:54.808285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:13.890082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:13.890133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:24.808477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:54.808215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:13.917443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:13.917505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:24.808157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:54.808080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:13.940497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:13.940547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:24.808101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:54.808426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:13.960159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:13.960238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:24.808389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:54.808145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:13.981473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:13.981603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:24.808040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:54.807981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:14.001970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:14.002016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:24.808065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:54.808053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:14.026543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:14.026613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:24.808295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:54.808020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:14.051724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:14.051789 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:24.808692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:54.808175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:14.136612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:14.136675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:24.808109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:54.808285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:14.158816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:14.158877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:24.808115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:54.807984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:14.179380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:14.179496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:24.808115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:54.808118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:14.198998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:14.199146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:24.809814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:54.808052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:14.217802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:14.217847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:24.808075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:54.808144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:14.247278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:14.247344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:24.807949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:54.808062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:14.265607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:14.265647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:24.808489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:54.808075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:14.421440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:14.421513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:24.808003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:54.808444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:14.443930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:14.443990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:24.808036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:54.807990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:14.463853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:14.463902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:24.808079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:54.808053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:14.485224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:14.485289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:24.808307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:54.808070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:14.505972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:14.506036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:24.808063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:54.808143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:14.526892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:14.526949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:24.807986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:54.808022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:14.546778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:14.547382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:24.808065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:54.808045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:14.569642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:14.569856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:24.808064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:54.808077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:14.590813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:14.590857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:24.809235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:54.808768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:14.614075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:14.614120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:24.807975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:54.808163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:14.637889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:14.637940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:24.808085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:54.807985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:14.689633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:14.689720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:24.808371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:54.808000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:14.706811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:14.706877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:24.808039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:54.808022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:14.734931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:14.735031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:24.808010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:54.808334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:14.788247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:14.788291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:24.808090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:54.808004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:14.815724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:14.815839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:24.807983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:54.808036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:14.841595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:14.841668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:24.808241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:54.808156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:14.863187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:14.863247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:24.807963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:54.807965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:14.884759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:14.884812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:24.808006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:54.808702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:14.904275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:14.904335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:24.808358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:54.807972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:14.925220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:14.925361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:24.808245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:54.809307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:14.958869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:14.959047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:24.808029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:54.808172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:14.988139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:14.988315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:24.808061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:54.807971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:15.015612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:15.015694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:24.807973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:54.808020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:15.038101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:15.038161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:24.808074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:54.808170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:15.069940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:15.070121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:24.808086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:54.808053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:15.099834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:15.099907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:24.808020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:54.808026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:15.122284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:15.122375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:24.808026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:54.808148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:15.146001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:15.146062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:24.808073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:54.808043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:15.185334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:15.185408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:24.808003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:54.808266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:15.203692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:15.203771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:24.808074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:54.808337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:15.227707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:15.227765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:24.808147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:54.808156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:15.266754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:15.266942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:24.808000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:54.808090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:15.288833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:15.288889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:24.808008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:54.808034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:15.311388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:15.311443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:24.808120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:54.808303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:15.330483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:15.330534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:24.807991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:54.808173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:15.349619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:15.349661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:24.808049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:54.808128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:15.370735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:15.370796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:24.808049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:54.808239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:15.394120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:15.394182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:24.808238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:54.808116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:15.414050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:15.414182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:24.808046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:54.808045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:15.441350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:15.441404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:24.807982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:54.807966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:15.465589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:15.465683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:24.808078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:54.808458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:15.485042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:15.485099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:24.808081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:54.808012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:15.508308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:15.508355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:24.808041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:54.808238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:15.532412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:15.532627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:24.807983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:54.808075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:15.553486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:15.553708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:24.807968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:54.808094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:15.574433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:15.574491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:24.813028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:54.808138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:15.597332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:15.597489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:24.808004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:54.808352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:15.620561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:15.620643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:24.808030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:54.808306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:15.640257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:15.640304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:24.807969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:54.808262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:15.661545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:15.661613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:24.808358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:54.808071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:15.679818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:15.680032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:24.808097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:54.808031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:15.698579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:15.698619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:24.808022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:54.807947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:15.716955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:15.717014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:24.807982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:54.808326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:15.739658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:15.739727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:24.808155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:54.811404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:15.759539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:15.759590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:24.807938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:54.808028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:15.780833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:15.780904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:24.808320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:54.808059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:15.804451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:15.804513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:24.808098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:54.808137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:15.827371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:15.827436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:24.808000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:54.808022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:15.847243 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:15.847315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:24.807957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:54.808090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:15.867046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:15.867356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:24.808180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:54.808522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:15.888928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:15.888966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:24.808181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:54.807999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:15.908463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:15.908522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:24.808101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:54.807973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:15.939270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:15.939499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:24.807973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:54.808081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:15.967605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:15.967696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:24.808058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:54.808158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:15.987436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:15.987483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:24.808146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:54.808033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:16.012181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:16.012402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:24.808027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:54.808068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:16.032966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:16.033012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:24.808002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:54.809174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:16.059000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:16.059074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:24.808040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:54.808390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:16.079897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:16.079951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:24.808130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:54.807948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:16.103160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:52:16.103246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:52:24.807989 metrics.go:34: INFO No non-zero metrics in the last 30s