By type
2022/03/24 03:12:50.954447 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/24 03:12:50.954518 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 03:12:50.954667 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 03:12:50.954788 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 03:12:50.954842 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 03:12:50.954980 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-ndwnb
2022/03/24 03:12:50.955373 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 03:12:50.955400 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 03:12:50.956199 beat.go:221: INFO filebeat start running.
2022/03/24 03:12:50.956370 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 03:12:50.959737 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 03:12:50.959824 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 03:12:50.959890 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 03:12:50.960238 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 03:12:50.960423 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/24 03:12:50.960460 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 03:12:50.960478 registrar.go:236: INFO Starting Registrar
2022/03/24 03:12:50.960566 sync.go:41: INFO Start sending events to output
2022/03/24 03:12:50.960627 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 03:12:50.961486 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/24 03:13:20.955381 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/03/24 03:13:50.955165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:20.955283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:50.955268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:20.955282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:50.955346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:20.955225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:50.955710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:20.955142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:50.955387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:55.972057 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:18:20.955395 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/24 03:18:50.955220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:20.955200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:50.955244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:20.955263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:50.955155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:20.955178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:50.955264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:20.955164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:50.955174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:20.955245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:50.955159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:20.955133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:50.955192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:20.955118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:50.955101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:20.955210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:50.955212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:20.955289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:50.955228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:20.955360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:50.955179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:20.955172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:50.955210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:20.955110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:50.955117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:20.955117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:50.955215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:20.955255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:50.955155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:20.955154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:50.955161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:20.955181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:50.955208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:20.955248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:50.955244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:20.955111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:50.955113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:20.955173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:50.955160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:20.955243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:50.955206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:20.955096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:50.955327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:20.955187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:21.156026 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/24 03:40:26.113706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:26.113741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:27.120352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:27.120408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:29.126129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:29.126217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:33.142857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:33.142905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:41.149759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:41.149795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:50.955158 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/03/24 03:40:57.169073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:57.169119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:20.955124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:29.187212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:29.187282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:50.955387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:20.955357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:29.204974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:29.205016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:50.955122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:20.955266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:29.222752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:29.222829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:50.955393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:20.955179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:29.240564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:29.240607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:50.955154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:20.955100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:26.175874 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:45:29.299138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:29.299191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:50.955191 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/24 03:46:20.955196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:29.317309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:29.317362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:50.955158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:20.955192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:29.334514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:29.334565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:50.955112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:20.955148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:29.353492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:29.353544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:50.955139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:20.955158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:29.372904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:29.372958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:50.955526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:20.955210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:29.391793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:29.391843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:50.955203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:20.955219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:29.410736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:29.410773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:50.955082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:20.955187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:29.432940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:29.433003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:50.955270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:20.955158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:29.451662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:29.451744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:50.955188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:20.955114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:29.471291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:29.471396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:50.955189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:20.955153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:29.489893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:29.490067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:50.955143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:20.955174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:29.511615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:29.511654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:50.955467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:20.955123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:29.554106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:29.554147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:50.955459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:20.955220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:29.575461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:29.575515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:50.955111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:20.955191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:29.594491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:29.594538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:50.955138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:20.955139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:29.613500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:29.613547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:50.955171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:20.955091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:29.631502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:29.631568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:50.955128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:20.955180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:29.647627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:29.647671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:50.955168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:20.955135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:29.663542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:29.663576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:50.955108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:20.955186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:29.684479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:29.684547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:50.955371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:20.955484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:29.702896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:29.702946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:50.955178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:20.955094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:29.720550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:29.720599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:50.955124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:20.955183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:29.743916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:29.743973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:50.955197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:20.955166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:29.763385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:29.763432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:50.955667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:20.955121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:29.783084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:29.783132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:50.955194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:20.955230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:29.823774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:29.823827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:50.955180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:20.955174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:29.850502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:29.850560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:50.955114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:20.955269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:29.874362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:29.874408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:50.955200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:20.955404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:29.892959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:29.893029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:50.955226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:20.955251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:29.922723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:29.922792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:50.955127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:20.955114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:29.940562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:29.940704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:50.955211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:20.955173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:29.965723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:29.965775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:50.955249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:20.955199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:29.983516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:29.983552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:50.955217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:20.955139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:30.002555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:30.002601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:50.955220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:20.955132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:30.021135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:30.021172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:50.955196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:20.955344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:30.045531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:30.045578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:50.955482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:20.955611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:30.062266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:30.062303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:50.955179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:20.955205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:30.079237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:30.079281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:50.955090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:20.955117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:30.099434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:30.099569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:50.955161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:20.955236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:30.119622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:30.119672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:50.955148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:20.955169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:30.137081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:30.137135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:50.955122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:20.955157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:30.156088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:30.156131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:50.955220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:20.955161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:30.174800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:30.175129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:50.955219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:20.955177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:30.194006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:30.194046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:50.955172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:20.955750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:30.212449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:30.212489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:50.955176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:20.955450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:30.231561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:30.231605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:50.955177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:20.955243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:30.253801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:30.254017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:50.955248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:20.955145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:30.271706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:30.271760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:50.955190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:20.955199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:30.291406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:30.291478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:50.955142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:20.955203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:30.308773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:30.308934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:50.955128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:20.955155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:30.340606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:30.340655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host