By type
2022/04/22 03:22:14.890221 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/04/22 03:22:14.890309 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/22 03:22:14.890438 logstash.go:90: INFO Max Retries set to: 3
2022/04/22 03:22:14.890572 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/22 03:22:14.890705 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-hkj5c
2022/04/22 03:22:14.890924 async.go:63: INFO Flush Interval set to: 1s
2022/04/22 03:22:14.890948 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/22 03:22:14.891782 metrics.go:23: INFO Metrics logging every 30s
2022/04/22 03:22:14.891965 beat.go:221: INFO filebeat start running.
2022/04/22 03:22:14.892036 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/22 03:22:14.900152 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/22 03:22:14.900219 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/22 03:22:14.900253 crawler.go:38: INFO Loading Prospectors: 1
2022/04/22 03:22:14.900433 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/22 03:22:14.900525 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/22 03:22:14.900539 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/22 03:22:14.900549 registrar.go:236: INFO Starting Registrar
2022/04/22 03:22:14.900598 sync.go:41: INFO Start sending events to output
2022/04/22 03:22:14.900629 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/22 03:22:24.902645 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/22 03:22:24.902771 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/22 03:22:24.903053 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/22 03:22:24.903291 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/22 03:22:24.903390 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/22 03:22:29.938258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:29.938303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:30.945010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:30.945047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:32.956052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:32.958099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:36.968435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:36.968505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:44.892380 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=59 registrar.writes=1
2022/04/22 03:22:44.979983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:44.980118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:00.997256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:00.997337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:23:33.018504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:33.018546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:44.892524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:24:14.892204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:24:33.038872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:24:33.038916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:24:44.892359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:25:14.892526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:25:33.060099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:25:33.060145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:25:44.892629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:26:14.892640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:26:33.086331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:26:33.086405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:26:44.892464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:27:14.892511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:27:29.919683 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:27:33.106254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:27:33.106463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:27:36.918195 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:27:36.918195 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:27:36.918194 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:27:44.892618 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/04/22 03:27:47.934042 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:28:14.892474 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/04/22 03:28:33.124688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:28:33.124750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:28:44.892083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:29:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:29:33.152541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:29:33.152593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:29:44.892063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:30:14.892296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:30:33.172886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:30:33.172940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:30:44.892125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:31:14.892002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:31:33.191738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:31:33.191783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:31:44.892042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:32:14.892081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:32:33.212261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:32:33.212421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:32:44.892186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:33:14.892076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:33:33.230961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:33:33.231133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:33:44.892133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:34:14.892136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:34:33.251520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:34:33.251559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:34:44.892427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:35:14.892124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:35:33.271999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:35:33.272066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:35:44.892205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:36:14.892098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:36:33.292074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:36:33.292111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:36:44.892067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:37:14.892179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:37:33.321640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:37:33.321687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:37:44.892046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:38:14.892041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:38:33.341915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:38:33.341955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:38:44.892141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:39:14.892102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:39:33.373590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:39:33.373629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:39:44.892274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:40:14.892123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:40:33.390707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:40:33.390750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:40:44.893196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:41:14.892193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:41:33.408891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:41:33.408929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:41:44.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:42:14.892264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:42:33.426758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:42:33.426796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:42:44.892045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:43:14.892108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:43:33.443841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:43:33.443883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:43:44.892115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:44:14.892141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:44:33.462450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:44:33.462490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:44:44.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:45:14.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:45:33.479172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:45:33.479222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:45:44.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:46:14.892160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:46:33.502047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:46:33.502092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:46:44.892108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:47:14.892589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:47:33.524817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:47:33.524870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:47:44.892158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:48:14.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:48:33.541769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:48:33.541818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:48:44.892165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:49:14.892095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:49:33.560435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:49:33.560599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:49:44.892307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:50:14.892150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:50:33.576407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:50:33.576450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:50:44.892118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:51:14.892104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:51:33.595146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:51:33.595208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:51:44.892191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:52:14.892220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:52:33.611224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:52:33.611262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:52:44.892155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:53:14.892122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:53:33.629315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:53:33.629362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:53:44.892061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:54:14.892189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:54:33.648150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:54:33.648206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:54:44.892059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:55:14.892143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:55:33.675971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:55:33.676040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:55:44.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:56:14.892457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:56:33.693670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:56:33.693709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:56:44.892057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:57:14.892082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:57:33.711950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:57:33.712003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:57:44.892091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:58:14.892121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:58:33.732653 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:58:33.732702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:58:44.892078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:59:14.892152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:59:33.752449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:59:33.752487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:59:44.892065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:00:14.892125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:00:33.770988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:00:33.771041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:00:44.892144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:01:14.892213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:01:33.788669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:01:33.788725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:01:44.892048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:02:14.892099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:02:33.806692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:02:33.806748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:02:44.892156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:03:14.892091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:03:33.833542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:03:33.833594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:03:44.892290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:04:14.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:04:33.856154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:04:33.856208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:04:44.892168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:05:14.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:05:33.874767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:05:33.874812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:05:44.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:06:14.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:06:33.897215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:06:33.897264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:06:44.892055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:07:14.892079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:07:33.918958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:07:33.919007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:07:44.892038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:08:14.892338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:08:33.935239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:08:33.935276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:08:44.892021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:09:14.892117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:09:33.960346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:09:33.960392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:09:44.892097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:10:14.892112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:10:33.980990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:10:33.981143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:10:44.892181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:11:14.892118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:11:33.998260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:11:33.998303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:11:44.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:12:14.892134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:12:34.016816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:12:34.016871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:12:44.892124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:13:14.892066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:13:36.035164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:13:36.035232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:13:44.892142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:14:14.892211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:14:36.063745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:14:36.063809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:14:44.892104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:15:14.892089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:15:36.080181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:15:36.080234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:15:44.892069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:16:14.892186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:16:36.098836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:16:36.098893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:16:44.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:17:14.892166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:17:36.116755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:17:36.116798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:17:44.892096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:18:14.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:18:36.137226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:18:36.137263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:18:44.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:19:14.892096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:19:36.155594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:19:36.155636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:19:44.892199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:20:14.892071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:20:36.174330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:20:36.174378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:20:44.892065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:21:14.892045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:21:36.192704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:21:36.192738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:21:44.892151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:22:14.892092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:22:36.211857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:22:36.211898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:22:44.892089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:23:14.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:23:36.229784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:23:36.229962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:23:44.892137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:24:14.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:24:36.249758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:24:36.249798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:24:44.892074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:25:14.892294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:25:36.270124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:25:36.270163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:25:44.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:26:14.892178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:26:36.289625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:26:36.289663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:26:44.892095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:27:14.892085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:27:36.306647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:27:36.306681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:27:44.892050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:28:14.892265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:28:36.323394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:28:36.323591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:28:44.892033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:29:14.892061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:29:36.342854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:29:36.342899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:29:44.892173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:30:14.892109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:30:36.360714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:30:36.360769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:30:44.892061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:31:14.892096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:31:36.378580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:31:36.378615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:31:44.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:32:14.892146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:32:36.395309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:32:36.395345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:32:44.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:33:14.892129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:33:36.415670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:33:36.415709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:33:44.892059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:34:14.892296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:34:36.434304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:34:36.434338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:34:44.892121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:35:14.892131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:35:36.455097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:35:36.455138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:35:44.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:36:14.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:36:36.480859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:36:36.480900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:36:44.892115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:37:14.892235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:37:36.501391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:37:36.501464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:37:44.892241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:38:14.892067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:38:36.519201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:38:36.519247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:38:44.892109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:39:14.892100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:39:36.537037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:39:36.537083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:39:44.892043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:40:14.892124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:40:36.554240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:40:36.554287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:40:44.892048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:41:14.892053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:41:36.575240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:41:36.575296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:41:44.892226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:42:14.892173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:42:36.594273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:42:36.594311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:42:44.892213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:43:14.892108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:43:36.614727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:43:36.614764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:43:44.892085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:44:14.892051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:44:36.634104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:44:36.634144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:44:44.892076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:45:14.892167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:45:36.652791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:45:36.652833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:45:44.892078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:46:14.892098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:46:36.670355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:46:36.670488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:46:44.892088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:47:14.892098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:47:36.689827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:47:36.689867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:47:44.892116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:48:14.892090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:48:36.707356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:48:36.707406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:48:44.892058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:49:14.892100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:49:36.725607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:49:36.725649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:49:44.892102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:50:14.892083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:50:36.743308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:50:36.743350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:50:44.892217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:51:14.892112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:51:36.773228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:51:36.773306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:51:44.892126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:52:14.892098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:52:36.790709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:52:36.790753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:52:44.892158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:53:14.892153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:53:36.810957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:53:36.810997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:53:44.892106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:54:14.892135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:54:36.838670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:54:36.838727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:54:44.892120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:55:14.892258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:55:36.880729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:55:36.880768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:55:44.892011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:56:14.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:56:36.899019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:56:36.899057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:56:44.892043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:57:14.892063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:57:36.916855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:57:36.916897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:57:44.892193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:58:14.892110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:58:36.961699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:58:36.961736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:58:44.892130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:59:14.892154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:59:36.978561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:59:36.978605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:59:44.892188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:00:14.892120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:00:36.985627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:00:36.985672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:00:44.892092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:01:14.892145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:01:37.007315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:01:37.007351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:01:44.892145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:02:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:02:37.023536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:02:37.023572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:02:44.892092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:03:14.892133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:03:37.043963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:03:37.044139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:03:44.892055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:04:14.892059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:04:37.060847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:04:37.060902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:04:44.892081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:05:14.892058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:05:37.077418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:05:37.077451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:05:44.892046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:06:14.892104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:06:37.097238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:06:37.097330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:06:44.892246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:07:14.892103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:07:37.123367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:07:37.123403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:07:44.892033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:08:14.892096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:08:37.145746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:08:37.145818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:08:44.892085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:09:14.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:09:37.171698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:09:37.171736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:09:44.892140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:10:14.892145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:10:37.189756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:10:37.190012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:10:44.892069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:11:14.892155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:11:37.209362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:11:37.209410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:11:44.892129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:12:14.892077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:12:37.230863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:12:37.230928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:12:44.892091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:13:14.892332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:13:37.255461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:13:37.255517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:13:44.892106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:14:14.892092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:14:37.283546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:14:37.283608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:14:44.892093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:15:14.892162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:15:37.301374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:15:37.301421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:15:44.892079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:16:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:16:37.319612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:16:37.319656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:16:44.892123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:17:14.892126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:17:37.343697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:17:37.343915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:17:44.892069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:18:14.892109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:18:37.362655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:18:37.362700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:18:44.892083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:19:14.892095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:19:37.381171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:19:37.381365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:19:44.892170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:20:14.892089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:20:37.397113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:20:37.397168 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:20:44.897409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:21:14.892106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:21:37.453504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:21:37.453550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:21:44.892083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:22:14.892331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:22:37.471980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:22:37.472015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:22:44.892027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:23:14.892234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:23:37.489853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:23:37.489896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:23:44.892430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:24:14.892102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:24:37.508553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:24:37.508611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:24:44.892345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:25:14.892044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:25:37.532487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:25:37.532537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:25:44.892112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:26:14.892078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:26:37.553634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:26:37.553678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:26:44.892187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:27:14.892060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:27:37.570816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:27:37.570858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:27:44.892113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:28:14.892129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:28:37.596313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:28:37.596350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:28:44.892116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:29:14.892123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:29:37.617773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:29:37.617813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:29:44.892033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:30:14.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:30:37.636234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:30:37.636394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:30:44.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:31:14.892116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:31:37.654881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:31:37.654920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:31:44.892333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:32:14.892279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:32:37.673619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:32:37.673675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:32:44.892063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:33:14.892063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:33:37.691021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:33:37.691184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:33:44.892125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:34:14.892115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:34:37.708899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:34:37.708976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:34:44.892457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:35:14.892200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:35:37.725230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:35:37.725325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:35:44.892130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:36:14.892159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:36:37.743217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:36:37.743270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:36:44.892069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:37:14.892099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:37:37.765886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:37:37.766119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:37:44.892055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:38:14.892311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:38:37.786382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:38:37.786433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:38:44.892971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:39:14.892100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:39:37.809878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:39:37.810065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:39:44.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:40:14.892137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:40:37.830005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:40:37.830236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:40:44.892337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:41:14.892339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:41:37.851369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:41:37.851409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:41:44.892220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:42:14.892016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:42:37.869917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:42:37.869956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:42:44.892091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:43:14.892095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:43:37.889088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:43:37.889125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:43:44.892129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:44:14.892276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:44:37.905715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:44:37.905806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:44:44.892110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:45:14.892045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:45:37.924397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:45:37.924465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:45:44.892136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:46:14.892088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:46:37.943378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:46:37.943430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:46:44.892106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:47:14.892067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:47:37.962243 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:47:37.962282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:47:44.892083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:48:14.892067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:48:37.981775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:48:37.981925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:48:44.892048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:49:14.892051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:49:37.999756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:49:37.999800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:49:44.892080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:50:14.892231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:50:38.016229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:50:38.016280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:50:44.892247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:51:14.892300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:51:38.034805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:51:38.034849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:51:44.892082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:52:14.892114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:52:38.051204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:52:38.051236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:52:44.892088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:53:14.892129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:53:38.071003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:53:38.071606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:53:44.892489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:54:14.892091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:54:38.091446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:54:38.091503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:54:44.892431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:55:14.892030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:55:38.110289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:55:38.110323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:55:44.892096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:56:14.892130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:56:38.129815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:56:38.129854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:56:44.892044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:57:14.892085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:57:38.150400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:57:38.150435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:57:44.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:58:14.892089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:58:38.168879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:58:38.168925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:58:44.892041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:59:14.892026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 05:59:38.187232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:59:38.187267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 05:59:44.892127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:00:14.892098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:00:38.207153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:00:38.207198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:00:44.892145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:01:14.892365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:01:38.227116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:01:38.227183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:01:44.892131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:02:14.892126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:02:38.245048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:02:38.245125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:02:44.892054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:03:14.892191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:03:38.262771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:03:38.262860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:03:44.892360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:04:14.892132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:04:38.281520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:04:38.281559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:04:44.892059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:05:14.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:05:38.304779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:05:38.304823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:05:44.892097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:06:14.892222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:06:38.323725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:06:38.323766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:06:44.892085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:07:14.892168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:07:38.342644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:07:38.342718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:07:44.892186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:08:14.892050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:08:38.362541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:08:38.362583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:08:44.892602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:09:14.892157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:09:38.383377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:09:38.383429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:09:44.892202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:10:14.892043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:10:38.400929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:10:38.400970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:10:44.892062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:11:14.892046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:11:38.418870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:11:38.418913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:11:44.892074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:12:14.892106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:12:38.437361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:12:38.437398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:12:44.892101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:13:14.892140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:13:38.456406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:13:38.456444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:13:44.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:14:14.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:14:38.473239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:14:38.473322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:14:44.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:15:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:15:38.499670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:15:38.499709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:15:44.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:16:14.892226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:16:38.521068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:16:38.521121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:16:44.892143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:17:14.892134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:17:38.543146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:17:38.543235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:17:44.892057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:18:14.892167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:18:38.561332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:18:38.561393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:18:44.892134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:19:14.892055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:19:38.578157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:19:38.578200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:19:44.892299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:20:14.892044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:20:38.595740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:20:38.595782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:20:44.892696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:21:14.892077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:21:38.613654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:21:38.613694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:21:44.892140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:22:14.892093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:22:38.632413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:22:38.632460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:22:44.892129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:23:14.892081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:23:38.649781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:23:38.649819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:23:44.892088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:24:14.892076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:24:38.668756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:24:38.668791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:24:44.892075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:25:14.893439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:25:38.687412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:25:38.687466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:25:44.892124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:26:14.892268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:26:38.708049 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:26:38.708098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:26:44.892073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:27:14.892098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:27:38.731163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:27:38.731219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:27:44.892039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:28:14.897394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:28:38.748813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:28:38.748865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:28:44.892062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:29:14.892300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:29:38.770707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:29:38.770748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:29:44.892354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:30:14.892056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:30:38.787749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:30:38.787808 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:30:44.892146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:31:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:31:38.806638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:31:38.806694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:31:44.892103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:32:14.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:32:38.831450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:32:38.831511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:32:44.892081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:33:14.892054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:33:38.857933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:33:38.857993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:33:44.892125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:34:14.892123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:34:38.875455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:34:38.875493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:34:44.892103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:35:14.892065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:35:38.895776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:35:38.895947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:35:44.892153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:36:14.892166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:36:38.915571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:36:38.915637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:36:44.892147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:37:14.892083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:37:38.934155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:37:38.934340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:37:44.892049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:38:14.892036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:38:38.955268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:38:38.955304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:38:44.892090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:39:14.892324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:39:38.975199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:39:38.975255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:39:44.892108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:40:14.892074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:40:38.993666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:40:38.993715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:40:44.892063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:41:14.892118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:41:39.010901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:41:39.010936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:41:44.892063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:42:14.892067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:42:39.028766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:42:39.028810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:42:44.892164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:43:14.892178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:43:39.046877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:43:39.046959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:43:44.892104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:44:14.892457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:44:39.066857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:44:39.066895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:44:44.892247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:45:14.892111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:45:39.087996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:45:39.088232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:45:44.892407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:46:14.892389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:46:39.106055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:46:39.106101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:46:44.892159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:47:14.892063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:47:39.126846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:47:39.126914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:47:44.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:48:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:48:39.150180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:48:39.150226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:48:44.892100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:49:14.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:49:39.184031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:49:39.184066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:49:44.892327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:50:14.892117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:50:39.200767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:50:39.200803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:50:44.892116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:51:14.892089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:51:39.219641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:51:39.219678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:51:44.892079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:52:14.892084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:52:39.239284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:52:39.239358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:52:44.892112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:53:14.892121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:53:39.259302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:53:39.259343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:53:44.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:54:14.892182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:54:39.276391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:54:39.276429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:54:44.892118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:55:14.892285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:55:39.297501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:55:39.297552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:55:44.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:56:14.892067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:56:39.315199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:56:39.315237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:56:44.892093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:57:14.892090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:57:39.334888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:57:39.334949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:57:44.892217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:58:14.892111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:58:39.352752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:58:39.352865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:58:44.892190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:59:14.892129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 06:59:39.371806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:59:39.371860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 06:59:44.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:00:14.892139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:00:39.394282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:00:39.394321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:00:44.892319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:01:14.892091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:01:39.410886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:01:39.410921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:01:44.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:02:14.892102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:02:39.429226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:02:39.429303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:02:44.892122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:03:14.892146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:03:39.446910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:03:39.446954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:03:44.892119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:04:14.892212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:04:39.465367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:04:39.465411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:04:44.892100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:05:14.892153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:05:39.484069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:05:39.484252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:05:44.892162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:06:14.892062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:06:39.502132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:06:39.502257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:06:44.892054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:07:14.892069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:07:39.519567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:07:39.519623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:07:44.892224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:08:14.892127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:08:39.542599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:08:39.542645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:08:44.892060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:09:14.892078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:09:39.561315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:09:39.561378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:09:44.892095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:10:14.892101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:10:39.582700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:10:39.582735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:10:44.892099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:11:14.892263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:11:39.615712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:11:39.615763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:11:44.892229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:12:14.892139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:12:39.633421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:12:39.633492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:12:44.892089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:13:14.892102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 07:13:39.652048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:13:39.652114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 07:13:44.892123 metrics.go:34: INFO No non-zero metrics in the last 30s