By type
2022/04/02 03:26:38.444114 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:38.444190 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:26:38.444389 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:26:38.444600 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:26:38.444765 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-vdkq2
2022/04/02 03:26:38.445169 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:26:38.445197 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:26:38.445858 beat.go:221: INFO filebeat start running.
2022/04/02 03:26:38.445933 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:26:38.447428 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:26:38.455268 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:26:38.455454 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:26:38.455580 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:26:38.455938 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:26:38.456089 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:26:38.456116 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/02 03:26:38.456152 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:26:38.455762 sync.go:41: INFO Start sending events to output
2022/04/02 03:26:38.456645 registrar.go:236: INFO Starting Registrar
2022/04/02 03:26:38.457827 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/04/02 03:27:08.447921 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:38.447862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:08.447868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:38.447852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:08.447852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:38.447709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:08.447736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:38.447740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:08.447748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:38.447716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:43.475386 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:32:08.447783 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:38.447912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:08.447705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:38.452714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:08.447721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:38.447870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:08.447922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:38.447756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:08.447735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:38.447822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:08.448347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:38.447685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:08.447726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:38.447729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:08.447696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:38.447764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:08.449398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:38.447782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:08.447802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:38.447797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:08.447742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:38.447743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:08.447749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:38.447831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:08.447763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:38.448036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:08.447769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:38.447720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:08.447753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:38.447722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:08.448394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:38.447814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:08.447710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:38.447831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:08.447735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:38.447689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:08.447743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:38.447842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:08.447775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:38.447761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:08.447828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:38.447797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:08.447786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:38.447762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:08.447748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:08.603745 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/04/02 03:54:13.615544 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.615592 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:14.619033 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:14.619073 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:16.623351 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:16.623400 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.626799 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:20.626852 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:28.633395 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:28.633451 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:38.447762 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:44.654379 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:44.654818 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:08.447944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:16.674634 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:16.674779 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:38.447801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:08.447673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:16.694590 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:16.694627 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:38.447744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:08.447785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:16.714156 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:16.714208 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:38.447737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:08.447718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:16.733605 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:16.733649 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:38.447717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:08.447723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:13.614882 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:59:16.752746 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:16.752826 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:38.447786 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:08.447735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:16.770916 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:16.770981 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:38.447694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:08.447738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:16.790256 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:16.790292 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:38.447754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:08.447708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:16.810640 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:16.810782 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:38.447724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:08.447825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:16.829943 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:16.829992 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:38.447688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:08.447703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:16.848108 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:16.848161 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:38.447770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:08.447943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:16.867717 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:16.867776 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:38.447736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:08.447771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:16.888993 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:16.889054 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:38.447738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:08.447886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:16.908997 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:16.909054 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:38.449109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:08.447781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:16.929316 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:16.929371 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:38.447754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:08.447772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:16.951771 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:16.951818 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:38.447735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:08.447761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:16.969227 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:16.969273 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:38.447787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:08.447773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:16.989108 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:16.989169 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:38.447769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:08.447680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:17.006183 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:17.006219 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:38.447753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:08.447741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:17.025954 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:17.026004 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:38.447817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:08.447743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:17.046227 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:17.046269 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:38.447942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:08.447899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:17.064733 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:17.064967 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:38.447738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:08.447709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:17.085335 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:17.085383 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:38.447765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:08.447789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:17.118334 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:17.118509 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:38.448005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:08.447700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:17.137494 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:17.137539 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:38.447747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:08.447790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:17.155687 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:17.155735 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:38.449548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:08.447772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:17.172745 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:17.172792 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:38.448960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:08.447768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:17.191423 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:17.191467 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:38.447780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:08.447721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:17.209364 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:17.209402 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:38.447827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:08.447720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:17.229113 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:17.229152 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:38.447766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:08.447823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:17.247353 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:17.247449 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:38.447793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:08.447851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:17.266671 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:17.266710 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:38.447814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:08.447761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:17.290975 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:17.291076 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:38.447732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:08.447754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:17.312731 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:17.312788 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:38.447734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:08.447727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:17.331037 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:17.331091 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:38.447835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:08.447749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:17.350314 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:17.350471 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:38.447764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:08.447869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:17.374331 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:17.374383 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:38.447746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:08.447752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:17.393177 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:17.393251 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:38.447908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:08.447662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:17.411180 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:17.411229 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:38.447798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:08.447754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:17.430273 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:17.430305 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:38.447739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:08.447893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:17.454464 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:17.454510 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:38.448247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:08.447770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:17.475392 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:17.475461 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:38.447670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:08.447742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:17.495284 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:17.495330 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:38.447865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:08.447828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:17.514544 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:17.514580 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:38.447708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:08.447715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:17.534640 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:17.534693 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:38.447726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:08.447724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:17.554917 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:17.554955 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:38.447691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:08.447684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:17.573224 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:17.573262 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:38.447796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:08.447693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:17.592734 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:17.592781 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:38.447783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:08.447700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:17.610590 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:17.610631 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:38.447746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:08.447789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:17.628669 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:17.628708 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:38.447721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:08.447777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:17.647479 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:17.647537 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:38.447797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:08.447957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:17.666172 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:17.666222 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:38.447853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:08.447770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:17.686145 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:17.686214 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:38.447747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:08.447717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:17.705085 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:17.705133 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:38.448005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:08.447711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:17.727339 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:17.727444 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:38.447787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:08.447743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:17.747350 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:17.747401 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:38.447702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:08.447707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:17.763788 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:17.763847 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:38.447777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:08.447768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:17.782816 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:17.782870 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:38.447752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:08.447757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:17.802973 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:17.803019 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:38.447767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:08.447756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:17.825879 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:17.825919 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:38.447754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:08.447776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:17.846701 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:17.846745 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:38.447755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:08.447810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:17.864659 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:17.864713 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:38.448535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:08.447875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:17.883038 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:17.883092 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:38.447831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:08.447793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:17.905055 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:17.905100 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:38.447733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:08.447842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:17.923317 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:17.923564 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:38.447815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:08.447810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:17.941737 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:17.941775 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:38.447691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:08.447746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:17.962468 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:17.962565 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:38.447712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:08.447696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:17.985085 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:17.985124 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:38.447707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:08.447716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:18.003284 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:18.003326 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:38.447771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:08.447711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:18.022852 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:18.022934 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:38.447783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:08.457104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:18.043712 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:18.043755 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:38.447720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:08.447727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:18.062311 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:18.062462 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:38.447782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:08.447870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:18.081576 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:18.081631 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:38.447845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:08.447827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:18.102412 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:18.102443 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:38.447721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:08.447778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:18.121086 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:18.121135 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:38.447832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:08.447725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:18.144415 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:18.144451 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:38.447693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:08.447718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:18.166106 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:18.166153 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:38.447717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:08.447893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:18.184912 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:18.184955 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:38.447768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:08.447801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:18.204045 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:18.204082 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:38.447767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:08.447735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:18.223320 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:18.223366 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:38.447769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:08.447681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:18.242685 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:18.242739 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:38.447729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:08.447705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:18.260240 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:18.260277 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:38.447887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:08.447734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:18.277458 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:18.277614 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:38.447778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:08.447747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:18.295369 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:18.295410 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:38.447767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:08.447899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:18.322016 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:18.322078 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:38.447770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:08.447699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:18.341194 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:18.341233 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:38.447772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:08.447753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:18.360700 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:18.360750 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:38.447823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:08.447696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:18.380938 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:18.380977 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:38.448846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:08.447791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:18.398616 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:18.398674 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:38.447835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:08.447744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:18.416971 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:18.417016 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:38.448096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:08.447803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:18.435076 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:18.435113 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:38.447937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:08.447723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:18.455138 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:18.455180 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:38.447705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:08.447704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:18.475231 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:18.475281 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:38.447707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:08.447738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:18.493983 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:18.494026 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:38.447688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:08.447805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:18.513197 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:18.513243 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:38.447690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:08.447808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:18.536320 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:18.536368 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:38.447872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:08.447895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:18.553998 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:18.554045 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:38.447829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:08.447764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:18.570384 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:18.570424 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:38.447807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:08.448454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:18.588944 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:18.588994 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:38.447829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:08.447816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:18.605908 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:18.605947 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:38.447792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:08.447701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:18.625198 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:18.625257 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:38.447741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:08.447696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:18.644064 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:18.644204 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:38.447790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:08.447675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:18.664581 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:18.664665 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:38.447958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:08.447837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:18.682177 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:18.682210 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:38.447799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:08.447682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:18.700591 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:18.700630 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:38.447766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:08.447733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:18.722042 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:18.722190 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:38.447811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:08.447834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:18.739859 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:18.739897 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:38.447710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:08.447897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:18.760344 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:18.760382 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:38.447743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:08.447767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:18.778716 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:18.778760 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:38.447819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:08.447829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:18.799401 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:18.799448 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:38.448955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:08.447788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:18.817862 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:18.817899 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:38.448336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:08.447803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:18.836164 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:18.836292 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:38.447879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:08.447778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:18.854271 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:18.854428 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:38.447755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:08.447826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:18.871298 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:18.871352 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:38.447749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:08.447839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:18.890782 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:18.890884 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:38.447771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:08.447738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:18.913293 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:18.913832 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:38.447695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:08.447772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:18.935223 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:18.935257 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:38.447735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:08.447703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:18.957348 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:18.957395 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:38.447763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:08.447833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:18.975606 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:18.975640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host