Results

          2022/01/22 03:23:31.444330 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/01/22 03:23:31.444392 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/22 03:23:31.444478 metrics.go:23: INFO Metrics logging every 30s
2022/01/22 03:23:31.444550 logstash.go:90: INFO Max Retries set to: 3
2022/01/22 03:23:31.444644 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/22 03:23:31.444756 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-fm6kr
2022/01/22 03:23:31.444948 async.go:63: INFO Flush Interval set to: 1s
2022/01/22 03:23:31.444967 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/22 03:23:31.445449 beat.go:221: INFO filebeat start running.
2022/01/22 03:23:31.445505 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/22 03:23:31.500155 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/22 03:23:31.500250 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/22 03:23:31.500339 crawler.go:38: INFO Loading Prospectors: 1
2022/01/22 03:23:31.504618 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/22 03:23:31.504658 registrar.go:236: INFO Starting Registrar
2022/01/22 03:23:31.504705 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/22 03:23:31.504720 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/22 03:23:31.504768 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/22 03:23:31.504790 sync.go:41: INFO Start sending events to output
2022/01/22 03:23:41.507821 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/22 03:23:41.507960 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/22 03:23:41.508352 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/22 03:23:41.508375 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/22 03:23:41.508469 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/22 03:23:46.511428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:23:46.511477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:23:47.514678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:23:47.514721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:23:49.523274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:23:49.523309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:23:53.526573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:23:53.526616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:24:01.445025 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=61 registrar.writes=1
2022/01/22 03:24:01.530439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:24:01.530473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:24:17.535027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:24:17.535066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:24:31.444902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:24:49.543922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:24:49.543967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:25:01.444981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:25:31.445026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:25:49.554470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:25:49.554535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:26:01.444864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:26:31.444858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:26:49.564759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:26:49.564822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:27:01.444749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:27:31.444876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:27:49.574852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:27:49.574894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:28:01.444849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:28:31.444950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:28:46.519126 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/22 03:28:49.584965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:28:49.585012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:29:01.444771 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/22 03:29:31.444820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:29:49.588684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:29:49.588740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:30:01.444773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:30:31.444902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:30:49.593785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:30:49.593830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:31:01.445101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:31:31.444804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:31:49.597340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:31:49.597388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:32:01.444920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:32:31.444961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:32:49.601814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:32:49.601862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:33:01.444847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:33:31.445144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:33:49.606629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:33:49.606677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:34:01.444919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:34:31.444949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:34:49.610761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:34:49.610826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:35:01.444982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:35:31.444910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:35:49.614958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:35:49.615016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:36:01.445389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:36:31.445000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:36:49.617739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:36:49.617773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:37:01.444931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:37:31.444874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:37:49.620924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:37:49.620979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:38:01.444858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:38:31.444956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:38:49.625781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:38:49.625828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:39:01.444946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:39:31.444809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:39:49.629676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:39:49.629740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:40:01.444964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:40:31.444969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:40:49.633627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:40:49.633671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:41:01.445159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:41:31.445123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:41:49.637963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:41:49.638007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:42:01.444976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:42:31.444982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:42:49.642172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:42:49.642236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:43:01.444888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:43:31.444864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:43:49.646480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:43:49.646526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:44:01.444942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:44:31.444790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:44:49.649857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:44:49.649907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:45:01.444872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:45:31.445064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:45:49.654524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:45:49.654597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:46:01.444865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:46:31.444985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:46:49.658429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:46:49.658526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:47:01.444891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:47:31.444875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:47:49.662462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:47:49.662519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:48:01.444841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:48:31.444825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:48:49.666674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:48:49.666718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:01.444852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:49:31.444896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:49:49.670545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:49.670593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:50:01.444795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:50:31.445226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:50:49.675459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:50:49.675518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:51:01.444786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:51:31.444865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:51:49.681549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:51:49.681678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:52:01.444818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:52:31.444850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:52:49.686953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:52:49.686982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:53:01.444867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:53:31.444822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:53:49.692901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:53:49.692929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:54:01.444805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:54:31.444882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:54:49.698371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:54:49.698407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:55:01.444796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:55:31.444784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:55:49.702816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:55:49.702863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:56:01.444933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:56:31.444982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:56:49.707865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:56:49.707910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:57:01.444849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:57:31.444874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:57:49.714274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:57:49.714303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:58:01.444870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:58:31.444980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:58:49.720126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:58:49.720166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:59:01.444844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:59:31.444868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:59:49.725114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:59:49.725149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:00:01.444902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:00:31.444914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:00:49.730317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:00:49.730394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:01:01.444882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:01:31.445118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:01:49.736045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:01:49.736103 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:02:01.444933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:02:31.444957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:02:49.741550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:02:49.741616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:03:01.444860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:03:31.444687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:03:49.747370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:03:49.747422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:04:01.444735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:04:31.444831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:04:49.752979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:04:49.753014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:05:01.444964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:05:31.444816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:05:49.758883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:05:49.758922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:06:01.444781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:06:31.444951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:06:49.764495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:06:49.764608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:07:01.444864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:07:31.444850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:07:49.769721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:07:49.769765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:08:01.445020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:08:31.444952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:08:49.775617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:08:49.775667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:09:01.444799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:09:31.444958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:09:49.780881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:09:49.780991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:10:01.444927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:10:31.444852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:10:49.786362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:10:49.786428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:11:01.444812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:11:31.445001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:11:49.792090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:11:49.792137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:12:01.444941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:12:31.444933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:12:49.797933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:12:49.797970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:13:01.444872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:13:31.444761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:13:49.803337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:13:49.803390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:14:01.444927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:14:31.444974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:14:49.809002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:14:49.809061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:15:01.444899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:15:31.444987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:15:49.813368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:15:49.813396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:16:01.444815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:16:31.445009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:16:49.819251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:16:49.819293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:17:01.444870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:17:31.444724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:17:49.824839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:17:49.824880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:18:01.444842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:18:31.444984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:18:49.830337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:18:49.830382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:19:01.445016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:19:31.445079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:19:49.835546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:19:49.835592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:20:01.444994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:20:31.444856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:20:49.841171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:20:49.841232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:21:01.444889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:21:31.444920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:21:49.846110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:21:49.846156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:22:01.444900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:22:31.444728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:22:49.851058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:22:49.851093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:23:01.444930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:23:31.444849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:23:49.855624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:23:49.855659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:24:01.444966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:24:31.444935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:24:49.861268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:24:49.861307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:25:01.444921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:25:31.444819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:25:49.866108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:25:49.866175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:26:01.444988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:26:31.444965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:26:49.870374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:26:49.870424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:27:01.444876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:27:31.444871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:27:49.874978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:27:49.875002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:28:01.445048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:28:31.444912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:28:49.879395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:28:49.879432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:29:01.444863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:29:31.444869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:29:49.884617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:29:49.884696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:30:01.444840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:30:31.444950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:30:49.889860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:30:49.890006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:31:01.444940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:31:31.444942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:31:49.894784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:31:49.894826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:32:01.444912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:32:31.445024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:32:49.900568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:32:49.900600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:33:01.444941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:33:31.444856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:33:49.906882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:33:49.906931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:34:01.444906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:34:31.444901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:34:49.916589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:34:49.916650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:35:01.444877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:35:31.444964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:35:49.922059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:35:49.922113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:36:01.444964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:36:31.445041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:36:49.927349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:36:49.927389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:37:01.445035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:37:31.444934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:37:49.933208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:37:49.933274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:38:01.444991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:38:31.444928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:38:49.938188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:38:49.938224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:39:01.444903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:39:31.444895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:39:49.943246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:39:49.943285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:40:01.444874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:40:31.445023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:40:49.949125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:40:49.949166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:41:01.444839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:41:31.444999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:41:49.954929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:41:49.954995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:42:01.444989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:42:31.444854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:42:49.961308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:42:49.961358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:43:01.444981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:43:31.444882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:43:49.966227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:43:49.966374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:44:01.444961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:44:31.445034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:44:49.971639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:44:49.971670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:45:01.444890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:45:31.444834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:45:49.977322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:45:49.977357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:46:01.444795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:46:31.445013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:46:49.981594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:46:49.981627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:47:01.444968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:47:31.444917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:47:49.987590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:47:49.987632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:48:01.444935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:48:31.444950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:48:49.992333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:48:49.992400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:49:01.444898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:49:31.444940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:49:49.998301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:49:49.998343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:50:01.445052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:50:31.444917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:50:50.002839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:50:50.002885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:51:01.444795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:51:31.444746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:51:50.008167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:51:50.008216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:52:01.444902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:52:31.444925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:52:50.013102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:52:50.013136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:53:01.444780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:53:31.445001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:53:50.022549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:53:50.022597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:54:01.444892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:54:31.444951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:54:50.031991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:54:50.032031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:55:01.444965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:55:31.444966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:55:50.041380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:55:50.041624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:56:01.444830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:56:31.445042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:56:50.050949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:56:50.050994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:57:01.444920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:57:31.444907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:57:50.060098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:57:50.060147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:58:01.444873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:58:31.444920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:58:50.069292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:58:50.069345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:59:01.444908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:59:31.444913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:59:50.080645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:59:50.080838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:00:01.444959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:00:31.444951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:00:50.090744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:00:50.090827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:01:01.444888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:01:31.444843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:01:50.100170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:01:50.100223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:02:01.445001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:02:31.444931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:02:50.109728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:02:50.109773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:03:01.444936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:03:31.444879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:03:50.119475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:03:50.119533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:04:01.444997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:04:31.444906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:04:50.130238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:04:50.130419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:05:01.444822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:05:31.444909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:05:50.139412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:05:50.139449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:06:01.444934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:06:31.444919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:06:50.150019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:06:50.150071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:07:01.444949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:07:31.444825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:07:50.159106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:07:50.159169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:08:01.444895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:08:31.444893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:08:50.167885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:08:50.167930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:09:01.444762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:09:31.444663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:09:50.177726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:09:50.177771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:10:01.444885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:10:31.444730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:10:50.187916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:10:50.187957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:11:01.444877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:11:31.444839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:11:50.199083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:11:50.199145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:12:01.445029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:12:31.444881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:12:50.208315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:12:50.208378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:13:01.445154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:13:31.445038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:13:50.216709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:13:50.216748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:14:01.445047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:14:31.445035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:14:50.226175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:14:50.226221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:15:01.444922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:15:31.444929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:15:50.237334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:15:50.237417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:16:01.444834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:16:31.444909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:16:50.246825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:16:50.246886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:17:01.445044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:17:31.444937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:17:50.257525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:17:50.257705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:18:01.444849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:18:31.445060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:18:50.271051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:18:50.271090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:19:01.445003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:19:31.444888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:19:50.281250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:19:50.281301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:20:01.444958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:20:31.445013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:20:50.291044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:20:50.291084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:21:01.444958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:21:31.444762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:21:50.301579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:21:50.301634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:22:01.444906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:22:31.444961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:22:50.311006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:22:50.311064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:23:01.444742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:23:31.444747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:23:50.319432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:23:50.319467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:24:01.444942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:24:31.444741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:24:50.329998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:24:50.330031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:25:01.444906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:25:31.444938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:25:50.338480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:25:50.338522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:26:01.444898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:26:31.444912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:26:50.347524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:26:50.347565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:27:01.444982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:27:31.444935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:27:50.356948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:27:50.356995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:28:01.444938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:28:31.444962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:28:50.366224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:28:50.366277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:29:01.444856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:29:31.444928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:29:50.376726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:29:50.376771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:30:01.444868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:30:31.444910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:30:50.387537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:30:50.387582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:31:01.444778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:31:31.444886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:31:50.398481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:31:50.398550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:32:01.444992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:32:31.445024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:32:50.408124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:32:50.408170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:33:01.444931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:33:31.444881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:33:50.418718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:33:50.418765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:34:01.444960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:34:31.444937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:34:50.426119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:34:50.426163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:35:01.444984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:35:31.444907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:35:50.435358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:35:50.435381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:36:01.444892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:36:31.444877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:36:50.445403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:36:50.445435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:37:01.444895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:37:31.444782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:37:50.456046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:37:50.456076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:38:01.444951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:38:31.445077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:38:50.465717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:38:50.465771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:39:01.444930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:39:31.444757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:39:50.475711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:39:50.475760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:40:01.444862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:40:31.444825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:40:50.486426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:40:50.486473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:41:01.444893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:41:31.444913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:41:50.497378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:41:50.497443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:42:01.444978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:42:31.444985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:42:50.507420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:42:50.507475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:43:01.445023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:43:31.444959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:43:50.515625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:43:50.515671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:44:01.444824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:44:31.444831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:44:50.525449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:44:50.525517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:45:01.445003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:45:31.444980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:45:50.535464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:45:50.535505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:46:01.444745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:46:31.444850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:46:50.545679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:46:50.545751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:47:01.444855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:47:31.444933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:47:50.555741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:47:50.555779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:48:01.444864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:48:31.444843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:48:50.566277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:48:50.566316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:49:01.444846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:49:31.444897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:49:50.575318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:49:50.575371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:50:01.444937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:50:31.444792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:50:50.583285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:50:50.583340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:51:01.444958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:51:31.444895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:51:50.591351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:51:50.591393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:52:01.444810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:52:31.444810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:52:50.600093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:52:50.600138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:53:01.444756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:53:31.444800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:53:50.608476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:53:50.608513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:54:01.444936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:54:31.444855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:54:50.617626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:54:50.617692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:55:01.444937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:55:31.444908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:55:50.657116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:55:50.657209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:56:01.444739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:56:31.444993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:56:50.665222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:56:50.665255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:57:01.444802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:57:31.445304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:57:50.674256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:57:50.674309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:58:01.444944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:58:31.444766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:58:50.682153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:58:50.682179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:59:01.444878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:59:31.444958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:59:50.690869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:59:50.690903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:00:01.444884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:00:31.445397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:00:50.700454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:00:50.700488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:01:01.444759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:01:31.444852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:01:50.710839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:01:50.710891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:02:01.444734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:02:31.444800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:02:50.721369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:02:50.721419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:03:01.444853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:03:31.444883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:03:50.729798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:03:50.729828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:04:01.444784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:04:31.445021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:04:50.740005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:04:50.740067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:05:01.444895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:05:31.444995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:05:50.747313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:05:50.747365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:06:01.444910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:06:31.444947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:06:50.756355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:06:50.756398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:07:01.444959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:07:31.444807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:07:50.766025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:07:50.766181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:08:01.444857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:08:31.444841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:08:50.778114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:08:50.778148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:09:01.444930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:09:31.444857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:09:50.787282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:09:50.787320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:10:01.444970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:10:31.444967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:10:50.796736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:10:50.796777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:11:01.444963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:11:31.444930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:11:50.806207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:11:50.806270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:12:01.444884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:12:31.444873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:12:50.815802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:12:50.815888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:13:01.444960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:13:31.444849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:13:50.830855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:13:50.830907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:14:01.444869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:14:31.445032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:14:50.841770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:14:50.841832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:15:01.444914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:15:31.444853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:15:50.851407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:15:50.851607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:16:01.444952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:16:31.444908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:16:50.861232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:16:50.861274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:17:01.444894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:17:31.444788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:17:50.871064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:17:50.871108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:18:01.444872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:18:31.444853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:18:50.881369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:18:50.881412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:19:01.444962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:19:31.444864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:19:50.923386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:19:50.923423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:20:01.444851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:20:31.444832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:20:50.932908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:20:50.932949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:21:01.444899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:21:31.444744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:21:50.941378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:21:50.941407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:22:01.444843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:22:31.444751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:22:50.951000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:22:50.951119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:23:01.444807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:23:31.444872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:23:50.961219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:23:50.961412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:24:01.444897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:24:31.444947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:24:50.971735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:24:50.971793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:25:01.444846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:25:31.444861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:25:50.981569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:25:50.981624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:26:01.444869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:26:31.444957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:26:50.990623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:26:50.990680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:27:01.444851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:27:31.445045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:27:51.000473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:27:51.000519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:28:01.444802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:28:31.444804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:28:51.009606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:28:51.009655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:29:01.445038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:29:31.444944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:29:51.019625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:29:51.019670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:30:01.444780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:30:31.444858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:30:51.029279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:30:51.029332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:31:01.444940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:31:31.444901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:31:51.039562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:31:51.039611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:32:01.444771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:32:31.444884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:32:51.049261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:32:51.049327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:33:01.445180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:33:31.444829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:33:51.059583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:33:51.059613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:34:01.444846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:34:31.445100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:34:51.068592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:34:51.068654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:35:01.444859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:35:31.444894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:35:51.078801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:35:51.078840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:36:01.444876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:36:31.444912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:36:51.087873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:36:51.087936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:37:01.444926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:37:31.444800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:37:51.097273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:37:51.097318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:38:01.444892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:38:31.445004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:38:51.107692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:38:51.107729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:39:01.444937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:39:31.445002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:39:51.116897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:39:51.117061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:40:01.444879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:40:31.445029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:40:51.126132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:40:51.126167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:41:01.445333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:41:31.444814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:41:51.135256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:41:51.135349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:42:01.444889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:42:31.444876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:42:51.143913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:42:51.143964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:43:01.444961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:43:31.444815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:43:51.151870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:43:51.151927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:44:01.444926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:44:31.444913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:44:51.162269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:44:51.162316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:45:01.444861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:45:31.444932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:45:51.176713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:45:51.176772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:46:01.444850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:46:31.444912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:46:51.185767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:46:51.185796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:47:01.444896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:47:31.444847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:47:51.195216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:47:51.195277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:48:01.444871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:48:31.444957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:48:51.204373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:48:51.204434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:49:01.444879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:49:31.444830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:49:51.212879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:49:51.212921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:50:01.444934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:50:31.444828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:50:51.224154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:50:51.224301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:51:01.444825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:51:31.444798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:51:51.234824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:51:51.234869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:52:01.444989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:52:31.444860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:52:51.243780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:52:51.243831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:53:01.444902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:53:31.444847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:53:51.254074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:53:51.254118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:54:01.444892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:54:31.444989 metrics.go:34: INFO No non-zero metrics in the last 30s