2022/03/16 03:27:28.899207 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/16 03:27:28.899474 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/16 03:27:28.899571 metrics.go:23: INFO Metrics logging every 30s
2022/03/16 03:27:28.899694 logstash.go:90: INFO Max Retries set to: 3
2022/03/16 03:27:28.899883 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/16 03:27:28.900212 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-l2c2h
2022/03/16 03:27:28.900642 async.go:63: INFO Flush Interval set to: 1s
2022/03/16 03:27:28.900741 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/16 03:27:28.901816 beat.go:221: INFO filebeat start running.
2022/03/16 03:27:28.901931 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/16 03:27:28.915412 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/16 03:27:28.915560 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/16 03:27:28.915634 crawler.go:38: INFO Loading Prospectors: 1
2022/03/16 03:27:28.916056 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/16 03:27:28.916192 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/16 03:27:28.916228 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/16 03:27:28.916246 registrar.go:236: INFO Starting Registrar
2022/03/16 03:27:28.916334 sync.go:41: INFO Start sending events to output
2022/03/16 03:27:28.916399 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/16 03:27:28.917591 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/16 03:27:58.901204 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/16 03:28:28.901023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:28:58.900231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:29:28.899994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:29:58.900005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:30:28.900023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:30:58.900175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:31:28.899899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:31:58.899930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:32:28.900040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:32:33.983118 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/16 03:32:58.900135 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/16 03:33:28.900020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:33:58.899943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:34:28.900039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:34:58.899968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:35:28.900807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:35:58.899894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:36:28.899870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:36:58.899931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:37:28.899972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:37:58.900066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:38:28.900161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:38:58.899929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:39:28.899939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:39:58.899918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:40:28.900065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:40:58.899983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:41:28.899910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:41:58.899905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:42:28.899929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:42:58.899941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:43:28.899949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:43:58.899930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:44:28.899909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:44:58.899910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:45:28.900422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:45:58.900262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:46:28.900545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:46:58.899919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:47:28.899934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:47:58.899990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:48:28.899961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:48:58.899905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:49:28.899870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:49:58.900054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:50:28.900002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:50:58.899957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:51:28.899927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:51:58.899984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:52:28.899972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:52:58.901708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:53:28.899907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:53:58.900010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:54:28.900674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:54:58.900023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:55:28.900106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:55:58.899964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:56:28.900311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:56:58.899942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:57:09.134641 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/16 03:57:09.226422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:09.226540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:10.233045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:10.233088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:12.250320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:12.250363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:16.262894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:16.263240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:24.295502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:24.295559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:28.900052 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/16 03:57:40.317177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:40.317258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:58.899901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:58:12.341556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:58:12.341671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:58:28.899878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:58:58.899990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:59:12.375952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:59:12.376146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:59:28.899959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:59:58.899950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:00:12.397871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:00:12.398279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:00:28.899913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:00:58.899919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:01:12.421317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:01:12.421378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:01:28.900088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:01:58.899889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:02:12.443954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:02:12.444235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:02:28.900223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:02:58.899969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:03:12.466929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:03:12.467128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:03:28.899911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:03:58.901078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:04:12.485166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:04:12.485426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:04:28.899839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:04:58.900134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:05:12.506403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:05:12.506578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:05:28.900037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:05:54.188962 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/16 04:05:58.899967 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/16 04:06:12.532998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:06:12.533058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:06:28.900134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:06:58.899983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:07:12.557796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:07:12.557843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:07:28.899946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:07:58.899936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:08:12.582388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:08:12.582449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:08:28.899873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:08:58.900027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:09:12.603958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:09:12.604002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:09:28.899915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:09:58.899977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:10:12.625418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:10:12.625579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:10:28.899906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:10:58.899974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:11:12.645937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:11:12.645999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:11:28.900071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:11:58.899980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:12:12.668026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:12:12.668087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:12:28.900024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:12:58.900201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:13:12.693502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:13:12.693580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:13:28.899922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:13:58.899923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:14:12.713610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:14:12.713662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:14:28.899956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:14:58.901860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:15:12.731445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:15:12.731490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:15:28.899944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:15:58.900004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:16:12.764943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:16:12.765052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:16:28.899880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:16:58.899866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:17:12.793457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:17:12.793528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:17:28.899997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:17:58.899993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:18:12.822875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:18:12.822930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:18:28.900149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:18:58.899903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:19:12.852921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:19:12.852981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:19:28.899794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:19:58.900138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:20:12.875051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:20:12.875119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:20:28.899939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:20:58.899936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:21:12.900734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:21:12.900798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:21:28.899860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:21:58.900004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:22:12.922568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:22:12.922626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:22:28.899950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:22:58.900024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:23:12.951973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:23:12.952029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:23:28.900064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:23:58.899874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:24:12.970808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:24:12.970919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:24:28.899910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:24:58.899946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:25:12.999801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:25:12.999853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:25:28.904379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:25:58.900011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:26:13.020530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:26:13.020584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:26:28.899842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:26:58.900405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:27:13.050392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:27:13.050472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:27:28.900209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:27:58.899935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:28:13.076901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:28:13.076946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:28:28.899895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:28:58.899903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:29:13.096587 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:29:13.096629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:29:28.899970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:29:58.899963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:30:13.116139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:30:13.116188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:30:28.899869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:30:58.899850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:31:13.145731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:31:13.145786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:31:28.899888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:31:58.899982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:32:13.167096 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:32:13.167150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:32:28.899892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:32:58.899915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:33:13.183996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:33:13.184244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:33:28.899991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:33:58.900039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:34:13.202745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:34:13.202790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:34:28.899939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:34:58.899963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:35:13.223475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:35:13.223533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:35:28.899998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:35:58.899992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:36:13.256913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:36:13.256964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:36:28.899906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:36:58.899833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:37:13.279577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:37:13.279675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:37:28.899825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:37:58.899923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:38:13.301812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:38:13.301977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:38:28.899932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:38:58.899900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:39:13.324570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:39:13.324611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:39:28.899894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:39:58.900010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:40:13.353682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:40:13.353741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:40:28.899977 metrics.go:34: INFO No non-zero metrics in the last 30s