2022/03/24 03:13:19.503115 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/24 03:13:19.503197 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 03:13:19.503323 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 03:13:19.503421 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 03:13:19.503586 publish.go:295: INFO Publisher name: onap-vfc-vnfres-844dfc67b6-6qzm8
2022/03/24 03:13:19.503848 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 03:13:19.503882 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 03:13:19.504649 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 03:13:19.505031 beat.go:221: INFO filebeat start running.
2022/03/24 03:13:19.505309 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 03:13:19.509733 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 03:13:19.509899 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 03:13:19.509954 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 03:13:19.510049 registrar.go:236: INFO Starting Registrar
2022/03/24 03:13:19.510139 sync.go:41: INFO Start sending events to output
2022/03/24 03:13:19.510286 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 03:13:19.510556 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 03:13:19.511142 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/24 03:13:19.511220 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 03:13:19.512355 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/24 03:13:49.505154 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/24 03:14:19.504987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:49.504981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:19.505086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:49.505155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:19.504985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:49.505088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:19.504942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:49.505151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:19.505133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:24.537445 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:18:49.505022 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/24 03:19:19.505058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:49.505122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:19.505066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:49.504965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:19.505191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:49.505047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:19.504979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:49.504937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:19.505165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:49.505005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:19.505174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:49.504986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:19.505020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:49.504960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:19.504956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:49.504970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:19.505003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:49.504957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:19.504986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:49.505060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:19.505186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:49.505018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:19.504935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:49.504968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:19.504974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:49.505057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:19.504943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:49.505019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:19.504953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:49.504956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:19.504939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:49.504931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:19.505191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:49.505034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:19.505061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:49.505035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:19.504951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:49.504951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:19.504926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:49.505055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:19.504924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:49.504969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:19.504977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:19.629899 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/24 03:40:24.627622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:24.627657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:25.632663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:25.632703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:27.635545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:27.635581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:31.642163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:31.642221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:39.647018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:39.647049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:49.504991 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/24 03:40:55.664861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:55.664928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:19.505010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:27.681507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:27.681553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:49.505022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:19.505017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:27.686922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:27.686954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:49.505054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:19.505017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:27.693278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:27.693314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:49.504994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:19.505239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:27.699383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:27.699424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:49.505006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:19.504904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:24.642085 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:45:27.717275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:27.717311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:49.505199 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/24 03:46:19.504967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:27.722807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:27.722838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:49.504960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:19.505023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:27.728359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:27.728402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:49.505042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:19.505001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:27.734921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:27.734965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:49.504968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:19.505357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:27.740400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:27.740454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:49.505065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:19.506546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:27.745920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:27.745959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:49.504968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:19.505214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:27.753163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:27.753194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:49.505032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:19.505011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:27.759179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:27.759212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:49.505134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:19.504983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:27.764225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:27.764278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:49.504964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:19.504957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:27.770005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:27.770044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:49.504941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:19.505101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:27.775889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:27.775935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:49.504961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:19.505109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:27.781664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:27.781710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:49.504990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:19.504968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:27.787924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:27.787986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:49.505097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:19.504942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:27.795954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:27.795996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:49.504917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:19.504978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:27.800788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:27.800830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:49.505018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:19.504908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:27.806657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:27.806830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:49.505036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:19.505007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:27.812991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:27.813030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:49.506387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:19.504968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:27.819523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:27.819563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:49.504947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:19.504958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:27.824974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:27.825032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:49.504990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:19.504976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:27.830421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:27.830462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:49.504974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:19.504978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:27.835862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:27.835904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:49.504974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:19.505020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:27.841265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:27.841297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:49.504973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:19.504995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:27.846720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:27.846765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:49.505108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:19.505117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:27.851811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:27.851847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:49.504928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:19.504983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:27.856459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:27.856491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:49.505632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:19.505048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:27.863184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:27.863232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:49.505013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:19.505094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:27.869263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:27.869315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:49.505040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:19.508673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:27.875512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:27.875603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:49.505182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:19.504926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:27.881442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:27.881474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:49.505018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:19.504972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:27.887352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:27.887396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:49.505004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:19.504940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:27.893169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:27.893308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:49.504971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:19.505024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:27.899358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:27.899427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:49.505076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:19.504997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:27.904857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:27.904890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:49.505057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:19.504988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:27.910401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:27.910435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:49.504950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:19.505006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:27.916225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:27.916370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:49.505101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:19.504993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:27.922812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:27.922852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:49.505016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:19.505020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:27.928076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:27.928114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:49.504942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:19.505109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:27.933176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:27.933221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:49.504917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:19.504920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:27.939798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:27.939832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:49.504986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:19.505172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:27.946614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:27.946670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:49.505421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:19.505632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:27.952708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:27.952902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:49.504947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:19.505031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:27.959123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:27.959340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:49.505069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:19.505012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:27.964684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:27.964721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:49.504888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:19.512793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:27.970378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:27.970452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:49.505023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:19.505026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:27.976649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:27.976843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:49.505049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:19.505047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:27.983990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:27.984025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:49.505070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:19.504984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:27.991547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:27.991598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:49.505055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:19.505818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:27.996924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:27.996956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:49.504928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:19.504989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:28.002024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:28.002177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:49.505023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:19.504935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:28.008182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:28.008217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:49.504999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:19.504971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:28.013622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:28.013658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:49.504958 metrics.go:34: INFO No non-zero metrics in the last 30s