Results

By type

          2022/01/15 03:17:14.236585 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/01/15 03:17:14.236632 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/15 03:17:14.236699 logstash.go:90: INFO Max Retries set to: 3
2022/01/15 03:17:14.236756 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/15 03:17:14.236825 metrics.go:23: INFO Metrics logging every 30s
2022/01/15 03:17:14.236908 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-x6kll
2022/01/15 03:17:14.237097 async.go:63: INFO Flush Interval set to: 1s
2022/01/15 03:17:14.237113 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/15 03:17:14.237583 beat.go:221: INFO filebeat start running.
2022/01/15 03:17:14.237701 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/15 03:17:14.622836 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/15 03:17:14.622945 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/15 03:17:14.623061 registrar.go:236: INFO Starting Registrar
2022/01/15 03:17:14.623155 sync.go:41: INFO Start sending events to output
2022/01/15 03:17:14.623007 crawler.go:38: INFO Loading Prospectors: 1
2022/01/15 03:17:14.623394 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/15 03:17:14.623627 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/15 03:17:14.623845 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/15 03:17:14.623962 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/15 03:17:14.625182 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/15 03:17:14.625366 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/15 03:17:14.625493 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/15 03:17:14.625723 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/15 03:17:14.625800 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/15 03:17:14.672682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:14.672717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:15.677253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:15.677297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:17.682837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:17.682916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:21.695048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:21.695389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:29.707565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:29.707617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:44.237317 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=2043 registrar.writes=1
2022/01/15 03:17:45.718230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:17:45.718313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:18:14.237344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:18:17.722787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:18:17.722840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:18:44.237458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:19:14.237305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:19:17.727071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:19:17.727123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:19:44.237367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:20:14.237205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:20:17.730572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:20:17.730615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:20:44.237204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:21:14.237246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:21:17.735042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:21:17.735084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:21:44.237452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:22:14.237507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:22:17.739786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:22:17.739834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:22:19.637775 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/15 03:22:44.237318 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/15 03:23:14.237354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:23:17.744253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:23:17.744289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:23:44.237227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:24:14.237267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:24:17.748746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:24:17.748929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:24:44.237221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:25:14.237163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:25:17.758300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:25:17.758335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:25:44.237081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:26:14.237377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:26:17.762339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:26:17.762414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:26:44.237152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:27:14.237169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:27:17.771283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:27:17.771323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:27:44.237282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:28:14.237278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:28:17.774320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:28:17.774362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:28:44.237214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:29:14.237271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:29:17.781982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:29:17.782123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:29:44.237205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:30:14.237200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:30:17.785959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:30:17.786000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:30:44.237237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:31:14.237240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:31:17.792223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:31:17.792277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:31:44.237238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:32:14.237168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:32:17.796521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:32:17.796568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:32:44.237216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:33:14.237186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:33:17.808020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:33:17.808052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:33:44.237244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:34:14.237250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:34:17.812596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:34:17.812642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:34:44.237291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:35:14.237281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:35:17.821070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:35:17.821109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:35:44.237234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:36:14.237286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:36:17.825248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:36:17.825314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:36:44.237148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:37:14.237170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:37:17.837073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:37:17.837112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:37:44.237263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:38:14.237320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:38:17.841614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:38:17.841669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:38:44.237227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:39:14.237208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:39:17.848590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:39:17.848633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:39:44.237093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:40:14.237335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:40:17.852925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:40:17.852978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:40:44.237260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:41:14.237349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:41:17.859937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:41:17.859981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:41:44.237352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:42:14.237299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:42:17.863519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:42:17.863546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:42:44.237204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:43:14.237239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:43:17.870450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:43:17.870481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:43:44.237251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:44:14.237267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:44:17.874576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:44:17.874621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:44:44.237252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:45:14.237456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:45:17.881539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:45:17.881687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:45:44.237260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:46:14.237177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:46:17.885370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:46:17.885406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:46:44.237297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:47:14.237262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:47:17.891526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:47:17.891563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:47:44.237181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:48:14.237277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:48:17.895451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:48:17.895493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:48:44.237108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:49:14.237186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:49:17.906312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:49:17.906368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:49:44.237241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:50:14.237379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:50:17.915359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:50:17.915404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:50:44.237264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:51:14.237246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:51:17.929148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:51:17.929469 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:51:44.237422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:52:14.237595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:52:17.937879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:52:17.937911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:52:44.237219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:53:14.237225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:53:17.951684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:53:17.951720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:53:44.237350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:54:14.237300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:54:17.961598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:54:17.961649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:54:44.237304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:55:14.237204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:55:17.972585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:55:17.972634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:55:44.237166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:56:14.237202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:56:17.981901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:56:17.981976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:56:44.237180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:57:14.237298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:57:17.992621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:57:17.992675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:57:44.237198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:58:14.237357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:58:18.001081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:58:18.001126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:58:44.237180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:59:14.237218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 03:59:18.010566 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:59:18.010744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 03:59:44.237247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:00:14.237209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:00:18.020493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:00:18.020539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:00:44.237315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:01:14.237161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:01:18.034005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:01:18.034036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:01:44.237174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:02:14.237274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:02:18.044451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:02:18.044516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:02:44.237288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:03:14.237330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:03:18.059488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:03:18.059536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:03:44.237226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:04:14.237264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:04:18.068825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:04:18.068875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:04:44.237258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:05:14.237271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:05:18.079636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:05:18.079670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:05:44.237310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:06:14.237173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:06:18.087280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:06:18.087317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:06:44.237143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:07:14.237301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:07:18.100238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:07:18.100281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:07:44.237167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:08:14.237309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:08:18.109572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:08:18.109626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:08:44.237214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:09:14.237208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:09:18.122756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:09:18.122798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:09:44.237220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:10:14.237334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:10:18.133647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:10:18.133692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:10:44.237380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:11:14.237336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:11:18.145410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:11:18.145453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:11:44.237253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:12:14.237262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:12:18.154932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:12:18.154965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:12:44.237269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:13:14.237238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:13:18.167722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:13:18.167754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:13:44.237299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:14:14.237267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:14:18.176771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:14:18.176853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:14:44.237260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:15:14.237265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:15:18.185770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:15:18.185803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:15:44.237309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:16:14.237261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:16:18.193687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:16:18.193731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:16:44.237362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:17:14.237235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:17:18.207419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:17:18.207451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:17:44.237239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:18:14.237187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:18:18.217553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:18:18.217611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:18:44.237201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:19:14.237332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:19:18.231125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:19:18.231165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:19:44.237246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:20:14.237366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:20:18.241981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:20:18.242040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:20:44.237130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:21:14.237228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:21:18.252098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:21:18.252145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:21:44.237458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:22:14.237434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:22:18.263780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:22:18.263831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:22:44.237342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:23:14.237414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:23:18.278086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:23:18.278144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:23:44.237268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:24:14.237271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:24:18.288475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:24:18.288518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:24:44.237285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:25:14.237325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:25:18.300758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:25:18.300795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:25:44.237321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:26:14.237283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:26:18.311269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:26:18.311340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:26:44.237201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:27:14.237245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:27:18.322059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:27:18.322123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:27:44.237169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:28:14.237178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:28:18.332398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:28:18.332443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:28:44.237290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:29:14.237242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:29:18.345287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:29:18.345322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:29:44.237265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:30:14.237445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:30:18.355535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:30:18.355572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:30:44.237276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:31:14.237195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:31:18.367545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:31:18.367586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:31:44.237119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:32:14.237215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:32:18.378026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:32:18.378075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:32:44.237318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:33:14.237231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:33:18.389469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:33:18.389514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:33:44.237263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:34:14.237197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:34:18.398673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:34:18.398732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:34:44.237217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:35:14.237307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:35:18.409809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:35:18.409870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:35:44.237314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:36:14.237213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:36:18.419279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:36:18.419363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:36:44.237198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:37:14.237312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:37:18.432538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:37:18.432580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:37:44.237317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:38:14.237147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:38:18.442140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:38:18.442186 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:38:44.237199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:39:14.237261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:39:18.455928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:39:18.455955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:39:44.237342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:40:14.237368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:40:18.465861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:40:18.465933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:40:44.237313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:41:14.237179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:41:18.480780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:41:18.480838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:41:44.237180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:42:14.237247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:42:18.490773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:42:18.490838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:42:44.237293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:43:14.237277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:43:18.501850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:43:18.501882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:43:44.237399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:44:14.237168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:44:18.510539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:44:18.510574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:44:44.237248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:45:14.238289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:45:18.525048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:45:18.525112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:45:44.237275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:46:14.237126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:46:18.534693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:46:18.534750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:46:44.237201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:47:14.237173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:47:18.547527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:47:18.547724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:47:44.237280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:48:14.237183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:48:18.558596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:48:18.558641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:48:44.237220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:49:14.237249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:49:18.571895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:49:18.571934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:49:44.237281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:50:14.237186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:50:18.585507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:50:18.585549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:50:44.237252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:51:14.237131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:51:18.594409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:51:18.594436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:51:44.237215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:52:14.237307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:52:18.605557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:52:18.605607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:52:44.237284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:53:14.237376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:53:18.619105 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:53:18.619153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:53:44.237273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:54:14.237286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:54:18.629471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:54:18.629525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:54:44.237203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:55:14.237227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:55:18.642954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:55:18.643031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:55:44.237241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:56:14.237412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:56:18.672162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:56:18.672206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:56:44.237280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:57:14.237238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:57:18.683497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:57:18.683532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:57:44.237373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:58:14.237177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:58:18.694403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:58:18.694457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:58:44.237208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:59:14.237285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 04:59:18.703994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:59:18.704148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 04:59:44.237309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:00:14.237176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:00:18.713353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:00:18.713399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:00:44.237185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:01:14.237226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:01:18.726939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:01:18.727030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:01:44.237295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:02:14.237236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:02:18.736404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:02:18.736442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:02:44.237184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:03:14.237246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:03:18.747700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:03:18.747730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:03:44.237296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:04:14.237195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:04:18.757792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:04:18.757930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:04:44.237238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:05:14.237176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:05:18.769196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:05:18.769233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:05:44.237249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:06:14.237257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:06:18.778270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:06:18.778292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:06:44.237164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:07:14.237233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:07:18.788125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:07:18.788165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:07:44.237276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:08:14.237259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:08:18.798538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:08:18.798589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:08:44.237294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:09:14.237282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:09:18.808666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:09:18.808697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:09:44.237281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:10:14.237327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:10:18.818871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:10:18.818917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:10:44.237296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:11:14.237114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:11:18.830734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:11:18.830795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:11:44.237271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:12:14.237992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:12:18.840851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:12:18.840900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:12:44.237343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:13:14.237266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:13:18.856280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:13:18.856328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:13:44.237382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:14:14.237182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:14:18.866351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:14:18.866398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:14:44.237322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:15:14.237212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:15:18.879453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:15:18.879486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:15:44.237315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:16:14.237313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:16:18.893266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:16:18.893315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:16:44.237354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:17:14.237250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:17:18.903394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:17:18.903442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:17:44.237300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:18:14.237206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:18:18.912717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:18:18.912750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:18:44.237359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:19:14.237194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:19:18.924036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:19:18.924072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:19:44.237733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:20:14.237291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:20:18.933260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:20:18.933316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:20:44.237272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:21:14.237251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:21:18.943232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:21:18.943303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:21:44.237304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:22:14.237206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/15 05:22:18.952145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/15 05:22:18.952210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host