By type
2022/04/02 03:09:51.020675 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/04/02 03:09:51.020864 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:09:51.020881 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:09:51.021232 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:09:51.021403 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:09:51.021722 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-5rn7d
2022/04/02 03:09:51.022068 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:09:51.022141 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:09:51.022962 beat.go:221: INFO filebeat start running.
2022/04/02 03:09:51.023070 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:09:51.027234 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:09:51.027325 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:09:51.027383 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:09:51.027407 registrar.go:236: INFO Starting Registrar
2022/04/02 03:09:51.027451 sync.go:41: INFO Start sending events to output
2022/04/02 03:09:51.027685 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:09:51.027685 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:09:51.027933 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/02 03:09:51.027970 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:10:11.030668 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/02 03:10:11.031179 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/02 03:10:11.031310 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/02 03:10:11.031367 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/02 03:10:11.031385 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/02 03:10:16.051806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:16.051883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:17.056869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:17.056917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:19.062508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:19.062605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:21.021591 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=64 registrar.writes=1
2022/04/02 03:10:23.069915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:23.070048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:31.076664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:31.076699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:47.095035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:47.095237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:51.022111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:11:19.115196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:11:19.115251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:11:21.021375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:11:51.021389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:12:19.134404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:12:19.134439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:12:21.021417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:12:51.021352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:13:19.156971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:13:19.157032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:13:21.021443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:13:51.021601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:14:19.176058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:14:19.176121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:14:21.021442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:14:51.021405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:15:16.046355 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:16.046505 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:16.046548 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:16.046595 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:19.201086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:15:19.201136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:15:21.021516 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/02 03:15:26.050554 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:51.021474 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/04/02 03:16:19.223936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:16:19.223989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:16:21.021398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:16:51.021425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:17:19.243345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:17:19.243402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:17:21.021676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:17:51.021483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:18:19.262664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:18:19.262719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:18:21.021404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:18:51.021449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:19:19.291681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:19:19.291746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:19:21.021399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:19:51.021469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:20:19.313433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:20:19.313499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:20:21.021374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:20:51.021618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:21:19.335875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:21:19.335948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:21:21.021376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:21:51.021428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:22:19.354056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:22:19.354104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:22:21.021467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:22:51.021375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:23:19.373518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:23:19.373560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:23:21.021403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:23:51.021478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:24:19.392565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:24:19.392605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:24:21.021536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:24:51.021446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:25:19.411754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:25:19.411793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:25:21.021501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:25:51.021410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:26:19.439743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:26:19.439784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:26:21.021341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:26:51.021406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:27:19.460695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:27:19.460840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:27:21.021342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:27:51.021561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:19.479464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:28:19.480002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:28:21.021401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:51.021387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:19.499857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:29:19.499894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:29:21.021527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:51.021409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:19.518062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:30:19.518124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:30:21.021445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:51.021330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:19.535740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:31:19.535798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:31:21.021345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:51.021437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:19.554521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:32:19.554662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:32:21.021439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:51.021551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:19.576784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:33:19.576840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:33:21.021410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:51.021463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:19.597083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:34:19.597141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:34:21.021452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:51.021428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:19.616330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:35:19.616390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:35:21.021409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:51.021491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:19.635192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:36:19.635235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:36:21.021335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:51.021447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:19.654858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:37:19.654961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:37:21.021427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:51.021413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:19.674798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:38:19.674866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:38:21.021488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:51.021406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:19.697339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:39:19.697392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:39:21.021501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:51.021531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:19.715539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:40:19.715594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:40:21.021479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:51.021459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:19.734846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:41:19.734910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:41:21.021542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:51.021548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:19.752107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:42:19.752158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:42:21.021482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:51.021370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:19.770317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:43:19.770361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:43:21.021512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:51.021372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:19.787516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:44:19.787565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:44:21.021430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:51.021403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:19.805689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:45:19.805732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:45:21.021593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:51.021503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:19.823187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:46:19.823221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:46:21.021418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:51.021470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:19.842406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:47:19.842769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:47:21.021553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:51.021389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:19.860492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:48:19.860533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:48:21.021305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:51.021388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:19.879598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:49:19.879639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:49:21.021456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:51.021471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:19.898435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:50:19.898501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:50:21.021357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:51.021418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:19.919360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:51:19.919422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:51:21.021456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:51.021428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:19.937435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:52:19.937487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:52:21.021391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:51.021425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:19.960282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:53:19.960357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:53:21.021443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:51.027361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:19.981522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:19.982001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:21.021493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:51.021456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:20.002101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:20.002139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:21.021385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:51.021437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:20.024381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:20.024447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:21.021463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:51.021454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:20.044299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:20.044337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:21.021410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:51.021474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:20.064560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:20.064694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:21.021392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:51.021383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:20.084965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:20.085020 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:21.021382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:51.021455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:20.104618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:20.104679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:21.021380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:51.021584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:20.125154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:20.125212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:21.021441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:51.021485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:20.144844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:20.144889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:21.021443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:51.021388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:20.163935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:20.163982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:21.021436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:51.021441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:20.182752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:20.182800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:21.021417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:51.021460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:20.199668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:20.199702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:21.021463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:51.021482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:20.219559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:20.219609 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:21.021468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:51.021442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:20.239291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:20.239352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:21.021368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:51.021499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:20.257158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:20.257226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:21.021550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:51.021554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:20.285319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:20.285367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:21.021431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:51.021444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:20.306312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:20.306463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:21.021409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:51.021393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:20.325676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:20.325720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:21.021558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:51.021513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:20.350009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:20.350063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:21.021391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:51.021445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:20.367352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:20.367402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:21.021437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:51.021402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:20.401554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:20.401613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:21.021345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:51.021530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:20.421865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:20.421916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:21.021506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:51.022878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:20.439876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:20.439950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:21.021360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:51.021353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:20.465087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:20.465135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:21.021382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:51.021383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:20.485817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:20.485855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:21.021412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:51.021354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:20.506704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:20.506764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:21.021363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:51.021360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:20.525074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:20.525112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:21.021393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:51.021509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:20.547953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:20.547997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:21.021416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:51.021423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:20.567540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:20.567670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:21.021623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:51.021431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:20.584821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:20.584877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:21.021444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:51.022031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:20.607385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:20.607421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:21.021425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:51.021412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:20.626423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:20.626481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:21.021419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:51.021414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:20.645542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:20.645578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:21.021348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:51.021362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:20.664956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:20.664998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:21.021361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:51.021434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:20.687212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:20.687259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:21.021417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:51.021443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:20.706524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:20.706701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:21.021398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:51.021448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:20.726435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:20.726485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:21.021416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:51.021398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:20.746480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:20.746522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:21.021359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:51.021351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:20.765555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:20.765603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:21.021365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:51.021405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:20.784448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:20.784501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:21.021412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:51.021381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:20.803441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:20.803505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:21.021430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:51.021350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:20.824229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:20.824269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:21.021405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:51.021473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:20.842968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:20.843125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:21.021434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:51.021428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:20.862897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:20.862960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:21.021486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:51.021461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:20.882345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:20.882421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:21.021446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:51.021537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:20.900403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:20.900444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:21.021429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:51.021363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:20.918984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:20.919030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:21.021387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:51.021488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:20.947921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:20.947971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:21.021377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:51.021518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:20.964965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:20.965002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:21.021370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:51.021420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:20.984233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:20.984274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:21.021416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:51.021422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:21.004043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:21.004125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:21.021409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:51.021372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:21.021377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:21.022610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:21.022637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:51.021411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:21.021409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:21.041882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:21.041925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:51.021349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:21.021346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:21.061209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:21.061251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:51.021417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:21.021397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:21.082225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:21.082265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:51.021438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:21.022641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:21.100577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:21.100613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:51.021670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:21.021371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:21.118921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:21.118984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:51.021408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:21.021496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:21.137899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:21.137937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:51.021399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:21.021478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:21.161371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:21.161418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:51.021500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:21.026686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:21.182447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:21.182514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:51.021395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:21.021374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:21.202666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:21.202716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:51.021741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:21.021404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:21.221685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:21.221732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:51.021366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:21.021473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:21.240520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:21.240573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:51.021436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:21.021413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:21.259614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:21.259743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:51.021449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:21.021527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:21.279316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:21.279374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:51.022000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:21.021443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:21.300024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:21.300071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:51.021421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:21.021529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:21.318106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:21.318149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:51.021469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:21.021398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:21.337164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:21.337211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:51.021458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:21.021404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:21.355210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:21.355335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:51.027363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:21.021486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:21.374776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:21.374828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:51.021481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:21.021438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:21.393774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:21.393819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:51.021410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:21.021467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:21.413616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:21.413670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:51.021423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:21.021434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:21.432181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:21.432504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:51.021391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:21.021412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:21.450042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:21.450085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:51.021405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:21.021363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:21.468878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:21.468930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:51.021461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:21.021455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:21.489452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:21.489493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:51.021503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:21.021499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:21.508035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:21.508067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:51.021448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:21.021412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:21.527002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:21.527085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:51.021402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:21.023334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:21.547164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:21.547222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:51.021401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:21.021411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:21.567808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:21.567863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:51.021421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:21.021367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:21.587471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:21.587513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:51.021477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:21.021419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:21.604850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:21.604891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:51.021527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:21.021419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:21.624036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:21.624074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:51.021359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:21.021423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:21.643866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:21.643912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:51.021449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:21.021599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:21.664087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:21.664127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:51.021548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:21.021398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:21.682884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:21.682924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:51.021465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:21.021453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:21.700190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:21.700254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:51.021356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:21.021497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:21.720742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:21.720775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:51.021498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:21.021389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:21.739652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:21.739700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:51.021416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:21.021457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:21.758600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:21.758659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:51.021380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:21.021413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:21.777199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:21.777252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:51.021463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:21.021415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:21.796751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:21.796801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:51.021321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:21.021416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:21.815485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:21.815555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:51.021445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:21.021382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:21.832978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:21.833028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:51.021459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:21.021484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:21.852858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:21.852896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:51.021363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:21.021443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:21.870035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:21.870086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:51.021359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:21.021530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:21.887981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:21.888037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:51.021415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:21.021529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:21.907634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:21.907703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:51.021366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:21.021366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:21.925985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:21.926029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:51.021409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:21.021338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:21.944441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:21.944505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:51.021411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:21.021424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:21.962885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:21.962924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:51.021336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:21.021412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:21.981413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:21.981486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:51.021373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:21.021441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:22.000154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:22.000188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:51.021418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:21.021483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:22.018357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:22.018401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:51.021467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:21.021377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:22.036358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:22.036415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:51.021458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:21.021448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:22.056606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:22.056643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:51.021445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:21.021438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:22.074949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:22.074990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:51.021426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:21.021374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:22.093454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:22.093500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:51.021394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:21.021430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:22.114178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:22.114221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:51.021404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:21.021466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:22.131740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:22.131783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:51.021532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:21.021431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:22.151372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:22.151415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:51.021517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:21.021384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:22.170385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:22.170432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:51.021368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:21.021604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:22.189191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:22.189245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:51.021460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:21.021524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:22.206546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:22.206602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:51.021426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:21.021370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:22.226818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:22.226859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:51.021433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:21.021412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:22.244896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:22.244952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:51.021412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:21.021467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:22.261958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:22.262016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:51.021419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:21.021485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:22.281831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:22.282050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:51.021394 metrics.go:34: INFO No non-zero metrics in the last 30s