Results

          2022/03/05 03:31:24.866365 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:31:24.866423 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:31:24.866512 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:31:24.866642 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:31:24.866734 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:31:24.866831 publish.go:295: INFO Publisher name: onap-vfc-vnfres-844dfc67b6-g9clp
2022/03/05 03:31:24.867063 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:31:24.867090 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:31:24.867733 beat.go:221: INFO filebeat start running.
2022/03/05 03:31:24.867827 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:31:24.871864 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:31:24.871992 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:31:24.872076 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:31:24.872321 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:31:24.872492 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/05 03:31:24.872614 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:31:24.872646 sync.go:41: INFO Start sending events to output
2022/03/05 03:31:24.872762 registrar.go:236: INFO Starting Registrar
2022/03/05 03:31:24.872942 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:31:24.873439 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/05 03:31:54.869533 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:32:24.868019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:54.867203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:24.867199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:54.867098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:24.872532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:54.867153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:24.867224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:54.867748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:24.867081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:29.914128 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/05 03:36:54.867199 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:37:24.867183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:54.867132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:24.867172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:54.867346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:24.868666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:54.867294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:24.867103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:54.867347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:24.867150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:54.867132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:24.867372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:54.867083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:24.867217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:54.867138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:24.867073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:54.867359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:24.867192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:54.867440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:24.867156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:54.867145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:24.867155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:54.867261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:24.867114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:54.867172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:24.867116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:54.867222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:24.867075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:54.867050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:24.867091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:54.867205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:24.867145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:54.867141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:24.867122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:54.867333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:24.867134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:54.867179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:24.867107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:54.867173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:24.867126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:54.867214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:24.867108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:54.867133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:24.867060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:35.060053 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/05 03:58:40.033161 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:40.033199 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.037296 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.037336 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:43.041163 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:43.041205 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:47.059676 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:47.059992 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:54.867983 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:55.070322 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:55.070375 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:11.077871 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:11.077915 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:24.867158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:43.084651 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:43.084692 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:54.868818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:24.867760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:43.090978 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:43.091016 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:54.867076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:24.867138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:43.099133 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:43.099173 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:54.867169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:24.867107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:43.106279 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:43.106329 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:54.867076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:24.867090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:40.072859 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/05 04:03:43.114130 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:43.114177 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:54.867142 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:24.867061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:43.120848 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:43.120884 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:54.867284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:24.867104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:43.138243 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:43.138290 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:54.867103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:24.867120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:43.145248 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:43.145285 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:54.867096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:24.867210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:43.152436 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:43.152475 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:54.868091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:24.867118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:43.161675 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:43.161716 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:54.867093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:24.867186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:43.172716 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:43.172775 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:54.867210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:24.867213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:43.185082 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:43.185121 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:54.867108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:24.867202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:43.192179 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:43.192219 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:54.867130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:24.867179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:43.205069 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:43.205109 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:54.867912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:24.867372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:43.214293 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:43.214625 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:54.867189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:24.867080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:43.221494 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:43.221533 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:54.867089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:24.867566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:43.233221 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:43.233259 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:54.867324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:24.867170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:43.244359 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:43.244397 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:54.867130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:24.867521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:43.251660 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:43.251796 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:54.867178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:24.867114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:43.287083 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:43.287140 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:54.867122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:24.867396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:43.299499 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:43.299545 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:54.868129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:24.867154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:43.306745 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:43.306784 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:54.867079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:24.867102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:43.323184 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:43.323223 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:54.867188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:24.867129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:43.330909 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:43.331024 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:54.867103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:24.867219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:43.338103 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:43.338158 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:54.876086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:24.867143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:43.345624 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:43.345760 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:54.871340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:24.867098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:43.352661 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:43.352733 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:54.867145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:24.867961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:43.360124 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:43.360190 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:54.868159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:24.867248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:43.367967 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:43.368067 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:54.867462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:24.867086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:43.379589 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:43.379630 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:54.867076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:24.875776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:43.401524 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:43.401565 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:54.867167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:24.867994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:43.408006 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:43.408042 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:54.867178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:24.867100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:43.425730 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:43.425802 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:54.867069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:24.867160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:43.436431 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:43.436557 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:54.867067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:24.867106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:43.443166 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:43.443211 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:54.867093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:24.867560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:43.455301 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:43.455354 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:54.867181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:24.871415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:43.468642 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:43.468684 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:54.867124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:24.867220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:43.477542 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:43.477601 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:54.867084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:24.869468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:43.485127 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:43.485170 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:54.867259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:24.867061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:43.493009 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:43.493054 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:54.867124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:24.867412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:43.506536 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:43.506575 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:54.867228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:24.867659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:43.513917 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:43.513971 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:54.868045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:24.868181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:43.545897 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:43.545934 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:54.867639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:24.867141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:43.552687 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:43.552726 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:54.867125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:24.867112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:43.558816 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:43.558855 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:54.867112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:24.867083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:43.570339 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:43.570384 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:54.867100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:24.867063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:43.577651 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:43.577685 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:54.867220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:24.867267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:43.584583 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:43.584650 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:54.867116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:24.867169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:43.597091 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:43.597129 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:54.867203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:24.867265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:43.604143 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:43.604189 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:54.869755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:24.867517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:43.613172 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:43.613585 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:54.867127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:24.867761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:43.623551 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:43.623727 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:54.867529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:24.867150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:43.631986 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:43.632029 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:54.867142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:24.867149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:43.639346 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:43.639394 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:54.867358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:24.867143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:43.646337 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:43.646374 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:54.867205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:24.867097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:43.654368 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:43.654426 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:54.867234 metrics.go:34: INFO No non-zero metrics in the last 30s