By type
2022/03/13 03:18:47.803860 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/13 03:18:47.803939 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/13 03:18:47.804051 logstash.go:90: INFO Max Retries set to: 3
2022/03/13 03:18:47.804157 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/13 03:18:47.805104 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-757xf
2022/03/13 03:18:47.805369 async.go:63: INFO Flush Interval set to: 1s
2022/03/13 03:18:47.805391 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/13 03:18:47.807794 beat.go:221: INFO filebeat start running.
2022/03/13 03:18:47.807859 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/13 03:18:47.807988 metrics.go:23: INFO Metrics logging every 30s
2022/03/13 03:18:47.813517 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/13 03:18:47.813619 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/13 03:18:47.813670 crawler.go:38: INFO Loading Prospectors: 1
2022/03/13 03:18:47.813683 registrar.go:236: INFO Starting Registrar
2022/03/13 03:18:47.813815 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/13 03:18:47.813788 sync.go:41: INFO Start sending events to output
2022/03/13 03:18:47.813857 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/13 03:18:47.813959 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/13 03:18:47.813985 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/13 03:18:47.814790 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/13 03:19:17.808554 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/13 03:19:47.808385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:17.808363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:47.808364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:17.808435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:47.808392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:17.808591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:47.808442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:17.808411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:47.808416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:52.825476 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:24:17.808363 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/13 03:24:47.808525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:17.809037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:47.816826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:17.808454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:47.808359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:17.808655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:47.808245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:17.808641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:47.808442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:17.808331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:47.808421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:17.808405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:47.808399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:17.808518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:47.808534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:17.808870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:47.808391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:17.808321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:47.808644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:17.808560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:47.808575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:17.808485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:47.808450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:17.808352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:47.808343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:17.808415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:47.808383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:17.808355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:47.808357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:17.808437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:47.808312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:17.810093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:47.810079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:17.808320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:47.808410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:17.808490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:47.808295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:17.808307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:47.808351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:17.808651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:47.808439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:17.808459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:47.808340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:17.808599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:47.808369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:17.810844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:47.808457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:07.983075 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/13 03:48:12.934821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:12.934891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:13.939010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:13.939083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:15.942291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:15.942324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:17.808461 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/13 03:48:19.946709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:19.946929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:27.952275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:27.952341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:43.956209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:43.956276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:47.808402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:15.971128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:15.971279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:17.808527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:47.808422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:15.974774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:15.974818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:17.808358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:47.808383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:15.979117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:15.979191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:17.808389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:47.808436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:15.982798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:15.982838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:17.808353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:47.808405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:12.995201 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:53:15.989112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:15.989174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:17.808595 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/13 03:53:47.809545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:15.993616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:15.993657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:17.808681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:47.808621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:15.998533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:15.998576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:17.810076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:47.808342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:16.003751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:16.003793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:17.808317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:47.810389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:16.010852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:16.010895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:17.808268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:47.808349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:16.017953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:16.018001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:17.808634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:47.808329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:16.022333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:16.022478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:17.808469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:47.808631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:16.026953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:16.026996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:17.808543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:47.808406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:16.030803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:16.030882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:17.808512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:47.808375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:16.034712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:16.034840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:17.808314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:47.808338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:16.039138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:16.039183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:17.809659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:47.808406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:16.042376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:16.042432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:17.808413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:47.808304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:16.048043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:16.048095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:17.808405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:47.808398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:16.052182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:16.052225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:17.808395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:47.809427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:16.057308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:16.057362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:17.808401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:47.808420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:16.061328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:16.061370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:17.808370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:47.808343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:16.065834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:16.065900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:17.808533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:47.808380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:16.069265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:16.069309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:17.808333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:47.808377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:16.074618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:16.074659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:17.808319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:47.808542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:16.078143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:16.078192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:17.808886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:47.808463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:16.081526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:16.081568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:17.808438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:47.808402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:16.100969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:16.101026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:17.812036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:47.808320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:16.105842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:16.106221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:17.808442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:47.808339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:16.112087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:16.112208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:17.808446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:47.808666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:16.115373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:16.115454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:17.808307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:47.808387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:16.119978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:16.120033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:17.808383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:47.808361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:16.125055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:16.125106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:17.812113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:47.808690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:16.128905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:16.128953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:17.808879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:47.808331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:16.132903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:16.132947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:17.808337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:47.808444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:16.138010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:16.138055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:17.808408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:47.808335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:16.141247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:16.141286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:17.808495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:47.808375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:16.145110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:16.145202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:17.808396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:47.809928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:16.149098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:16.149136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:17.808362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:47.808488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:16.153948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:16.153994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:17.808460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:47.808409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:16.157324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:16.157361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:17.808433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:47.808660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:16.162537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:16.162605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:17.808380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:47.808371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:16.166973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:16.167009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:17.808346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:47.808334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:16.171087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:16.171155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:17.823329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:47.808932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:16.175735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:16.175787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:17.808427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:47.808331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:16.180071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:16.180107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:17.808637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:47.808528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:16.185547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:16.185613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:17.808348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:47.808352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:16.189467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:16.189560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:17.808336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:47.808378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:16.193221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:16.193262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:17.808337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:47.808560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:16.198188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:16.198231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:17.808404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:47.808448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:37:16.203348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:37:16.203571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:37:17.808389 metrics.go:34: INFO No non-zero metrics in the last 30s