By type
2022/04/02 03:26:20.013064 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:26:20.013239 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:26:20.013252 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:26:20.013613 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:26:20.014023 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:26:20.014782 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-7d4f6
2022/04/02 03:26:20.015425 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:26:20.015513 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:26:20.017459 beat.go:221: INFO filebeat start running.
2022/04/02 03:26:20.017587 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:26:20.075964 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:26:20.076057 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:26:20.076185 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:26:20.076390 registrar.go:236: INFO Starting Registrar
2022/04/02 03:26:20.076550 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:26:20.076622 sync.go:41: INFO Start sending events to output
2022/04/02 03:26:20.076630 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:26:20.076773 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/02 03:26:20.076806 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:26:20.077361 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/04/02 03:26:50.014833 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:27:20.014835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:27:50.013563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:20.013806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:50.013657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:20.013526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:50.013631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:20.013567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:50.013696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:20.013558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:25.126509 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:31:50.013794 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:32:20.013519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:50.013622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:20.013611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:50.013657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:20.013766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:50.013619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:20.013647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:50.013669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:20.013627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:50.013571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:20.013591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:50.013529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:20.013570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:50.013675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:20.013603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:50.013522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:20.013583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:50.013512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:20.013637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:50.013625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:20.013554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:50.013577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:20.013593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:50.013549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:20.013655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:50.013727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:20.013524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:50.013663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:20.013566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:50.013622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:20.013550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:50.013628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:20.013605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:50.013524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:20.013670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:50.013592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:20.013581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:50.013625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:20.013518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:50.013662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:20.013549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:50.013623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:20.015803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:50.013732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:10.295856 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/04/02 03:54:10.324131 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:10.324174 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:11.327398 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:11.327430 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:13.330779 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:13.330906 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:17.337158 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:17.337292 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:20.013592 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:25.345759 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.345792 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:41.371337 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:41.371369 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:50.013487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:13.392007 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:13.392051 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:20.013583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:50.013491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:13.408594 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:13.408641 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:20.013553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:50.014071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:13.425639 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:13.425676 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:20.013696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:50.013719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:13.447304 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:13.447339 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:20.013518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:50.013515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:13.463044 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:13.463080 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:15.318637 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:59:20.013610 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 03:59:50.013516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:13.480802 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:13.480914 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:20.013559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:50.013516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:13.498047 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:13.498085 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:20.013556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:50.013515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:13.514386 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:13.514441 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:20.013649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:50.013684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:13.532767 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:13.532953 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:20.013690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:50.013531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:13.551835 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:13.551871 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:20.013710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:50.013542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:13.568048 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:13.568081 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:20.013523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:50.013541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:13.585205 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:13.585240 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:20.013594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:50.013623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:13.601205 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:13.601234 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:20.013795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:50.013519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:13.618814 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:13.618877 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:20.013512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:50.013551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:13.637094 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:13.637187 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:20.013566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:50.013550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:13.655361 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:13.655481 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:20.013598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:50.013568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:13.673197 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:13.673251 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:20.013599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:50.013679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:13.690843 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:13.690894 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:20.013583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:50.014072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:13.708829 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:13.708882 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:20.013649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:50.013511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:13.727032 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:13.727064 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:20.013592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:50.013612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:13.748088 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:13.748143 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:20.013568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:50.013510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:13.767679 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:13.767720 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:20.014482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:50.013544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:13.787295 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:13.787332 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:20.013500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:50.013581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:13.804240 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:13.804284 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:20.013636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:50.013565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:13.821069 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:13.821297 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:20.013500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:50.013617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:13.837730 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:13.837791 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:20.013570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:50.013640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:13.854083 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:13.854118 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:20.013659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:50.013588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:13.876506 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:13.876879 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:20.013493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:50.013569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:13.897260 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:13.897305 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:20.013580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:50.013533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:13.915371 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:13.915433 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:20.013552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:50.013702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:13.932480 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:13.932511 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:20.013503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:50.013482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:13.949698 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:13.949756 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:20.013561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:50.013567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:13.967178 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:13.967221 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:20.013656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:50.013627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:13.984269 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:13.984307 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:20.013623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:50.013574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:14.000625 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:14.000662 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:20.013633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:50.013595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:14.016442 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:14.016475 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:20.013541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:50.013566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:14.033988 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:14.034022 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:20.013657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:50.013531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:14.051147 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:14.051310 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:20.013543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:50.016556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:14.068992 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:14.069030 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:20.014257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:50.013643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:14.085551 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:14.085674 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:20.013585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:50.013557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:14.101724 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:14.101767 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:20.013526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:50.013658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:14.119562 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:14.119601 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:20.013574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:50.013494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:14.138336 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:14.138366 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:20.013580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:50.013559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:14.154864 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:14.154920 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:20.013625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:50.013581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:14.172102 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:14.172138 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:20.013577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:50.013508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:14.189569 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:14.189603 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:20.013571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:50.013577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:14.207433 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:14.207471 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:20.013631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:50.013526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:14.226629 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:14.226744 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:20.013556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:50.013718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:14.246220 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:14.246260 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:20.013552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:50.014115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:14.269972 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:14.270106 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:20.013512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:50.013709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:14.296151 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:14.296189 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:20.013577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:50.013610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:14.314488 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:14.314534 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:20.013508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:50.013580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:14.331764 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:14.331796 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:20.013561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:50.013923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:14.349160 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:14.349203 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:20.013677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:50.013636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:14.368704 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:14.368739 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:20.013609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:50.013554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:14.386278 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:14.386315 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:20.013519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:50.014506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:14.405842 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:14.405877 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:20.013543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:50.013586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:14.423034 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:14.423084 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:20.013528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:50.013517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:14.444271 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:14.444298 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:20.013503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:50.013638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:14.462882 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:14.462918 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:20.013577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:50.013681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:14.480065 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:14.480111 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:20.013577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:50.013549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:14.501312 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:14.501346 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:20.013687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:50.013601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:14.517766 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:14.517798 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:20.013539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:50.013495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:14.535838 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:14.535876 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:20.013771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:50.013629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:14.552671 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:14.552710 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:20.013584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:50.013535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:14.569416 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:14.569450 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:20.013579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:50.013502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:14.587655 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:14.587698 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:20.013469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:50.013598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:14.603032 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:14.603066 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:20.014435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:50.013582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:14.621221 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:14.621286 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:20.013569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:50.013570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:14.638810 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:14.638859 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:20.013620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:50.013563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:14.660138 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:14.660174 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:20.013618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:50.013570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:14.678425 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:14.678469 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:20.013602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:50.013684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:14.696110 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:14.696144 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:20.013601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:50.013612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:14.712867 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:14.712914 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:20.013749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:50.013884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:14.729693 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:14.729737 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:20.013634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:50.013522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:14.747086 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:14.747137 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:20.013759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:50.013615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:14.764768 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:14.764820 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:20.013592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:50.013629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:14.780744 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:14.780797 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:20.013593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:50.013549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:14.799005 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:14.799053 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:20.013557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:50.013731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:14.817584 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:14.817627 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:20.013607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:50.013591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:14.834933 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:14.834966 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:20.013827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:50.013543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:14.853144 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:14.853179 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:20.013560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:50.013586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:14.870762 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:14.870799 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:20.013616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:50.013510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:14.888080 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:14.888121 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:20.013630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:50.013714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:14.904693 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:14.904735 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:20.013664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:50.013576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:14.922052 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:14.922100 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:20.013610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:50.013621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:14.941368 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:14.941395 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:20.013571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:50.013588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:14.958831 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:14.958874 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:20.013558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:50.013565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:14.975453 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:14.975609 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:20.013609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:50.013537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:14.993075 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:14.993119 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:20.013548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:50.013604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:15.010766 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:15.010829 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:20.013595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:50.013614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:15.027620 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:15.027735 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:20.013527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:50.013589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:15.045657 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:15.045694 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:20.013555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:50.013608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:15.063405 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:15.063442 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:20.013623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:50.013570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:15.079512 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:15.079547 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:20.013584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:50.013765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:15.095699 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:15.095746 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:20.013555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:50.014249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:15.113178 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:15.113217 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:20.013666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:50.013638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:15.131573 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:15.131606 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:20.013522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:50.013639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:15.147966 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:15.148004 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:20.013490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:50.013554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:15.163927 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:15.163967 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:20.013626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:50.013547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:15.181211 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:15.181377 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:20.013527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:50.013645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:15.199019 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:15.199209 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:20.013648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:50.013530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:15.217221 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:15.217257 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:20.013579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:50.013467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:15.240179 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:15.240228 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:20.013780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:50.013549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:15.257181 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:15.257248 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:20.013622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:50.013579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:15.276902 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:15.276947 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:20.013516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:50.013968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:15.295630 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:15.295676 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:20.013582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:50.013606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:15.313949 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:15.313985 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:20.013619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:50.013687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:15.334274 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:15.334307 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:20.013656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:50.013561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:15.351091 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:15.351129 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:20.013544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:50.013583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:15.368629 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:15.368662 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:20.013499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:50.013537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:15.416694 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:15.416733 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:20.013760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:50.013512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:15.435816 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:15.435849 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:20.013557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:50.014613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:15.452807 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:15.452856 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:20.013660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:50.013713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:15.471560 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:15.471595 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:20.014373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:50.013592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:15.488206 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:15.488359 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:20.013524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:50.016767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:15.507424 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:15.507464 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:20.013523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:50.013832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:15.527593 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:15.527632 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:20.013667 metrics.go:34: INFO No non-zero metrics in the last 30s