2022/03/09 16:21:15.361963 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/09 16:21:15.362048 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 16:21:15.362120 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 16:21:15.362211 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 16:21:15.362321 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 16:21:15.362495 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-d6pv5
2022/03/09 16:21:15.362874 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 16:21:15.362900 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 16:21:15.363550 beat.go:221: INFO filebeat start running.
2022/03/09 16:21:15.363632 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 16:21:15.369649 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 16:21:15.369769 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 16:21:15.369830 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 16:21:15.370205 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 16:21:15.370377 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/09 16:21:15.370417 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 16:21:15.370495 registrar.go:236: INFO Starting Registrar
2022/03/09 16:21:15.370558 sync.go:41: INFO Start sending events to output
2022/03/09 16:21:15.370621 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 16:21:35.375122 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/09 16:21:35.376702 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/09 16:21:35.377106 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/09 16:21:35.377533 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/09 16:21:35.377820 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/09 16:21:40.393870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:40.394065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:41.403232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:41.403349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:43.410464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:43.410559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:45.366168 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=72 registrar.writes=1
2022/03/09 16:21:47.429289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:47.429360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:55.442696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:55.442776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:11.484099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:11.484208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:15.362595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:22:43.506237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:43.506289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:45.362467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:23:15.362621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:23:43.523615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:23:43.523650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:23:45.362572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:24:15.362492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:24:43.543801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:24:43.543860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:24:45.362524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:25:15.362527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:25:43.565771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:25:43.565834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:25:45.362605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:26:15.362471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:26:40.400671 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:43.586535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:26:43.586585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:26:45.362883 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/09 16:27:15.364069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:27:43.605843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:27:43.605895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:27:45.362394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:28:15.362486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:28:43.627800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:28:43.627863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:28:45.362505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:29:15.362635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:29:43.648067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:29:43.648161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:29:45.362449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:30:15.362523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:30:43.665354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:30:43.665404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:30:45.362454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:31:15.362432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:31:43.683303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:31:43.683353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:31:45.362531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:32:15.362487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:32:43.703490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:32:43.703566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:32:45.363240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:33:15.362480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:33:43.723142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:33:43.723187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:33:45.362495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:34:15.362424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:34:43.742602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:34:43.742661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:34:45.362411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:35:15.362595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:35:43.762069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:35:43.762132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:35:45.365950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:36:15.362529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:36:43.786153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:36:43.786206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:36:45.362502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:37:15.362526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:37:43.807075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:37:43.807134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:37:45.362604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:15.362407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:43.827208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:38:43.827255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:38:45.362472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:15.362463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:43.849446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:39:43.849491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:39:45.362492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:15.362547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:43.869911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:40:43.870219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:40:45.362664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:15.362553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:43.889262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:41:43.889310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:41:45.362422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:42:15.362472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:42:43.908188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:42:43.908237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:42:45.362632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:15.362432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:43.927630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:43:43.927680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:43:45.363246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:15.362543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:43.954755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:44:43.954794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:44:45.362466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:15.362424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:43.971113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:45:43.971169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:45:45.362434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:15.362974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:43.988803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:46:43.988849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:46:45.362553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:15.362573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:44.012986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:47:44.013050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:47:45.362558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:15.362618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:44.031441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:48:44.031496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:48:45.362571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:15.362523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:44.054559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:49:44.054639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:49:45.362433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:15.362474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:44.083295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:50:44.083519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:50:45.362873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:15.364047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:44.104966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:51:44.105043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:51:45.362443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:15.362497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:44.123941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:52:44.124008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:52:45.362423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:15.362414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:44.143402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:53:44.143452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:53:45.362485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:15.362459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:44.162875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:54:44.162929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:54:45.362468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:15.362651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:44.186071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:55:44.186137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:55:45.362539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:15.362698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:44.205236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:56:44.205284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:56:45.362532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:15.362900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:44.242480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:57:44.242699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:57:45.362524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:15.362473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:44.259019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:58:44.259056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:58:45.363601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:15.362524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:44.275178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:59:44.275214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:59:45.362437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:15.362499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:44.293306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:00:44.293365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:00:45.362428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:01:15.362414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:01:44.314425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:01:44.314466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:01:45.362466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:02:15.362427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:02:44.333269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:02:44.333315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:02:45.362383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:03:15.362466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:03:44.354011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:03:44.354065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:03:45.362504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:04:15.362493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:04:44.372603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:04:44.372677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:04:45.362482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:05:15.362491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:05:44.391803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:05:44.391840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:05:45.362469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:06:15.362389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:06:44.411135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:06:44.411187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:06:45.362437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:07:15.362506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:07:44.416902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:07:44.416966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:07:45.362440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:08:15.362412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:08:44.425107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:08:44.425146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:08:45.362479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:09:15.362404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:09:44.431789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:09:44.431830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:09:45.362541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:10:15.362781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:10:44.437738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:10:44.437772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:10:45.362510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:11:15.362435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:11:44.442940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:11:44.442973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:11:45.362537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:12:15.362568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:12:44.449232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:12:44.449363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:12:45.362378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:13:15.362431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:13:44.457358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:13:44.457414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:13:45.362499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:14:15.362468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:14:44.463146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:14:44.463194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:14:45.362428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:15:15.362480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:15:44.468841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:15:44.468892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:15:45.362416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:16:15.362458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:16:44.475129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:16:44.475162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:16:45.362531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:17:15.362454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:17:44.484332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:17:44.484374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:17:45.362456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:18:15.362455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:18:44.491134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:18:44.491170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:18:45.362543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:19:15.362428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:19:44.497378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:19:44.497415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:19:45.362403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:20:15.362596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:20:44.503139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:20:44.503180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:20:45.362501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:21:15.362393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:21:44.508728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:21:44.508769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:21:45.362445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:22:15.362469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:22:44.516160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:22:44.516200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:22:45.362922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:23:15.362434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:23:44.521689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:23:44.521723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:23:45.362436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:24:15.362437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:24:44.526802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:24:44.526844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:24:45.362475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:25:15.362426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:25:44.533235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:25:44.533271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:25:45.362552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:26:15.362509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:26:44.539745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:26:44.539777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:26:45.362373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:27:15.362451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:27:44.546711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:27:44.546781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:27:45.362492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:28:15.362588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:28:44.552759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:28:44.552794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:28:45.362457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:29:15.362483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:29:44.560294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:29:44.560351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:29:45.362441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:30:15.362485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:30:44.568632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:30:44.568682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:30:45.368490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:31:15.362472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:31:44.574899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:31:44.575049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:31:45.362454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:32:15.362467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:32:44.584160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:32:44.584208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:32:45.362484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:33:15.362458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:33:44.591152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:33:44.591279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:33:45.362470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:34:15.362472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:34:44.597623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:34:44.597677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:34:45.362438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:35:15.362425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:35:44.605783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:35:44.605823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:35:45.362475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:36:15.362392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:36:44.613351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:36:44.613391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:36:45.362487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:37:15.362593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:37:44.618382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:37:44.618416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:37:45.362455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:38:15.362633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:38:44.624946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:38:44.625001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:38:45.362480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:39:15.362430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:39:44.632470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:39:44.632503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:39:45.362492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:40:15.362396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:40:44.640037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:40:44.640071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:40:45.362379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:41:15.362532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:41:44.647844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:41:44.647884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:41:45.362477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:42:15.362465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:42:44.655144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:42:44.655184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:42:45.362432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:43:15.362478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:43:44.662341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:43:44.662574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:43:45.362435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:44:15.362405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:44:44.670821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:44:44.670868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:44:45.362425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:45:15.362667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:45:44.677830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:45:44.677873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:45:45.362549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:46:15.362531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:46:44.690678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:46:44.690763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:46:45.362611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:47:15.362430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:47:44.697000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:47:44.697064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:47:45.362370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:48:15.362438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:48:44.705382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:48:44.705433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:48:45.362402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:49:15.362428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:49:44.712813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:49:44.712863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:49:45.362451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:50:15.362504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:50:44.720091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:50:44.720136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:50:45.362482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:51:15.362553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:51:44.727076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:51:44.727114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:51:45.362476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:52:15.362467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:52:44.734512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:52:44.735558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:52:45.362454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:53:15.362499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:53:44.742128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:53:44.742182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:53:45.362530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:54:15.362490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:54:44.754447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:54:44.754491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:54:45.362471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:55:15.362556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:55:44.761957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:55:44.761994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:55:45.362635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:56:15.362418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:56:44.769244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:56:44.769306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:56:45.362387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:57:15.362529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:57:44.775561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:57:44.775643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:57:45.362447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:58:15.362377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:58:44.783376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:58:44.783418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:58:45.362405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:59:15.362495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:59:44.794466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:59:44.794499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:59:45.362438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:00:15.362446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:00:44.801751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:00:44.801800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:00:45.362446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:01:15.362402 metrics.go:34: INFO No non-zero metrics in the last 30s