Results

          2022/03/26 03:14:33.511126 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/26 03:14:33.511184 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/26 03:14:33.511359 logstash.go:90: INFO Max Retries set to: 3
2022/03/26 03:14:33.511515 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/26 03:14:33.511767 metrics.go:23: INFO Metrics logging every 30s
2022/03/26 03:14:33.511845 publish.go:295: INFO Publisher name: onap-vfc-vnflcm-84bd7747bf-zcndm
2022/03/26 03:14:33.512323 async.go:63: INFO Flush Interval set to: 1s
2022/03/26 03:14:33.512771 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/26 03:14:33.513547 beat.go:221: INFO filebeat start running.
2022/03/26 03:14:33.513629 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/26 03:14:33.520840 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/26 03:14:33.520941 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/26 03:14:33.521044 crawler.go:38: INFO Loading Prospectors: 1
2022/03/26 03:14:33.521141 sync.go:41: INFO Start sending events to output
2022/03/26 03:14:33.521076 registrar.go:236: INFO Starting Registrar
2022/03/26 03:14:33.521327 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/26 03:14:33.521372 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/26 03:14:33.521780 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/26 03:14:33.521939 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/26 03:14:33.522644 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/26 03:15:03.512332 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/26 03:15:33.512235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:03.512523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:33.512379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:03.512401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:33.512380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:03.512280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:33.512323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:03.512363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:33.512382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:38.534351 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:20:03.512386 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/26 03:20:33.512282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:03.512226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:33.512373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:03.512347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:33.512448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:03.512404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:33.512205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:03.512301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:33.512468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:03.512223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:33.512302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:03.512285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:33.512277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:03.512307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:33.512317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:03.512340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:33.512232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:03.512334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:33.512218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:03.512277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:33.512300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:03.512541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:33.512300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:03.512249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:33.512514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:03.512432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:33.512240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:03.512299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:33.512262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:03.512220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:33.512188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:03.512379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:33.512481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:03.512287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:33.512258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:03.512289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:33.512236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:03.513028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:33.512350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:03.512278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:33.512302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:03.512331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:33.512299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:03.512367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:33.515873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:53.687849 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/26 03:42:58.686830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:58.686873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:59.690260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:59.690294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:01.694267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:01.694310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:03.512280 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/26 03:43:05.700541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:05.700571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:13.706561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:13.706601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:29.722651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:29.722695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:33.512330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:01.751932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:44:01.752015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:44:03.512347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:33.512253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:01.777504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:45:01.777538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:45:03.512350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:33.512337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:01.796555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:46:01.796595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:46:03.512320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:33.512337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:01.813439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:47:01.813588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:47:03.512262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:33.512219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:01.831763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:48:01.831902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:48:03.512308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:33.512248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:01.859901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:49:01.859937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:49:03.512245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:33.512369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:01.879769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:50:01.879801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:50:03.512244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:33.512282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:01.898873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:51:01.898912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:51:03.512337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:28.715725 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:51:33.512238 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/26 03:52:01.918221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:52:01.918253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:52:03.512363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:33.512286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:01.934166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:53:01.934203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:53:03.512245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:33.512279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:01.960546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:54:01.960592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:54:03.512247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:33.512257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:01.983017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:55:01.983087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:55:03.512294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:33.512207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:02.006047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:56:02.006114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:56:03.512218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:33.512315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:02.029700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:57:02.029757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:57:03.512250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:33.512308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:02.058614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:58:02.058649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:58:03.512271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:33.512290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:02.077780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:59:02.077825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:59:03.512265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:33.512281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:02.099895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:00:02.099932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:00:03.512342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:33.512273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:02.118059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:01:02.118104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:01:03.512355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:33.512410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:02.136545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:02:02.136611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:02:03.512353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:33.512453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:02.172210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:03:02.172362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:03:03.512446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:33.512237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:02.190054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:04:02.190108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:04:03.512337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:33.512280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:02.211486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:05:02.211527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:05:03.512275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:33.512191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:02.229395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:06:02.229438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:06:03.512266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:33.512322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:02.249754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:07:02.249793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:07:03.512276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:33.512495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:02.284553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:08:02.284608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:08:03.512263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:33.512270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:02.302683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:09:02.302716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:09:03.512270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:33.512347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:02.321826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:10:02.321864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:10:03.512242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:33.512269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:02.342525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:11:02.342571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:11:03.512335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:33.512243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:02.365468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:12:02.365512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:12:03.512299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:33.512332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:02.383552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:13:02.383614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:13:03.512980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:33.512246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:02.401997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:14:02.402152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:14:03.512248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:33.512202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:02.419819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:15:02.419864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:15:03.512216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:33.512366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:02.439043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:16:02.439077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:16:03.512335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:33.512499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:02.495999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:17:02.496059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:17:03.512334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:33.512248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:02.513262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:18:02.513295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:18:03.512315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:33.512252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:02.530703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:19:02.530746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:19:03.512268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:33.512253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:02.565134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:20:02.565175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:20:03.512324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:33.512307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:02.588139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:21:02.588195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:21:03.512278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:33.512205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:02.603928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:22:02.603960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:22:03.512308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:33.512266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:02.622185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:23:02.622224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:23:03.512298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:33.512344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:02.640759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:24:02.640830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:24:03.512216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:33.512300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:02.665306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:25:02.665377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:25:03.512284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:33.512338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:02.689165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:26:02.689245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:26:03.512279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:33.512267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:02.710117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:27:02.710155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:27:03.512306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:33.512224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:02.841009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:28:02.841058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:28:03.558408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:33.512195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:02.879201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:29:02.879254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:29:03.512322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:33.512318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:02.896027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:30:02.896087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:30:03.512288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:33.512288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:02.917298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:31:02.918605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:31:03.512288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:33.512273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:02.938164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:32:02.938232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:32:03.512303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:33.512508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:02.960809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:33:02.960854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:33:03.513851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:33.512267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:03.114118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:34:03.114158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:34:03.512288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:33.512290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:03.131291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:35:03.131329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:35:03.512303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:33.512712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:03.151488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:36:03.151533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:36:03.512270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:33.512250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:03.168360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:37:03.168395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:37:03.512296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:33.512188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:03.186868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:38:03.186903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:38:03.512254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:33.512334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:03.206720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:39:03.206886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:39:03.512313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:33.512576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:03.226731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:40:03.226783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:40:03.512340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:33.514917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:03.252010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:41:03.252074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:41:03.512266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:33.512198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:42:03.276030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:42:03.276084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:42:03.512353 metrics.go:34: INFO No non-zero metrics in the last 30s