By type
2022/04/02 03:27:03.299726 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/04/02 03:27:03.299778 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:27:03.299891 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:27:03.299890 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:27:03.300118 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:27:03.300386 publish.go:295: INFO Publisher name: onap-vfc-vnfres-844dfc67b6-r4mjf
2022/04/02 03:27:03.301462 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:27:03.301489 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:27:03.302089 beat.go:221: INFO filebeat start running.
2022/04/02 03:27:03.302207 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:27:03.306628 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:27:03.306832 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:27:03.307034 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:27:03.307145 sync.go:41: INFO Start sending events to output
2022/04/02 03:27:03.307371 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:27:03.307443 registrar.go:236: INFO Starting Registrar
2022/04/02 03:27:03.307681 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:27:03.307972 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/02 03:27:03.308117 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:27:03.308863 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/04/02 03:27:33.300433 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/04/02 03:28:03.300343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:33.300322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:03.300334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:33.300294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:03.300449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:33.300326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:03.300355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:33.300498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:03.300382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:08.332539 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:32:33.300453 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/04/02 03:33:03.300284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:33.300371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:03.300395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:33.300271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:03.300277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:33.300256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:03.300205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:33.300288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:03.300282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:33.300242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:03.300250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:33.300328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:03.300260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:33.300300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:03.300284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:33.300250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:03.300316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:33.300254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:03.300237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:33.300329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:03.300292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:33.300342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:03.300216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:33.300211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:03.300269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:33.300248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:03.300333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:33.300223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:03.300241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:33.300356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:03.300278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:33.300231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:03.300212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:33.300235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:03.300233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:33.300236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:03.300281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:33.300213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:03.300219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:33.300279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:03.300302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:33.300317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:03.300267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:13.480833 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/04/02 03:54:18.482035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:18.482072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:19.485512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:19.485544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:21.490348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:21.490421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:25.499719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:25.499749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:33.300207 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/04/02 03:54:33.503323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:33.503357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:49.508232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:49.508264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:03.300237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:21.511519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:21.511553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:33.300243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:03.300250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:21.515581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:21.515622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:33.300248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:03.300248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:21.519451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:21.519489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:33.300280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:03.300370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:21.523595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:21.523633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:33.300285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:03.300189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:18.491659 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:59:21.529218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:21.529254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:33.300279 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/04/02 04:00:03.300296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:21.533743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:21.533894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:33.300211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:03.300263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:21.537669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:21.537704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:33.300211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:03.300271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:21.542876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:21.542986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:33.300229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:03.300282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:21.548977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:21.549009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:33.300342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:03.300198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:21.553708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:21.553764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:33.300200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:03.300190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:21.557918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:21.557968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:33.300530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:03.300257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:21.562405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:21.562468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:33.300319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:03.300284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:21.566487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:21.566526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:33.300278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:03.300233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:21.571119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:21.571196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:33.300289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:03.300461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:21.575143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:21.575179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:33.300281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:03.300195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:21.578058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:21.578105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:33.300205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:03.300180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:21.581352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:21.581383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:33.300209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:03.300182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:21.584964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:21.584995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:33.300220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:03.300332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:21.591316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:21.591347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:33.300242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:03.300381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:21.595546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:21.595581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:33.300460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:03.300205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:21.611116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:21.611153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:33.300382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:03.300303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:21.615551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:21.615597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:33.300409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:03.300316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:21.620488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:21.620521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:33.300236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:03.300251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:21.624126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:21.624221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:33.300242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:03.300236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:21.629364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:21.629460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:33.300252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:03.300254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:21.635701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:21.635736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:33.300263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:03.300299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:21.653912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:21.653951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:33.300284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:03.300264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:21.660449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:21.660489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:33.300276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:03.300365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:21.663812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:21.663864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:33.300284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:03.300310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:21.668042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:21.668091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:33.300331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:03.300262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:21.671545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:21.671581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:33.300449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:03.300452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:21.675242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:21.675282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:33.300220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:03.300230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:21.679154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:21.679206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:33.300333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:03.300406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:21.682444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:21.682602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:33.300294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:03.300322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:21.686006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:21.686038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:33.300455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:03.300242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:21.689413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:21.689451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:33.300293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:03.300321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:21.694114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:21.694157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:33.300316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:03.300297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:21.699732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:21.699767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:33.300177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:03.300244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:21.703263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:21.703302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:33.300249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:03.300332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:21.708577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:21.708617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:33.300378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:03.300338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:21.712461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:21.712509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:33.300324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:03.300239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:21.721249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:21.721299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:33.300290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:03.300244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:21.724374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:21.724420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:33.308618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:03.300376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:21.736552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:21.736607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:33.300218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:03.300362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:21.743258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:21.743484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:33.300292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:03.300285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:21.748643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:21.748690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:33.300217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:03.300276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:21.754189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:21.754231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:33.300354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:03.300256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:21.758358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:21.758417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:33.300291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:03.300670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:21.763050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:21.763155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:33.300242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:03.300320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:21.766912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:21.766944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:33.300313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:03.300257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:21.771502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:21.771547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:33.300213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:03.300243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:21.775463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:21.775514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:33.300279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:03.300183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:21.778609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:21.778643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:33.300243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:03.300186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:21.783183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:21.783220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:33.300388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:03.300223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:21.788033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:21.788234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:33.300197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:03.300230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:21.792185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:21.792217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:33.300218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:03.300324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:21.797170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:21.797256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:33.300245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:03.300216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:21.800630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:21.800667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:33.300266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:03.300258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:21.806871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:21.806905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:33.300202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:03.300333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:21.810601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:21.810703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:33.300245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:03.300222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:21.813799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:21.813835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:33.300283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:03.300334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:21.817627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:21.817660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:33.300203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:03.300217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:21.820835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:21.820870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:33.300333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:03.300205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:21.825408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:21.825595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:33.300301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:03.300445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:21.837495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:21.837843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:33.300233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:03.300342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:21.848663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:21.848701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:33.300237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:03.300271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:21.854313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:21.854362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:33.300263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:03.300402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:21.858907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:21.858945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:33.300221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:03.300190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:21.862434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:21.862475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:33.300342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:03.300291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:21.866844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:21.866881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:33.300214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:03.300413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:21.871497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:21.871542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:33.300777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:03.300352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:21.876120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:21.876532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:33.300262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:03.300410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:21.881201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:21.881243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:33.300382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:03.300314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:21.884722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:21.884862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:33.300293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:03.300198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:21.887486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:21.887815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:33.300281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:03.300383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:21.891116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:21.891171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:33.300236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:03.300301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:21.894740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:21.894802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:33.300412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:03.300201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:21.898149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:21.898188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:33.300302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:03.300252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:21.903073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:21.903130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:33.300166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:03.300308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:21.908113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:21.908178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:33.300322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:03.300228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:21.931283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:21.931342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:33.300222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:03.300209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:21.937143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:21.937202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:33.300292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:03.300294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:21.945808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:21.945936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:33.300239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:03.300234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:21.953090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:21.953153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:33.300420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:03.300236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:21.958727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:21.958774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:33.300505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:03.300263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:21.965713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:21.965796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:33.300292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:03.300285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:21.971875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:21.971950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:33.300255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:03.300254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:21.977849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:21.977882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:33.300227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:03.300226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:21.982989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:21.983022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:33.300344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:03.300452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:21.989009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:21.989179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:33.300310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:03.300186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:21.995156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:21.995207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:33.300376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:03.300327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:22.001704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:22.001739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:33.300364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:03.300260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:22.007779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:22.007814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:33.300244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:03.300278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:22.013531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:22.013568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:33.300251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:03.300289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:22.019384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:22.019422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:33.300266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:03.300198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:22.027376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:22.027411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:33.300193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:03.300288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:22.041362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:22.041428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:33.300284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:03.300239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:22.050018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:22.050069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:33.300295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:03.300290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:22.056394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:22.056427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:33.300226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:03.300301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:22.062415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:22.062453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:33.300270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:03.300261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:22.067816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:22.067851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:33.300263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:03.300310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:22.074681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:22.074720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:33.300298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:03.300353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:22.080556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:22.080595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:33.300564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:03.300507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:22.087968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:22.088124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:33.300426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:03.300265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:22.094176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:22.094214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:33.300305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:03.300362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:22.100894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:22.100928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:33.300202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:03.300216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:22.108103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:22.108164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:33.300366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:03.300227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:22.114487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:22.114529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:33.300260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:03.300412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:22.120544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:22.120577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:33.300289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:03.300220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:22.128085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:22.128255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:33.300228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:03.301239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:22.136565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:22.136630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:33.300215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:03.300216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:22.149209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:22.149256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:33.300280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:03.300289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:22.156224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:22.156270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:33.300279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:03.300249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:22.164185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:22.164231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:33.300359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:03.300280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:22.171727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:22.171771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:33.300319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:03.300384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:22.179501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:22.179608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:33.300251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:03.300262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:22.185584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:22.185651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:33.300314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:03.300209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:22.192407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:52:22.192613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:52:33.300320 metrics.go:34: INFO No non-zero metrics in the last 30s