By type
2022/03/08 02:31:02.108711 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/03/08 02:31:02.108745 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/08 02:31:02.108799 logstash.go:90: INFO Max Retries set to: 3
2022/03/08 02:31:02.108858 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/08 02:31:02.108868 metrics.go:23: INFO Metrics logging every 30s
2022/03/08 02:31:02.108950 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-cnq48
2022/03/08 02:31:02.109092 async.go:63: INFO Flush Interval set to: 1s
2022/03/08 02:31:02.109112 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/08 02:31:02.109466 beat.go:221: INFO filebeat start running.
2022/03/08 02:31:02.109534 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/08 02:31:02.325654 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/08 02:31:02.325712 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/08 02:31:02.325791 crawler.go:38: INFO Loading Prospectors: 1
2022/03/08 02:31:02.325922 registrar.go:236: INFO Starting Registrar
2022/03/08 02:31:02.325971 sync.go:41: INFO Start sending events to output
2022/03/08 02:31:02.326005 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/08 02:31:02.326056 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/08 02:31:02.326184 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/08 02:31:02.326261 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/08 02:31:32.109455 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/08 02:31:52.329802 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/08 02:31:52.330032 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/08 02:31:52.330136 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/08 02:31:52.330166 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/08 02:31:52.330291 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/08 02:31:57.337379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:31:57.337425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:31:58.342554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:31:58.342581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:00.347474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:00.347516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:02.109332 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=55
2022/03/08 02:32:04.357247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:04.357288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:12.365419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:12.365448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:28.374701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:28.374740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:32:32.109307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:33:00.384859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:33:00.384902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:33:02.109355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:33:32.109254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:34:00.421349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:00.421408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:02.109364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:34:32.109398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:35:00.430187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:35:00.430356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:35:02.109297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:35:32.109271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:36:00.443905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:36:00.443949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:36:02.109265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:36:32.109328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:36:57.343456 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/08 02:37:00.452594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:37:00.452631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:37:02.109270 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/08 02:37:12.342471 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/08 02:37:12.342481 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/08 02:37:12.342646 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/08 02:37:32.109343 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/03/08 02:38:00.461152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:38:00.461208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:38:02.109331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:38:32.109233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:39:00.469970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:39:00.470013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:39:02.109363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:39:32.110296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:40:00.480421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:40:00.480596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:40:02.109340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:40:32.109287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:41:00.490364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:41:00.490418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:41:02.109287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:41:32.109254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:42:00.502258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:42:00.502299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:42:02.109293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:42:32.109331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:43:00.511660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:43:00.511698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:43:02.109444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:43:32.109437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:44:00.520153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:44:00.520227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:44:02.109406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:44:32.109438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:45:00.529566 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:45:00.529619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:45:02.109349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:45:32.109175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:46:00.538336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:46:00.538385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:46:02.109376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:46:32.109341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:47:00.547595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:47:00.547637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:47:02.109205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:47:32.109301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:48:00.556050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:48:00.556079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:48:02.109280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:48:32.109375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:49:00.565241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:49:00.565285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:49:02.109345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:49:32.109243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:50:00.575751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:50:00.575801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:50:02.109303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:50:32.109358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:51:00.586952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:51:00.587038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:51:02.109318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:51:32.109168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:52:00.598822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:52:00.598878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:52:02.109213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:52:32.109376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:53:00.608985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:53:00.609030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:53:02.109275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:53:32.109303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:54:00.619256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:54:00.619320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:54:02.109229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:54:32.109216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:55:00.628955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:55:00.628989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:55:02.109297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:55:32.109242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:56:00.639219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:56:00.639268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:56:02.109326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:56:32.109318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:57:00.649005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:57:00.649050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:57:02.109371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:57:32.109185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:58:00.658650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:58:00.658741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:58:02.109253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:58:32.109280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:59:00.668493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:59:00.668568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:59:02.109329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:59:32.109334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:00:00.676665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:00:00.676716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:00:02.109212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:00:32.109340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:01:00.685770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:01:00.685817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:01:02.109258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:01:32.109171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:02:00.693979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:02:00.694007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:02:02.109255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:02:32.109295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:03:00.702967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:03:00.703007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:03:02.109258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:03:32.109315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:04:00.710910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:04:00.711034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:04:02.109366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:04:32.109357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:05:00.719853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:05:00.719888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:05:02.109293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:05:32.109286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:06:00.730314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:06:00.730366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:06:02.109342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:06:32.109361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:07:00.739726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:07:00.739774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:07:02.109370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:07:32.109295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:08:00.750815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:08:00.750859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:08:02.109392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:08:32.109314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:09:00.761251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:09:00.761303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:09:02.109156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:09:32.109309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:10:00.770290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:10:00.770334 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:10:02.109275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:10:32.109307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:11:00.780223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:11:00.780262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:11:02.109283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:11:32.109206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:12:00.791151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:12:00.791192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:12:02.109378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:12:32.109319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:13:00.802582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:13:00.802641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:13:02.109158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:13:32.109304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:14:00.812285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:14:00.812324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:14:02.109237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:14:32.109285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:15:00.821588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:15:00.821632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:15:02.109371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:15:32.109374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:16:00.831562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:16:00.831605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:16:02.109351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:16:32.109360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:17:00.840320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:17:00.840358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:17:02.109461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:17:32.109422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:18:00.850312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:18:00.850357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:18:02.109276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:18:32.109375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:19:00.860505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:19:00.860560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:19:02.109365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:19:32.109301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:20:00.871658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:20:00.871727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:20:02.109428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:20:32.109334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:21:00.881615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:21:00.881668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:21:02.109362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:21:32.109283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:22:00.892687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:22:00.892721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:22:02.109330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:22:32.109298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:23:00.904678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:23:00.904725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:23:02.109452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:23:32.109193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:24:00.914073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:24:00.914121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:24:02.109302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:24:32.109271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:25:00.923249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:25:00.923296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:25:02.109330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:25:32.109360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:26:00.933514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:26:00.933553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:26:02.109368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:26:32.109357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:27:00.944559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:27:00.944605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:27:02.109284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:27:32.109330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:28:00.953861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:28:00.953900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:28:02.109382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:28:32.109369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:29:00.964492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:29:00.964534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:29:02.109357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:29:32.109305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:30:00.974510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:30:00.974565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:30:02.109374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:30:32.109437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:31:00.984133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:31:00.984188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:31:02.109327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:31:32.109369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:32:00.994731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:32:00.994801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:32:02.109367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:32:32.109245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:33:01.006629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:33:01.006680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:33:02.109291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:33:32.109211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:34:01.016935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:34:01.016980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:34:02.109227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:34:32.109337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:35:01.027573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:35:01.027618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:35:02.109306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:35:32.109360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:36:01.037255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:36:01.037320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:36:02.109347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:36:32.109279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:37:01.046019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:37:01.046069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:37:02.109220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:37:32.109299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:38:01.055105 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:38:01.055164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:38:02.109346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:38:32.109253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:39:01.064334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:39:01.064381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:39:02.109217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:39:32.109266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:40:01.073568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:40:01.073633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:40:02.109155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:40:32.109330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:41:01.083057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:41:01.083099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:41:02.109387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:41:32.109356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:42:01.091352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:42:01.091399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:42:02.109323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:42:32.109282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:43:01.101263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:43:01.101313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:43:02.109298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:43:32.109351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:44:01.111558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:44:01.111607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:44:02.109362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:44:32.109324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:45:01.119117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:45:01.119174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:45:02.109303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:45:32.109304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:46:01.128518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:46:01.128555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:46:02.109278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:46:32.109244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:47:01.137011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:47:01.137049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:47:02.109234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:47:32.109255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:48:01.146577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:48:01.146605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:48:02.109350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:48:32.109261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:49:01.155914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:49:01.155965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:49:02.109298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:49:32.109285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:50:01.164521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:50:01.164588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:50:02.109199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:50:32.109384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:51:01.173705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:51:01.173748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:51:02.109348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:51:32.109343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:52:01.183123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:52:01.183163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:52:02.109366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:52:32.109369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:53:01.191476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:53:01.191520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:53:02.109285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:53:32.109297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:54:01.202127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:54:01.202168 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:54:02.109327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:54:32.109261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:55:01.210449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:55:01.210504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:55:02.109330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:55:32.109408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:56:01.219825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:56:01.219881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:56:02.109350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:56:32.109394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:57:01.228573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:57:01.228622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:57:02.109358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:57:32.109275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:58:01.237730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:58:01.237783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:58:02.109281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:58:32.109275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:59:01.246448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:59:01.246488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:59:02.109372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:59:32.109191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:00:01.256164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:00:01.256209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:00:02.109441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:00:32.109238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:01:01.265243 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:01:01.265290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:01:02.109373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:01:32.109303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:02:01.273081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:02:01.273112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:02:02.109216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:02:32.109329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:03:01.281243 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:03:01.281280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:03:02.109290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:03:32.109553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:04:01.290141 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:04:01.290192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:04:02.109272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:04:32.109141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:05:01.299012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:05:01.299058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:05:02.109337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:05:32.109387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:06:01.308916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:06:01.308967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:06:02.109300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:06:32.109290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:07:01.318129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:07:01.318166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:07:02.109239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:07:32.109384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:08:01.326716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:08:01.326758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:08:02.109307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:08:32.109297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:09:01.336460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:09:01.336506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:09:02.109292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:09:32.109255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:10:01.345979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:10:01.346016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:10:02.109279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:10:32.109262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:11:01.353690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:11:01.353733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:11:02.109261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:11:32.109273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:12:01.363811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:12:01.363968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:12:02.109254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:12:32.109285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:13:01.372111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:13:01.372153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:13:02.109198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:13:32.109273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:14:01.379261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:14:01.379304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:14:02.109337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:14:32.109272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:15:01.388862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:15:01.388906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:15:02.109222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:15:32.109320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:16:01.397662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:16:01.397706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:16:02.109318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:16:32.109341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:17:01.406106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:17:01.406149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:17:02.109287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:17:32.109327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:18:01.414622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:18:01.414663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:18:02.109367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:18:32.109346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:19:01.424627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:19:01.424784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:19:02.109399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:19:32.109340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:20:01.433999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:20:01.434050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:20:02.109234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:20:32.109382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:21:01.443456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:21:01.443507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:21:02.109315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:21:32.109213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:22:01.452024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:22:01.452070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:22:02.109361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:22:32.109299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:23:01.460792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:23:01.460828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:23:02.109335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:23:32.109313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:24:01.470256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:24:01.470291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:24:02.109358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:24:32.109280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:25:01.480018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:25:01.480065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:25:02.109426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:25:32.109372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:26:01.489017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:26:01.489062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:26:02.109463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:26:32.109191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:27:01.497183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:27:01.497227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:27:02.109460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:27:32.109232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:28:01.507201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:28:01.507241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:28:02.109293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:28:32.109282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:29:01.516675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:29:01.516720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:29:02.109405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:29:32.109263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:30:01.525679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:30:01.525731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:30:02.109331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:30:32.109277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:31:01.535319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:31:01.535359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:31:02.109197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:31:32.109353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:32:01.544099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:32:01.544143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:32:02.109387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:32:32.109278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:33:01.553713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:33:01.553758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:33:02.109263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:33:32.109300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:34:01.563932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:34:01.563980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:34:02.109360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:34:32.109363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:35:01.573992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:35:01.574045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:35:02.109234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:35:32.109240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:36:01.583967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:36:01.584021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:36:02.109225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:36:32.109239 metrics.go:34: INFO No non-zero metrics in the last 30s