By type
2022/01/20 05:55:29.377761 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/01/20 05:55:29.377807 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/20 05:55:29.377888 logstash.go:90: INFO Max Retries set to: 3
2022/01/20 05:55:29.377909 metrics.go:23: INFO Metrics logging every 30s
2022/01/20 05:55:29.377991 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/20 05:55:29.378147 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-8q7zj
2022/01/20 05:55:29.378325 async.go:63: INFO Flush Interval set to: 1s
2022/01/20 05:55:29.378370 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/20 05:55:29.378790 beat.go:221: INFO filebeat start running.
2022/01/20 05:55:29.378861 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/20 05:55:29.616606 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/20 05:55:29.616678 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/20 05:55:29.616718 crawler.go:38: INFO Loading Prospectors: 1
2022/01/20 05:55:29.616760 registrar.go:236: INFO Starting Registrar
2022/01/20 05:55:29.616948 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/20 05:55:29.616977 sync.go:41: INFO Start sending events to output
2022/01/20 05:55:29.616988 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/20 05:55:29.617235 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/20 05:55:29.617275 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/20 05:55:29.617786 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/20 05:55:29.617885 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/20 05:55:29.617966 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/20 05:55:29.618041 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/20 05:55:29.618078 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/20 05:55:29.655352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:29.655380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:30.658737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:30.658774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:32.670051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:32.670117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:36.677659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:36.677685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:44.683691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:44.683724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:55:59.378254 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=2043 registrar.writes=1
2022/01/20 05:56:00.691917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:56:00.691969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:56:29.378236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 05:56:32.700253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:56:32.700304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:56:59.378199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 05:57:29.378220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 05:57:32.708200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:57:32.708230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:57:59.378678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 05:58:29.378215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 05:58:32.716121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:58:32.716154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:58:59.378156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 05:59:29.378355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 05:59:32.723942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:59:32.723974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 05:59:59.378210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:00:29.378224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:00:32.730239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:00:32.730270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:00:34.628942 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/20 06:00:59.378177 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/20 06:01:29.378174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:01:32.737124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:01:32.737154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:01:59.378222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:02:29.378201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:02:32.746841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:02:32.746937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:02:59.378925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:03:29.378197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:03:32.758119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:03:32.758145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:03:59.378185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:04:29.378253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:04:32.766251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:04:32.766277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:04:59.378227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:05:29.378156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:05:32.774405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:05:32.774432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:05:59.378195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:06:29.378224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:06:32.783100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:06:32.783132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:06:59.378210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:07:29.378209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:07:32.791594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:07:32.791634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:07:59.378183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:08:29.378217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:08:32.799339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:08:32.799367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:08:59.378185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:09:29.378233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:09:32.809346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:09:32.809393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:09:59.378173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:10:29.378240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:10:32.817774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:10:32.817816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:10:59.378189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:11:29.378296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:11:32.825919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:11:32.825947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:11:59.378141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:12:29.378196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:12:32.835038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:12:32.835070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:12:59.378155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:13:29.378205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:13:32.843216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:13:32.843431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:13:59.378188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:14:29.378159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:14:32.851501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:32.851540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:59.378278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:15:29.378162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:15:32.860135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:15:32.860247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:15:59.378181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:16:29.378199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:16:32.868084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:16:32.868118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:16:59.378159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:17:29.378203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:17:32.882971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:17:32.883007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:17:59.378284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:18:29.378245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:18:32.891842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:18:32.891870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:18:59.378225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:19:29.378245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:19:32.900868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:19:32.900898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:19:59.378167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:20:29.378193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:20:32.907838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:20:32.907872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:20:59.378233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:21:29.378235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:21:32.923443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:21:32.923476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:21:59.378214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:22:29.378185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:22:32.931386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:22:32.931419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:22:59.378228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:23:29.378196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:23:32.939779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:23:32.939899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:23:59.378205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:24:29.378220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:24:32.948730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:24:32.948765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:24:59.378236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:25:29.378258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:25:32.956139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:25:32.956169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:25:59.378232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:26:29.378316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:26:32.963201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:26:32.963244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:26:59.378231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:27:29.378223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:27:32.974941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:27:32.974983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:27:59.378198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:28:29.378197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:28:32.982345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:28:32.982377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:28:59.378338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:29:29.378240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:29:32.994438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:29:32.994468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:29:59.378207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:30:29.378213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:30:33.002100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:30:33.002130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:30:59.378205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:31:29.378213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:31:33.010450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:31:33.010480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:31:59.378166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:32:29.378225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:32:33.016840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:32:33.016876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:32:59.378237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:33:29.378219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:33:33.027445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:33:33.027483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:33:59.378204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:34:29.378173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:34:33.034880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:34:33.034913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:34:59.378191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:35:29.378211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:35:33.042965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:35:33.043014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:35:59.378206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:36:29.378185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:36:33.050208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:36:33.050233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:36:59.378148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:37:29.378146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:37:33.060358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:37:33.060383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:37:59.378273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:38:29.378271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:38:33.066552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:38:33.066588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:38:59.378176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:39:29.378177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:39:33.076089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:39:33.076115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:39:59.378194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:40:29.378167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:40:33.082911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:40:33.082940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:40:59.378210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:41:29.378219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:41:33.092541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:41:33.092568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:41:59.378224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:42:29.378198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:42:33.100611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:42:33.100643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:42:59.378142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:43:29.378173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:43:33.110081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:43:33.110117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:43:59.378186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:44:29.378245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:44:33.119758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:44:33.119787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:44:59.378223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:45:29.378183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:45:33.127833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:45:33.127866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:45:59.378186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:46:29.378194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:46:33.134350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:46:33.134381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:46:59.378169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:47:29.378226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:47:33.145087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:47:33.145139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:47:59.378288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:48:29.378265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:48:33.153743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:48:33.153780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:48:59.378176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:49:29.378181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:49:33.167293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:49:33.167331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:49:59.378167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:50:29.378245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:50:33.174527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:50:33.174564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:50:59.378249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:51:29.378299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:51:33.183810 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:51:33.183845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:51:59.378217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:52:29.378293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:52:33.190766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:52:33.190883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:52:59.378227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:53:29.378208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:53:33.197746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:53:33.197776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:53:59.378184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:54:29.378240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:54:33.201351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:54:33.201377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:54:59.378247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:55:29.378191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:55:33.212289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:55:33.212330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:55:59.378274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:56:29.378250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:56:33.219083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:56:33.219112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:56:59.378312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:57:29.378191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:57:33.229102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:57:33.229131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:57:59.378203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:58:29.378230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:58:33.235085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:58:33.235118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:58:59.378146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:59:29.378224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:59:33.243667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:59:33.243704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:59:59.378182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:00:29.378197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:00:33.250490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:00:33.250540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:00:59.378208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:01:29.378159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:01:33.261941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:01:33.261970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:01:59.378166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:02:29.378196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:02:33.269174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:02:33.269204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:02:59.378234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:03:29.378199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:03:33.281484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:03:33.281571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:03:59.378177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:04:29.378211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:04:33.288054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:04:33.288090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:04:59.378231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:05:29.378152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:05:33.297107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:05:33.297146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:05:59.378215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:06:29.378244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:06:33.305162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:06:33.305203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:06:59.378205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:07:29.378221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:07:33.314579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:07:33.314618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:07:59.378212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:08:29.378226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:08:33.321012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:08:33.321046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:08:59.378191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:09:29.378213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:09:33.329224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:09:33.329258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:09:59.378243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:10:29.378179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:10:33.335928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:10:33.335961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:10:59.378208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:11:29.378227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:11:33.345607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:11:33.345649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:11:59.378183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:12:29.378182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:12:33.353019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:12:33.353060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:12:59.378185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:13:29.378187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:13:33.361644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:13:33.361705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:13:59.378206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:14:29.378214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:14:33.368809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:14:33.368842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:14:59.378231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:15:29.378180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:15:33.378983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:15:33.379014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:15:59.378193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:16:29.378194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:16:33.385588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:16:33.385631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:16:59.378187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:17:29.378251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:17:33.392335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:17:33.392361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:17:59.378217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:18:29.378278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:18:33.399510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:18:33.399550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:18:59.378253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:19:29.378150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:19:33.408297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:19:33.408334 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:19:59.378173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:20:29.378180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:20:33.414989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:20:33.415023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:20:59.378203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:21:29.378256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:21:33.424889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:21:33.424919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:21:59.378160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:22:29.378179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:22:33.431490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:22:33.431520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:22:59.378195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:23:29.378245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:23:33.439059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:23:33.439091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:23:59.378226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:24:29.378182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:24:33.446820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:24:33.446851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:24:59.378226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:25:29.378220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:25:33.456351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:25:33.456383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:25:59.378152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:26:29.378185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:26:33.467365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:26:33.467407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:26:59.378201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:27:29.378205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:27:33.478258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:27:33.478292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:27:59.378235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:28:29.378207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:28:33.485502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:28:33.485530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:28:59.378214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:29:29.378141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:29:33.494597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:29:33.494632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:29:59.378220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:30:29.378206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:30:33.502848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:30:33.502891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:30:59.378238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:31:29.378208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:31:33.514878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:31:33.514915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:31:59.378165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:32:29.378199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:32:33.522040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:32:33.522077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:32:59.378149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:33:29.378260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:33:33.532284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:33:33.532315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:33:59.378186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:34:29.378202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:34:33.539915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:34:33.539955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:34:59.378155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:35:29.378219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:35:33.551172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:35:33.551218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:35:59.378203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:36:29.378256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:36:33.558679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:36:33.558712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:36:59.378243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:37:29.378206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:37:33.599573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:37:33.599605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:37:59.378173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:38:29.378195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:38:33.606298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:38:33.606333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:38:59.378194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:39:29.378206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:39:33.618222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:39:33.618255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:39:59.378179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:40:29.378177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:40:33.626487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:40:33.626532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:40:59.378258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:41:29.378217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:41:33.634119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:41:33.634149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:41:59.378193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:42:29.378199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:42:33.640552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:42:33.640585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:42:59.378164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:43:29.378213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:43:33.647936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:43:33.647966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:43:59.378157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:44:29.378193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:44:33.655184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:44:33.655301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:44:59.378202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:45:29.378208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:45:33.663845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:45:33.663878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:45:59.378156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:46:29.378295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:46:33.671847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:46:33.671878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:46:59.378244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:47:29.378229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:47:33.680482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:47:33.680526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:47:59.378216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:48:29.378191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:48:33.687703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:48:33.687741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:48:59.378165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:49:29.378171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:49:33.703626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:49:33.703758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:49:59.378252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:50:29.378204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:50:33.710959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:50:33.711002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:50:59.378213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:51:29.378223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:51:33.719179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:51:33.719209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:51:59.378255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:52:29.378201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:52:33.726155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:52:33.726188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:52:59.378263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:53:29.378320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:53:33.734112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:53:33.734147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:53:59.378211 metrics.go:34: INFO No non-zero metrics in the last 30s