Results

By type

          2022/04/09 03:10:37.853610 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/04/09 03:10:37.853778 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/09 03:10:37.853784 metrics.go:23: INFO Metrics logging every 30s
2022/04/09 03:10:37.854062 logstash.go:90: INFO Max Retries set to: 3
2022/04/09 03:10:37.854262 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/09 03:10:37.854535 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-plbm6
2022/04/09 03:10:37.854832 async.go:63: INFO Flush Interval set to: 1s
2022/04/09 03:10:37.854897 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/09 03:10:37.855504 beat.go:221: INFO filebeat start running.
2022/04/09 03:10:37.855690 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/09 03:10:37.861011 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/09 03:10:37.861189 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/09 03:10:37.861282 crawler.go:38: INFO Loading Prospectors: 1
2022/04/09 03:10:37.861636 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/09 03:10:37.861819 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/09 03:10:37.862020 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/09 03:10:37.862115 registrar.go:236: INFO Starting Registrar
2022/04/09 03:10:37.862237 sync.go:41: INFO Start sending events to output
2022/04/09 03:10:37.862412 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/09 03:10:57.865980 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/09 03:10:57.866123 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/09 03:10:57.866323 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/09 03:10:57.866606 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/09 03:10:57.866785 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/09 03:11:02.885095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:02.885127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:03.888400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:03.888444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:05.892282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:05.892314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:07.854767 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/04/09 03:11:09.899437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:09.899466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:17.906644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:17.906680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:33.925738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:33.925774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:11:37.854633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:12:05.944667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:12:05.944705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:12:07.854212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:12:37.854273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:13:05.961739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:13:05.961795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:13:07.854267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:13:37.854228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:14:05.979757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:14:05.979786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:14:07.854192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:14:37.854293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:15:05.996796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:15:05.996976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:15:07.854238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:15:37.854256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:16:02.876967 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/09 03:16:06.012860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:16:06.012912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:16:07.854319 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/09 03:16:37.854404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:17:06.029859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:17:06.029947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:17:07.854235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:17:37.854288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:18:06.046904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:18:06.046958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:18:07.854230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:18:37.854240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:19:06.064130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:19:06.064160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:19:07.854238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:19:37.854224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:20:06.081520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:20:06.081569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:20:07.854268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:20:37.854251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:21:06.097669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:21:06.097716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:21:07.854257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:21:37.854235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:22:06.114847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:22:06.114991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:22:07.854291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:22:37.854163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:23:06.132082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:23:06.132113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:23:07.854287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:23:37.854251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:24:06.152583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:24:06.152624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:24:07.854303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:24:37.854348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:25:06.170051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:25:06.170109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:25:07.854219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:25:37.854329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:26:06.191478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:26:06.191511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:26:07.854357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:26:37.854260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:27:06.210593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:27:06.210643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:27:07.854219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:27:37.854252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:28:06.228966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:28:06.228996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:28:07.854265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:28:37.854229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:29:06.245230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:29:06.245338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:29:07.854235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:29:37.854198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:30:06.261196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:30:06.261227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:30:07.854231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:30:37.854235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:31:06.278012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:31:06.278062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:31:07.854268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:31:37.854297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:32:06.294630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:32:06.294662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:32:07.854250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:32:37.854244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:33:06.310978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:33:06.311008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:33:07.854314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:33:37.854288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:34:06.328457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:34:06.328495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:34:07.854283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:34:37.854236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:35:06.344495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:35:06.344541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:35:07.854247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:35:37.854276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:36:06.362505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:36:06.362538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:36:07.854231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:36:37.854274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:37:06.378706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:37:06.378742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:37:07.854307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:37:37.854295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:38:06.403336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:38:06.403492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:38:07.854222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:38:37.854231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:39:06.420282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:39:06.420321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:39:07.854715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:39:37.854313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:40:06.438730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:40:06.438789 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:40:07.854254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:40:37.854290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:41:06.456269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:41:06.456315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:41:07.854286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:41:37.854220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:42:06.474567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:42:06.474606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:42:07.854336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:42:37.854393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:43:06.491436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:43:06.491472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:43:07.854341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:43:37.854282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:44:06.506537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:44:06.506567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:44:07.854263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:44:37.854302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:45:06.522907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:45:06.522949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:45:07.854257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:45:37.854200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:46:06.538785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:46:06.538818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:46:07.854215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:46:37.854348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:47:06.556349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:47:06.556381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:47:07.854233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:47:37.854490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:48:06.572628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:48:06.572672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:48:07.854240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:48:37.854251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:49:06.589979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:49:06.590019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:49:07.854361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:49:37.854240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:50:06.608391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:50:06.608421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:50:07.854187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:50:37.854280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:51:06.626260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:51:06.626306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:51:07.854230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:51:37.854280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:52:06.646228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:52:06.646266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:52:07.854190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:52:37.854250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:53:06.663997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:53:06.664032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:53:07.854240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:53:37.854273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:54:06.681027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:54:06.681067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:54:07.854213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:54:37.854189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:55:06.697409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:55:06.697636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:55:07.854310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:55:37.854272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:56:06.714626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:56:06.714668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:56:07.854292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:56:37.854327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:57:06.732024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:57:06.732064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:57:07.854416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:57:37.854266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:58:06.748245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:58:06.748281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:58:07.854198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:58:37.854264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:59:06.764024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:59:06.764072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 03:59:07.854158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 03:59:37.854254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:00:06.780485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:00:06.780516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:00:07.854237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:00:37.854304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:01:06.796560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:01:06.796590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:01:07.854229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:01:37.854284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:02:06.813253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:02:06.813696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:02:07.854240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:02:37.854264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:03:06.832115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:03:06.832175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:03:07.854270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:03:37.854273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:04:06.847891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:04:06.847926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:04:07.854254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:04:37.854296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:05:06.864889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:05:06.864918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:05:07.854234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:05:37.854543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:06:06.872338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:06:06.872391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:06:07.854332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:06:37.854248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:07:06.877349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:07:06.877381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:07:07.854368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:07:37.854257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:08:06.883068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:08:06.883106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:08:07.854239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:08:37.854278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:09:06.888332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:09:06.888366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:09:07.854330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:09:37.854329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:10:06.893901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:10:06.893935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:10:07.854261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:10:37.854280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:11:06.899946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:11:06.899980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:11:07.854304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:11:37.854236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:12:06.906044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:12:06.906081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:12:07.854258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:12:37.854210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:13:06.911224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:13:06.911261 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:13:07.854340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:13:37.854250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:14:06.916786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:14:06.916925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:14:07.854250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:14:37.854217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:15:06.923538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:15:06.923713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:15:07.854240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:15:37.854263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:16:06.930355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:16:06.930612 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:16:07.854269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:16:37.854246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:17:06.936648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:17:06.936676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:17:07.854330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:17:37.854236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:18:06.941975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:18:06.942015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:18:07.854198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:18:37.854187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:19:06.947475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:19:06.947519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:19:07.854234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:19:37.854252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:20:06.953263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:20:06.953297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:20:07.854266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:20:37.854229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:21:06.960357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:21:06.960411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:21:07.854261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:21:37.854273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:22:06.966075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:22:06.966113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:22:07.854250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:22:37.854268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:23:06.972034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:23:06.972059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:23:07.854236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:23:37.854243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:24:06.979419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:24:06.979455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:24:07.854201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:24:37.854473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:25:06.986602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:25:06.986648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:25:07.854252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:25:37.854309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:26:06.991857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:26:06.991887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:26:07.854289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:26:37.854287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:27:06.997263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:27:06.997306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:27:07.854227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:27:37.854265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:28:07.003270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:28:07.003310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:28:07.854398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:28:37.854251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:29:07.009612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:29:07.009643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:29:07.854241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:29:37.854234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:30:07.019497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:30:07.019528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:30:07.854331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:30:37.854164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:31:07.025205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:31:07.025253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:31:07.854228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:31:37.854201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:32:07.030535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:32:07.030585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:32:07.854201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:32:37.854375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:33:07.038083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:33:07.038148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:33:07.854362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:33:37.854282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:34:07.045646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:34:07.045678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:34:07.854249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:34:37.854319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:35:07.051314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:35:07.051353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:35:07.854215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:35:37.854211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:36:07.056600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:36:07.056633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:36:07.854291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:36:37.854228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:37:07.061840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:37:07.061885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:37:07.854306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:37:37.854294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:38:07.067960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:38:07.068091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:38:07.854196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:38:37.854199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:39:07.074014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:39:07.074056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:39:07.854287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:39:37.854280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:40:07.080241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:40:07.080279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:40:07.854240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:40:37.854241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:41:07.085739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:41:07.085769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:41:07.854202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:41:37.854230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:42:07.091806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:42:07.091839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:42:07.854290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:42:37.854368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:43:07.098622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:43:07.098667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:43:07.854374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:43:37.854253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:44:07.106325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:44:07.106361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:44:07.854233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:44:37.854313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:45:07.111523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:45:07.111558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:45:07.854158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:45:37.854348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:46:07.117089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:46:07.117130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:46:07.854256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:46:37.854295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:47:07.123150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:47:07.123194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/09 04:47:07.854209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/09 04:47:37.854225 metrics.go:34: INFO No non-zero metrics in the last 30s