By type
2022/04/13 03:31:54.051216 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/13 03:31:54.051352 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/13 03:31:54.051378 metrics.go:23: INFO Metrics logging every 30s
2022/04/13 03:31:54.051719 logstash.go:90: INFO Max Retries set to: 3
2022/04/13 03:31:54.051862 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/13 03:31:54.052111 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-nn24n
2022/04/13 03:31:54.052481 async.go:63: INFO Flush Interval set to: 1s
2022/04/13 03:31:54.052510 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/13 03:31:54.053419 beat.go:221: INFO filebeat start running.
2022/04/13 03:31:54.053576 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/13 03:31:54.069774 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/13 03:31:54.069944 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/13 03:31:54.070017 crawler.go:38: INFO Loading Prospectors: 1
2022/04/13 03:31:54.070113 registrar.go:236: INFO Starting Registrar
2022/04/13 03:31:54.070146 sync.go:41: INFO Start sending events to output
2022/04/13 03:31:54.070348 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/13 03:31:54.070379 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/13 03:31:54.070543 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/13 03:31:54.070604 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/13 03:31:54.072553 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/13 03:31:54.072748 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/13 03:31:54.072874 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/13 03:31:54.073000 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/13 03:31:54.073201 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/13 03:31:59.145926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:31:59.146051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:00.175410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:00.175452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:02.190815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:02.190875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:06.252303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:06.252397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:14.272300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:14.272385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:24.052033 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/13 03:32:30.301850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:30.301956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:54.055811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:33:02.344988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:33:02.345059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:33:24.052050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:33:54.052095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:34:02.380747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:34:02.381127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:34:24.051817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:34:54.052170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:35:02.404388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:35:02.404461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:35:24.051807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:35:54.052141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:36:02.432698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:36:02.432772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:36:24.051921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:36:54.051911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:36:59.120076 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:36:59.120116 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:36:59.120267 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:36:59.120089 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:37:02.487669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:37:02.487759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:37:19.121491 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:37:24.051930 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/04/13 03:37:54.051760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:38:02.510778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:38:02.510846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:38:24.051868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:38:54.051847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:39:02.539651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:39:02.539722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:39:24.052260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:39:54.051854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:40:02.561249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:40:02.561335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:40:24.051979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:40:54.051846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:41:02.623457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:41:02.624449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:41:24.051896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:41:54.051760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:42:02.679932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:42:02.679996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:42:24.051816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:42:54.051913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:43:02.720157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:43:02.720214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:43:24.052009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:43:54.052158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:44:02.775109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:44:02.775176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:44:24.052444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:44:54.051947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:45:02.806029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:45:02.806091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:45:24.051865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:45:54.051878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:46:02.856738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:46:02.856804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:46:24.051852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:46:54.052041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:47:02.888560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:47:02.888639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:47:24.051971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:47:54.052004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:48:02.912585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:48:02.912645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:48:24.052147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:48:54.051923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:49:02.990087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:49:02.990150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:49:24.051847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:49:54.051984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:50:03.051084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:50:03.051153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:50:24.051933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:50:54.051789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:51:03.079277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:51:03.079344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:51:24.051866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:51:54.052879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:52:03.108397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:52:03.108458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:52:24.051767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:52:54.051821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:53:03.151806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:53:03.151867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:53:24.052025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:53:54.051776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:54:03.185448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:54:03.185510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:54:24.051813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:54:54.051741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:55:03.212111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:55:03.213099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:55:24.051932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:55:54.051894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:56:03.268952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:56:03.269027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:56:24.051745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:56:54.051861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:57:03.293667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:57:03.293730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:57:24.051924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:57:54.051924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:58:03.329720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:58:03.329780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:58:24.055930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:58:54.051798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:59:03.367310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:59:03.367390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:59:24.051867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:59:54.051854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:00:03.401397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:00:03.401456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:00:24.051901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:00:54.051919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:01:03.424218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:01:03.424286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:01:24.051780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:01:54.051780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:02:03.484056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:02:03.484110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:02:24.051967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:02:54.052130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:03:03.509284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:03:03.509483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:03:24.051856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:03:54.051862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:04:03.545889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:04:03.545944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:04:24.051953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:04:54.052240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:05:03.580516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:05:03.580878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:05:24.052150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:05:54.052685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:06:03.605681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:06:03.605741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:06:24.055326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:06:54.053403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:07:03.644777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:07:03.644843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:07:24.051915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:07:54.051830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:08:03.684732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:08:03.684793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:08:24.052132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:08:54.051762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:09:03.707564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:09:03.707625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:09:24.051807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:09:54.051812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:10:03.753032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:10:03.753078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:10:24.051946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:10:54.053506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:11:03.786245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:11:03.786326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:11:24.051953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:11:54.051839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:12:03.816364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:12:03.816425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:12:24.052071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:12:54.052083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:13:03.861965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:13:03.862121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:13:24.051871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:13:54.052116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:14:03.890556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:14:03.890625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:14:24.052031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:14:54.051799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:15:03.916130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:15:03.916196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:15:24.052379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:15:54.051928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:16:03.959894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:16:03.959958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:16:24.052042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:16:54.051845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:17:03.989439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:17:03.989969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:17:24.051849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:17:54.052560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:18:04.012497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:18:04.012573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:18:24.051943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:18:54.052301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:19:04.060793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:19:04.060846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:19:24.051831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:19:54.052067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:20:04.093934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:20:04.094007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:20:24.051791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:20:54.051781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:21:04.116955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:21:04.117012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:21:24.051791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:21:54.051896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:22:04.158291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:22:04.158495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:22:24.052034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:22:54.051926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:23:04.195645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:23:04.195711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:23:24.052114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:23:54.051763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:24:04.218876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:24:04.219235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:24:24.051741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:24:54.051723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:25:04.253016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:25:04.253067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:25:24.051900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:25:54.053859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:26:04.275537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:26:04.275631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:26:24.052342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:26:54.053105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:27:04.298612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:27:04.298678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:27:24.052400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:27:54.051751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:28:04.321977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:28:04.322312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:28:24.051990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:28:54.052140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:29:04.447735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:29:04.447786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:29:24.051847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:29:54.052090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:30:04.476887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:30:04.476960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:30:24.051906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:30:54.051907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:31:04.502234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:31:04.502297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:31:24.051850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:31:54.051762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:32:04.548727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:32:04.548819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:32:24.051860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:32:54.053090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:33:04.569420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:33:04.569463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:33:24.052047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:33:54.052067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:34:04.606423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:34:04.608978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:34:24.055055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:34:54.051804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:35:04.657656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:35:04.657738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:35:24.051811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:35:54.051714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:36:04.683874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:36:04.683946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:36:24.051771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:36:54.051738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:37:04.706392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:37:04.706473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:37:24.051840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:37:54.051779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:38:04.756308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:38:04.756485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:38:24.052058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:38:54.052637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:39:04.779250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:39:04.779325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:39:24.052373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:39:54.051981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:40:04.800526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:40:04.800597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:40:24.051894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:40:54.051862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:41:04.839773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:41:04.839837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:41:24.052269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:41:54.051961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:42:04.867774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:42:04.867822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:42:24.052056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:42:54.051970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:43:04.892890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:43:04.892952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:43:24.051916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:43:54.052050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:44:04.918306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:44:04.918375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:44:24.052214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:44:54.051894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:45:04.995939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:45:04.996961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:45:24.052038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:45:54.051824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:46:05.019748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:46:05.019822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:46:24.051759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:46:54.051879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:47:05.079910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:47:05.079976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:47:24.051875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:47:54.051808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:48:05.101968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:48:05.102020 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:48:24.051836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:48:54.051921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:49:05.152518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:49:05.152582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:49:24.051929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:49:54.051840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:50:05.180881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:50:05.180959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:50:24.051816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:50:54.051956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:51:05.206499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:51:05.206581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:51:24.051819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:51:54.056994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:52:05.264403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:52:05.264487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:52:24.052251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:52:54.052001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:53:05.298350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:53:05.298411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:53:24.051856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:53:54.051759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:54:05.335641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:54:05.335713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:54:24.052692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:54:54.051843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:55:05.369911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:55:05.369975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:55:24.051901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:55:54.051812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:56:05.407240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:56:05.407651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:56:24.051853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:56:54.051970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:57:05.443187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:57:05.443250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:57:24.053855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:57:54.051883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:58:05.470656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:58:05.470909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:58:24.051978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:58:54.051885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:59:05.502758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:59:05.502803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:59:24.051781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:59:54.051847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:00:05.539990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:00:05.540055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:00:24.051990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:00:54.052035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:01:05.586585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:01:05.586638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:01:24.051970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:01:54.051794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:02:05.610497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:02:05.610564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:02:24.051897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:02:54.051813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:03:05.662316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:03:05.662362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:03:24.052705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:03:54.051892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:04:05.698172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:04:05.698234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:04:24.051745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:04:54.052023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:05:05.760379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:05:05.760462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:05:24.051785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:05:54.051802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:06:05.814661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:06:05.814732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:06:24.051756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:06:54.051805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:07:05.872756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:07:05.872811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:07:24.051856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:07:54.052069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:08:05.908288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:08:05.908359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:08:24.051804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:08:54.051937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:09:05.944030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:09:05.944086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:09:24.052769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:09:54.051780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:10:05.979408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:10:05.979854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:10:24.052007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:10:54.052239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:11:06.060665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:11:06.060758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:11:24.051974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:11:54.051838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:12:06.106899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:12:06.106962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:12:24.051928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:12:54.051931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:13:06.140966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:13:06.141201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:13:24.051785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:13:54.051828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:14:06.178126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:14:06.178191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:14:24.051903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:14:54.051830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:15:06.279014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:15:06.279080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:15:24.052346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:15:54.051922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:16:06.321587 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:16:06.321646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:16:24.051765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:16:54.051912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:17:06.363170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:17:06.363278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:17:24.052039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:17:54.055922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:18:06.398775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:18:06.398850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:18:24.052017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:18:54.051806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:19:06.427810 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:19:06.427890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:19:24.052036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:19:54.052077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:20:06.471420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:20:06.471528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:20:24.051898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:20:54.051876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:21:06.500033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:21:06.500102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:21:24.051938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:21:54.051729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:22:06.543779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:22:06.543839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:22:24.051780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:22:54.051829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:23:06.589079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:23:06.589165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:23:24.051870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:23:54.051863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:24:06.611251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:24:06.611320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:24:24.051785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:24:54.051838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:25:06.661661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:25:06.661729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:25:24.051802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:25:54.051805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:26:06.691352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:26:06.691418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:26:24.051959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:26:54.052263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:27:06.718248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:27:06.718302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:27:24.051882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:27:54.051974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:28:06.758903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:28:06.758982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:28:24.051901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:28:54.051818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:29:06.787997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:29:06.788068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:29:24.051898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:29:54.052494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:30:06.812716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:30:06.812801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:30:24.051993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:30:54.052113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:31:06.871637 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:31:06.871690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:31:24.051758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:31:54.051828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:32:06.906567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:32:06.906649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:32:24.051803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:32:54.052944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:33:06.979802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:33:06.979874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:33:24.052552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:33:54.051830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:34:07.024777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:34:07.024821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:34:24.051780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:34:54.051773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:35:07.079604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:35:07.079661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:35:24.055491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:35:54.051852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:36:07.115316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:36:07.115380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:36:24.052058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:36:54.051852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:37:07.155059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:37:07.155114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:37:24.051888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:37:54.053019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:38:07.203588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:38:07.203677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:38:24.051937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:38:54.052021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:39:07.232001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:39:07.232067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:39:24.051955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:39:54.051860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:40:07.275518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:40:07.275566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:40:24.052957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:40:54.052040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:41:07.302028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:41:07.302093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:41:24.051901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:41:54.051921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:42:07.361834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:42:07.361894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:42:24.052018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:42:54.051914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:43:07.394691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:43:07.394755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:43:24.054946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:43:54.051819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:44:07.487899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:44:07.487953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:44:24.051897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:44:54.051763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:45:07.517953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:45:07.518045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:45:24.051852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:45:54.051749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:46:07.576574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:46:07.577042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:46:24.051836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:46:54.051761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:47:07.651986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:47:07.652050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:47:24.051909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:47:54.051846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:48:07.705712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:48:07.705770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:48:24.051892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:48:54.052398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:49:07.770273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:49:07.770592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:49:24.051848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:49:54.051974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:50:07.808393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:50:07.808456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:50:24.051857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:50:54.051830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:51:07.864553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:51:07.864621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:51:24.052087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:51:54.051855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:52:07.890958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:52:07.891029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:52:24.051834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:52:54.051823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:53:07.933297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:53:07.933365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:53:24.051991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:53:54.052115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:54:07.978049 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:54:07.978122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:54:24.051708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:54:54.052336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:55:08.002035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:55:08.002098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:55:24.051923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:55:54.051981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:56:08.076516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:56:08.076564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:56:24.051961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:56:54.051851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:57:08.097731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:57:08.097790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:57:24.052033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:57:54.051889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:58:08.122972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:58:08.123419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:58:24.051874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:58:54.051940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:59:08.172235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:59:08.172302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 05:59:24.051873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 05:59:54.051907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:00:08.201998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:00:08.202072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:00:24.051927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:00:54.051828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:01:08.258720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:01:08.258798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:01:24.051994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:01:54.052047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:02:08.296652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:02:08.296718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:02:24.052086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:02:54.052119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:03:08.333059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:03:08.334975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:03:24.052157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:03:54.051897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:04:08.400569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:04:08.400662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:04:24.052226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:04:54.052111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:05:08.471219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:05:08.471266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:05:24.051752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:05:54.051768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:06:08.499443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:06:08.499786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:06:24.051805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:06:54.051897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:07:08.550093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:07:08.550150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:07:24.051886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:07:54.051871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:08:08.582467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:08:08.582549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:08:24.052023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:08:54.051758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:09:08.608806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:09:08.608867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:09:24.052089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:09:54.052109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:10:08.648022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:10:08.648090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:10:24.051930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:10:54.053278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:11:08.698455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:11:08.698525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:11:24.052025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:11:54.052027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:12:08.804069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:12:08.804132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:12:24.053052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:12:54.051852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:13:08.871062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:13:08.871109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:13:24.052049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:13:54.051798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:14:08.920759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:14:08.920826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:14:24.051843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:14:54.051864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:15:08.982228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:15:08.982290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:15:24.051794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:15:54.051837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:16:09.032647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:16:09.032895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:16:24.051920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:16:54.051740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:17:09.092478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:17:09.092553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:17:24.053055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:17:54.051796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:18:09.127359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:18:09.127423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:18:24.052403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:18:54.051846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:19:09.160088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:19:09.160156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:19:24.051932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:19:54.051989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:20:09.214109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:20:09.214213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:20:24.052085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:20:54.052089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:21:09.260176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:21:09.260254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:21:24.051800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:21:54.055893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:22:09.314887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:22:09.314944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:22:24.052104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:22:54.051806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:23:09.367098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:23:09.367162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:23:24.052565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:23:54.051814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:24:09.468449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:24:09.468499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:24:24.051837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:24:54.051779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 06:25:09.535796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:25:09.535865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 06:25:24.052033 metrics.go:34: INFO No non-zero metrics in the last 30s