By type
2022/01/22 03:49:16.887965 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/22 03:49:16.888002 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/22 03:49:16.888105 metrics.go:23: INFO Metrics logging every 30s
2022/01/22 03:49:16.888100 logstash.go:90: INFO Max Retries set to: 3
2022/01/22 03:49:16.888169 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/22 03:49:16.888263 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-9t4hq
2022/01/22 03:49:16.888401 async.go:63: INFO Flush Interval set to: 1s
2022/01/22 03:49:16.888425 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/22 03:49:16.888875 beat.go:221: INFO filebeat start running.
2022/01/22 03:49:16.888941 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/22 03:49:17.244737 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/22 03:49:17.244820 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/22 03:49:17.244864 crawler.go:38: INFO Loading Prospectors: 1
2022/01/22 03:49:17.244894 registrar.go:236: INFO Starting Registrar
2022/01/22 03:49:17.245016 sync.go:41: INFO Start sending events to output
2022/01/22 03:49:17.245050 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/22 03:49:17.245267 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/22 03:49:17.245353 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/22 03:49:17.245064 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/22 03:49:17.246005 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/22 03:49:17.246035 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/22 03:49:17.246129 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/22 03:49:17.246286 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/22 03:49:17.246368 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/22 03:49:22.254769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:22.254821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:23.260939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:23.260969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:25.263354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:25.263377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:29.270014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:29.270056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:37.277311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:37.277344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:46.888408 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=356 registrar.writes=1
2022/01/22 03:49:53.284619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:49:53.284645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:50:16.888360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:50:25.290911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:50:25.290941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:50:46.888581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:51:16.888381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:51:25.298690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:51:25.298733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:51:46.888377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:52:16.888330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:52:25.305981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:52:25.306025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:52:46.888473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:53:16.888446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:53:25.313826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:53:25.313853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:53:46.888348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:54:16.888371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:54:22.254041 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/22 03:54:22.254088 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/22 03:54:22.254047 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/22 03:54:22.254125 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/22 03:54:22.254576 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/01/22 03:54:25.321740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:54:25.321774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:54:46.888404 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/01/22 03:55:16.888321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:55:25.329311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:55:25.329338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:55:46.888403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:56:16.888347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:56:25.338246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:56:25.338336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:56:46.888433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:57:16.888448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:57:25.347545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:57:25.347569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:57:46.888373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:58:16.888374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:58:25.355579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:58:25.355608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:58:46.888391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:59:16.888388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 03:59:25.362930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:59:25.362972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 03:59:46.888364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:00:16.888349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:00:25.371716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:00:25.371755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:00:46.888369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:01:16.888334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:01:25.380310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:01:25.380334 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:01:46.888370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:02:16.888337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:02:25.387510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:02:25.387539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:02:46.888371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:03:16.888323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:03:25.397975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:03:25.398009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:03:46.888373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:04:16.888304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:04:25.404849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:04:25.404891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:04:46.888373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:05:16.888381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:05:25.412874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:05:25.412910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:05:46.888320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:06:16.888372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:06:25.419743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:06:25.419781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:06:46.888370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:07:16.888339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:07:25.427327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:07:25.427358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:07:46.888371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:08:16.888368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:08:25.434329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:08:25.434370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:08:46.888395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:09:16.888351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:09:25.441977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:09:25.442010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:09:46.888406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:10:16.888398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:10:25.449211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:10:25.449264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:10:46.888378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:11:16.888389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:11:25.456951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:11:25.456980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:11:46.888414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:12:16.888357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:12:25.464275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:12:25.464304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:12:46.888371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:13:16.888342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:13:25.472462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:13:25.472485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:13:46.888311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:14:16.888349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:14:25.480840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:14:25.480872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:14:46.888315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:15:16.888340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:15:25.487873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:15:25.487903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:15:46.888358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:16:16.888402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:16:25.495003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:16:25.495036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:16:46.888531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:17:16.888419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:17:25.502236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:17:25.502263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:17:46.888355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:18:16.888433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:18:25.509656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:18:25.509700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:18:46.888397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:19:16.888367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:19:25.518431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:19:25.518461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:19:46.888419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:20:16.888351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:20:25.525433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:20:25.525458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:20:46.888375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:21:16.888349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:21:25.532432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:21:25.532461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:21:46.888335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:22:16.888336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:22:25.539857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:22:25.539886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:22:46.888352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:23:16.889568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:23:25.547205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:23:25.547235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:23:46.888376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:24:16.888380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:24:25.555275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:24:25.555311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:24:46.888378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:25:16.888352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:25:25.562813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:25:25.562843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:25:46.888357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:26:16.888401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:26:25.570286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:26:25.570320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:26:46.888415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:27:16.888498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:27:25.577605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:27:25.577637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:27:46.888426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:28:16.888358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:28:25.585321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:28:25.585360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:28:46.888368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:29:16.888324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:29:25.593869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:29:25.593893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:29:46.888306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:30:16.888405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:30:25.601765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:30:25.601817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:30:46.888347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:31:16.888396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:31:25.609245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:31:25.609286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:31:46.888346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:32:16.888338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:32:25.616725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:32:25.616756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:32:46.888340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:33:16.888346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:33:25.627315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:33:25.627359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:33:46.888358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:34:16.888411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:34:25.638673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:34:25.638728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:34:46.888329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:35:16.888392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:35:25.646836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:35:25.646873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:35:46.888365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:36:16.888427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:36:25.653805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:36:25.653835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:36:46.888341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:37:16.888487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:37:25.661122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:37:25.661151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:37:46.888362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:38:16.888392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:38:25.668824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:38:25.668874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:38:46.888352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:39:16.888333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:39:25.682112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:39:25.682145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:39:46.888299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:40:16.888389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:40:25.688684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:40:25.688716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:40:46.888361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:41:16.888327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:41:25.696144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:41:25.696180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:41:46.888307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:42:16.888383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:42:25.702849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:42:25.702883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:42:46.888339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:43:16.888363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:43:25.711635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:43:25.711677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:43:46.888334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:44:16.888353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:44:25.719753 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:44:25.719796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:44:46.888324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:45:16.888328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:45:25.726914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:45:25.726945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:45:46.888373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:46:16.888394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:46:25.734184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:46:25.734213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:46:46.888365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:47:16.888419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:47:25.741893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:47:25.741923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:47:46.888425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:48:16.888392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:48:25.751898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:48:25.751958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:48:46.888374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:49:16.888362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:49:25.761284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:49:25.761313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:49:46.888344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:50:16.888315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:50:25.770145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:50:25.770176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:50:46.888384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:51:16.888360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:51:25.778700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:51:25.778741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:51:46.888361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:52:16.888361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:52:25.787176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:52:25.787205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:52:46.888396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:53:16.888365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:53:25.794652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:53:25.794690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:53:46.888373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:54:16.888347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:54:25.801994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:54:25.802029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:54:46.888312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:55:16.888389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:55:25.811775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:55:25.811811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:55:46.888349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:56:16.888353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:56:25.819342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:56:25.819374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:56:46.888347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:57:16.888367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:57:25.826584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:57:25.826611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:57:46.888373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:58:16.888354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:58:25.833269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:58:25.833309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:58:46.888371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:59:16.888318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 04:59:25.841267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:59:25.841297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 04:59:46.888386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:00:16.888306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:00:25.847552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:00:25.847583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:00:46.888380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:01:16.888337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:01:25.855192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:01:25.855221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:01:46.888339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:02:16.888382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:02:25.862893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:02:25.862951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:02:46.888337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:03:16.888369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:03:25.873804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:03:25.873831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:03:46.888340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:04:16.888330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:04:25.880325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:04:25.880354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:04:46.888336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:05:16.888367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:05:25.887869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:05:25.887905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:05:46.888327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:06:16.888329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:06:25.895456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:06:25.895495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:06:46.888316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:07:16.888364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:07:25.902607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:07:25.902646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:07:46.888371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:08:16.888315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:08:25.910326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:08:25.910367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:08:46.888341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:09:16.888322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:09:25.917820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:09:25.917861 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:09:46.888322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:10:16.888357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:10:25.924378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:10:25.924439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:10:46.888390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:11:16.888366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:11:25.932363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:11:25.932388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:11:46.888296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:12:16.888379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:12:25.938667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:12:25.938699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:12:46.888344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:13:16.888340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:13:25.947154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:13:25.947189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:13:46.888345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:14:16.888347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:14:25.955013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:14:25.955043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:14:46.888327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:15:16.888364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:15:25.962827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:15:25.962860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:15:46.888294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:16:16.888370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:16:25.970738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:16:25.970776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:16:46.888375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:17:16.888328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:17:25.979599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:17:25.979628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:17:46.888347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:18:16.888396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:18:25.986042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:18:25.986074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:18:46.888352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:19:16.888376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:19:25.994175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:19:25.994202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:19:46.888373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:20:16.888358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:20:26.001117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:20:26.001148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:20:46.888361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:21:16.888343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:21:26.009541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:21:26.009570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:21:46.888348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:22:16.888349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:22:26.017593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:22:26.017625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:22:46.888432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:23:16.888382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:23:26.024774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:23:26.024803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:23:46.888378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:24:16.888368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:24:26.031493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:24:26.031531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:24:46.888379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:25:16.888386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:25:26.039357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:25:26.039396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:25:46.888326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:26:16.888354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:26:26.047702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:26:26.047735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:26:46.888331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:27:16.888371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:27:26.056983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:27:26.057012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:27:46.888336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:28:16.888405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:28:26.064376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:28:26.064423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:28:46.888371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:29:16.888361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:29:26.071497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:29:26.071532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:29:46.888327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:30:16.888386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:30:26.079268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:30:26.079307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:30:46.888334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:31:16.888382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:31:26.087558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:31:26.087592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:31:46.888311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:32:16.888352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:32:26.095482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:32:26.095535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:32:46.888392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:33:16.888374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:33:26.104401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:33:26.104426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:33:46.888346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:34:16.888317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:34:26.111263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:34:26.111290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:34:46.888369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:35:16.888364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:35:26.118036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:35:26.118066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:35:46.888402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:36:16.888391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:36:26.125612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:36:26.125648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:36:46.888342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:37:16.888324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:37:26.133166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:37:26.133252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:37:46.888348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:38:16.888331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:38:26.140946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:38:26.140977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:38:46.888375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:39:16.888354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:39:26.147812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:39:26.147842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:39:46.888429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:40:16.888304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:40:26.154413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:40:26.154445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:40:46.888351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:41:16.888360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:41:26.162137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:41:26.162169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:41:46.888322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:42:16.888313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:42:26.170367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:42:26.170402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:42:46.888338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:43:16.888342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:43:26.178956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:43:26.178987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:43:46.888356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:44:16.888337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:44:26.188005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:44:26.188037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:44:46.888347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:45:16.888340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:45:26.195391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:45:26.195424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:45:46.888340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:46:16.888314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:46:26.202679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:46:26.202702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:46:46.888360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:47:16.888324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:47:26.209886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:47:26.209919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:47:46.888480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:48:16.888303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:48:26.217446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:48:26.217471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:48:46.888317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:49:16.888353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:49:26.226062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:49:26.226086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:49:46.888350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:50:16.888394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:50:26.233600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:50:26.233635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:50:46.888334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:51:16.888413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:51:26.242352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:51:26.242393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:51:46.888334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:52:16.888360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:52:26.249431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:52:26.249478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:52:46.888351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:53:16.888348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:53:26.256102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:53:26.256131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:53:46.888296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:54:16.888335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:54:26.263668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:54:26.263693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:54:46.888242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:55:16.888364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:55:26.272150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:55:26.272181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:55:46.888351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:56:16.888374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:56:26.279254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:56:26.279296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:56:46.888377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:57:16.888370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:57:26.286909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:57:26.286943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:57:46.888350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:58:16.888358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:58:26.293727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:58:26.293755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:58:46.888304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:59:16.888389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 05:59:26.302551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:59:26.302581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 05:59:46.888351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:00:16.888370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/22 06:00:26.310118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/22 06:00:26.310150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host