By type
2022/03/06 03:10:26.722567 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/06 03:10:26.722735 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/06 03:10:26.722624 metrics.go:23: INFO Metrics logging every 30s
2022/03/06 03:10:26.722903 logstash.go:90: INFO Max Retries set to: 3
2022/03/06 03:10:26.722989 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/06 03:10:26.723141 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-wgtmm
2022/03/06 03:10:26.723396 async.go:63: INFO Flush Interval set to: 1s
2022/03/06 03:10:26.723414 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/06 03:10:26.723939 beat.go:221: INFO filebeat start running.
2022/03/06 03:10:26.724009 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/06 03:10:26.728352 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/06 03:10:26.728411 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/06 03:10:26.728443 crawler.go:38: INFO Loading Prospectors: 1
2022/03/06 03:10:26.728547 registrar.go:236: INFO Starting Registrar
2022/03/06 03:10:26.728622 sync.go:41: INFO Start sending events to output
2022/03/06 03:10:26.728661 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/06 03:10:26.728754 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/06 03:10:26.728782 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/06 03:10:26.728813 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/06 03:10:46.731492 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/06 03:10:46.731692 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/06 03:10:46.731990 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/06 03:10:46.732072 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/06 03:10:46.732138 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/06 03:10:51.765147 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:10:51.765238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:10:52.768370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:10:52.768413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:10:54.773348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:10:54.773379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:10:56.723330 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=76 registrar.writes=1
2022/03/06 03:10:58.785826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:10:58.785860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:11:06.791898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:11:06.791969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:11:22.811722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:11:22.811812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:11:26.723583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:11:54.831974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:11:54.832040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:11:56.723282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:12:26.723273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:12:54.850572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:12:54.850655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:12:56.723414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:13:26.723198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:13:54.869705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:13:54.869850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:13:56.723286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:14:26.723215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:14:54.887840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:14:54.887882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:14:56.723202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:15:26.723369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:15:51.750872 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/06 03:15:54.906400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:15:54.906452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:15:56.723855 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/06 03:16:26.723170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:16:54.925776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:16:54.925826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:16:56.723213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:17:26.723187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:17:54.944800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:54.944923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:56.723544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:18:26.723347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:18:54.967136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:18:54.967230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:18:56.723415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:19:26.723174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:19:54.988729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:19:54.988768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:19:56.723272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:20:26.723266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:20:55.008984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:20:55.009018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:20:56.723160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:21:26.723315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:21:55.028398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:21:55.028457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:21:56.723245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:22:26.723202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:22:55.046239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:22:55.046312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:22:56.723297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:23:26.723313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:23:55.066942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:23:55.066984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:23:56.723203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:24:26.723281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:24:55.086060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:24:55.086113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:24:56.723194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:25:26.723341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:25:55.105388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:25:55.105426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:25:56.723313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:26:26.723297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:26:55.123560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:26:55.123610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:26:56.723242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:27:26.723268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:27:55.141690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:27:55.141735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:27:56.723235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:28:26.723189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:28:55.161036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:28:55.161069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:28:56.723129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:29:26.723251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:29:55.181037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:29:55.181103 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:29:56.723175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:30:26.723386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:30:55.198778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:30:55.198824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:30:56.723242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:31:26.723204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:31:55.215875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:31:55.215921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:31:56.723206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:32:26.723369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:32:55.234864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:32:55.234900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:32:56.723303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:33:26.723202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:33:55.253193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:33:55.253252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:33:56.723126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:34:26.723248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:34:55.274706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:34:55.274757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:34:56.723240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:35:26.723183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:35:55.302991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:35:55.303046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:35:56.723187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:36:26.723279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:36:55.322308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:36:55.322359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:36:56.723317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:37:26.723260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:37:55.341108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:37:55.341171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:37:56.723266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:38:26.723151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:38:55.359860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:38:55.359993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:38:56.723153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:39:26.723181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:39:55.378463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:39:55.378496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:39:56.723234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:40:26.723380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:40:55.398059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:40:55.398100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:40:56.723182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:41:26.723265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:41:55.416123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:41:55.416164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:41:56.723234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:42:26.723194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:42:55.434615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:42:55.434649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:42:56.723197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:43:26.723185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:43:55.456917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:43:55.456974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:43:56.723237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:44:26.723272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:44:55.474395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:44:55.474440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:44:56.723284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:45:26.723271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:45:55.493820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:45:55.493900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:45:56.723248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:46:26.723327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:46:55.513057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:46:55.513089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:46:56.723180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:47:26.723232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:47:55.531074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:47:55.531119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:47:56.723144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:48:26.723243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:48:55.549495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:48:55.549620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:48:56.723263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:49:26.723268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:49:55.568627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:49:55.568667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:49:56.723273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:50:26.723252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:50:55.586730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:50:55.586767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:50:56.723238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:51:26.723233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:51:55.605208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:51:55.605250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:51:56.723241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:52:26.723233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:52:55.623104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:52:55.623147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:52:56.723212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:53:26.723234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:53:55.642536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:53:55.642585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:53:56.723317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:54:26.723250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:54:55.661548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:54:55.661585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:54:56.723167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:55:26.723219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:55:55.683864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:55:55.683913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:55:56.723255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:56:26.723215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:56:55.703548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:56:55.703594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:56:56.723216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:57:26.723160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:57:55.721449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:57:55.721483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:57:56.723159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:58:26.723192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:58:55.740363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:58:55.740412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:58:56.723190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:59:26.723224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:59:55.759476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:59:55.759702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:59:56.723455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:00:26.723293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:00:55.781233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:00:55.781297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:00:56.723254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:01:26.723208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:01:55.799393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:01:55.799431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:01:56.723237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:02:26.723171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:02:55.817246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:02:55.817288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:02:56.723187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:03:26.723364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:03:55.835179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:03:55.835236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:03:56.723318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:04:26.723685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:04:55.851986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:04:55.852164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:04:56.723210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:05:26.723247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:05:55.870595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:05:55.870635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:05:56.723222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:06:26.723226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:06:55.889792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:06:55.889845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:06:56.723208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:07:26.723202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:07:55.907192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:07:55.907240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:07:56.723180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:08:26.723327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:08:55.926605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:08:55.926776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:08:56.723251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:09:26.723270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:09:55.947324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:09:55.947384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:09:56.723256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:10:26.723265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:10:55.965903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:10:55.965941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:10:56.723155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:11:26.723244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:11:55.985195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:11:55.985233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:11:56.723260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:12:26.723237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:12:56.004448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:12:56.004537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:12:56.723283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:13:26.723343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:13:56.024521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:13:56.024555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:13:56.723517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:14:26.723235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:14:56.045978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:14:56.046038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:14:56.724074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:15:26.723223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:15:56.064270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:15:56.064324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:15:56.723191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:16:26.723417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:16:56.070357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:16:56.070394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:16:56.723424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:17:26.723247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:17:56.090650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:17:56.090691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:17:56.723251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:18:26.723199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:18:56.109987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:18:56.110370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:18:56.723215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:19:26.723141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:19:56.130337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:19:56.130416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:19:56.723234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:20:26.723243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:20:56.150242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:20:56.150506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:20:56.723175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:21:26.723151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:21:56.170682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:21:56.170825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:21:56.723237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:22:26.723357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:22:56.189974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:22:56.190021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:22:56.723173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:23:26.723181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:23:56.209058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:23:56.209097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:23:56.723200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:24:26.723183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:24:56.228646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:24:56.228709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:24:56.723244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:25:26.723171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:25:56.247664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:25:56.247714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:25:56.723204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:26:26.723269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:26:56.264771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:26:56.264815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:26:56.723221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:27:26.723255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:27:56.284637 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:27:56.284717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:27:56.723316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:28:26.723230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:28:56.302836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:28:56.302885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:28:56.723258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:29:26.723221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:29:56.319406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:29:56.319553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:29:56.723212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:30:26.723327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:30:56.338675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:30:56.338719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:30:56.723348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:31:26.723225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:31:56.360523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:31:56.360729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:31:56.723206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:32:26.723125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:32:56.383731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:32:56.383766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:32:56.723227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:33:26.723192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:33:56.403186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:33:56.403220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:33:56.723152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:34:26.724630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:34:56.419453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:34:56.419490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:34:56.723214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:35:26.723319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:35:56.438959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:35:56.439003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:35:56.723219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:36:26.723234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:36:56.458070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:36:56.458106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:36:56.723169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:37:26.723252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:37:56.477094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:37:56.477141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:37:56.723301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:38:26.723231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:38:56.495455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:38:56.495510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:38:56.723225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:39:26.723216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:39:56.514751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:39:56.514783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:39:56.723203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:40:26.723183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:40:56.534159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:40:56.534205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:40:56.723240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:41:26.723215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:41:56.552824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:41:56.552913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:41:56.723181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:42:26.723239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:42:56.577496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:42:56.577545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:42:56.723207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:43:26.723208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:43:56.595798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:43:56.595865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:43:56.723256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:44:26.723139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:44:56.614823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:44:56.614891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:44:56.723225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:45:26.723199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:45:56.633463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:45:56.633509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:45:56.723204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:46:26.723131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:46:56.653839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:46:56.653876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:46:56.723282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:47:26.723252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:47:56.672945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:47:56.672995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:47:56.723364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:48:26.723234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:48:56.691020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:48:56.691080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:48:56.723206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:49:26.723331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:49:56.710192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:49:56.710242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:49:56.723143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:50:26.723157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:50:56.723119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:50:56.729250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:50:56.729276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:51:26.723216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:51:56.723188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:51:56.748195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:51:56.748224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:52:26.723441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:52:56.723266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:52:56.765933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:52:56.765974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:53:26.723255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:53:56.723267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:53:56.785014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:53:56.785057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:54:26.723186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:54:56.723199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:54:56.803825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:54:56.803864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:55:26.723253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:55:56.724081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:55:56.824016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:55:56.824064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:56:26.723204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:56:56.723171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:56:56.842285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:56:56.842330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:57:26.723270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:57:56.723184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:57:56.861633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:57:56.861692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:58:26.723259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:58:56.723204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:58:56.880702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:58:56.880736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:59:26.723274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:59:56.723523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:59:56.900500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:59:56.900572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:00:26.723268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:00:56.723362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:00:56.917709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:00:56.917835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:01:26.723166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:01:56.723194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:01:56.936903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:01:56.936984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:02:26.723251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:02:56.723222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:02:56.956298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:02:56.956346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:03:26.723190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:03:56.723137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:03:56.975072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:03:56.975107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:04:26.723264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:04:56.723189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:04:56.993156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:04:56.993194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host