By type
2022/04/17 03:15:16.084173 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/04/17 03:15:16.084260 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/17 03:15:16.084303 metrics.go:23: INFO Metrics logging every 30s
2022/04/17 03:15:16.084428 logstash.go:90: INFO Max Retries set to: 3
2022/04/17 03:15:16.084610 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/17 03:15:16.084815 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-8dstz
2022/04/17 03:15:16.085145 async.go:63: INFO Flush Interval set to: 1s
2022/04/17 03:15:16.085179 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/17 03:15:16.086025 beat.go:221: INFO filebeat start running.
2022/04/17 03:15:16.086174 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/17 03:15:16.093473 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/17 03:15:16.093595 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/17 03:15:16.093656 crawler.go:38: INFO Loading Prospectors: 1
2022/04/17 03:15:16.094027 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/17 03:15:16.094209 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/17 03:15:16.094249 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/17 03:15:16.094275 registrar.go:236: INFO Starting Registrar
2022/04/17 03:15:16.094326 sync.go:41: INFO Start sending events to output
2022/04/17 03:15:16.094380 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/17 03:15:36.097326 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/17 03:15:36.097505 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/17 03:15:36.097602 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/17 03:15:36.097869 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/17 03:15:36.097965 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/17 03:15:41.121621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:41.121675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:42.125549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:42.125607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:44.129604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:44.129648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:46.086111 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=70 registrar.writes=1
2022/04/17 03:15:48.148109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:48.148170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:56.158597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:56.158658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:12.184926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:12.185114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:16.085434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:16:44.208416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:44.208460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:46.084628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:17:16.084747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:17:44.226623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:17:44.226664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:17:46.084778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:18:16.084724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:18:44.244962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:18:44.245013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:18:46.084673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:19:16.084689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:19:44.264479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:19:44.264537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:19:46.084674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:20:16.084725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:20:41.113322 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/17 03:20:44.288755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:20:44.288811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:20:46.084700 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/17 03:21:16.084825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:21:44.308038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:21:44.308082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:21:46.084575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:22:16.084684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:22:44.327996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:22:44.328063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:22:46.084727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:23:16.084696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:23:44.353066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:23:44.353143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:23:46.084740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:24:16.084675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:24:44.372801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:24:44.372865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:24:46.084660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:25:16.084820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:25:44.393596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:25:44.393653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:25:46.087037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:26:16.085770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:26:44.413036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:26:44.413081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:26:46.084837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:27:16.084692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:27:44.432157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:27:44.432201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:27:46.084732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:28:16.084721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:28:44.453363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:28:44.453424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:28:46.084926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:29:16.084633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:29:44.472125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:29:44.472189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:29:46.084675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:30:16.084871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:30:44.494543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:30:44.494587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:30:46.084649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:31:16.084732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:31:44.514080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:31:44.514616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:31:46.084593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:32:16.084634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:32:44.537440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:32:44.537504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:32:46.084660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:33:16.084676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:33:44.555747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:33:44.555802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:33:46.084730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:34:16.084753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:34:44.576871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:34:44.576932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:34:46.084773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:35:16.084759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:35:44.598579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:35:44.598642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:35:46.084901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:36:16.084668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:36:44.617623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:36:44.617676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:36:46.084678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:37:16.084576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:37:44.637274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:37:44.637467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:37:46.084741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:38:16.085019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:38:44.657363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:38:44.657402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:38:46.084714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:39:16.084697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:39:44.675153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:39:44.675213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:39:46.084815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:40:16.084600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:40:44.699280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:40:44.699329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:40:46.084669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:41:16.084668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:41:44.718663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:41:44.718724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:41:46.084746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:42:16.084738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:42:44.738511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:42:44.738545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:42:46.084791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:43:16.085015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:43:44.755503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:43:44.755559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:43:46.084660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:44:16.084967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:44:44.774011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:44:44.774064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:44:46.084790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:45:16.084800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:45:44.792778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:45:44.792835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:45:46.084609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:46:16.084661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:46:44.812041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:46:44.812083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:46:46.084614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:47:16.084826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:47:44.831823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:47:44.831891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:47:46.084667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:48:16.084690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:48:44.851982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:48:44.852034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:48:46.084701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:49:16.084691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:49:44.872225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:49:44.872267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:49:46.084743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:50:16.084695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:50:44.889761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:50:44.889800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:50:46.084609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:51:16.084714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:51:44.907667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:51:44.907709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:51:46.084590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:52:16.084678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:52:44.928298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:52:44.928342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:52:46.084702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:53:16.084657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:53:44.946752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:53:44.946991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:53:46.084790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:54:16.085094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:54:44.965097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:54:44.965156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:54:46.084653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:55:16.084779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:55:44.985916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:55:44.985973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:55:46.084696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:56:16.084782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:56:45.004346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:56:45.004380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:56:46.084785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:57:16.085022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:57:45.024255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:57:45.024468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:57:46.084837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:58:16.084753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:58:45.042774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:58:45.043006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:58:46.084636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:59:16.084731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:59:45.060043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:59:45.060085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:59:46.084631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:00:16.084763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:00:45.083468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:00:45.083541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:00:46.084808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:01:16.084623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:01:45.100973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:01:45.101013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:01:46.084589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:02:16.085346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:02:45.121468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:02:45.121512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:02:46.084635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:03:16.084787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:03:45.140501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:03:45.140544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:03:46.084701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:04:16.084730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:04:45.159494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:04:45.159557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:04:46.084735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:05:16.084664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:05:45.178426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:05:45.178483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:05:46.084566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:06:16.084726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:06:45.196214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:06:45.196265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:06:46.084743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:07:16.084847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:07:45.219896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:07:45.219968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:07:46.084587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:08:16.084647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:08:45.238328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:08:45.238404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:08:46.084722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:09:16.084907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:09:45.257222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:09:45.257383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:09:46.084780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:10:16.084679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:10:45.275122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:10:45.275284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:10:46.084652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:11:16.084806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:11:45.293443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:11:45.293597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:11:46.084692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:12:16.084614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:12:45.312564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:12:45.312625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:12:46.084556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:13:16.084694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:13:45.329176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:13:45.329219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:13:46.084796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:14:16.084771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:14:45.352270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:14:45.352311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:14:46.084913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:15:16.084680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:15:45.375523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:15:45.375572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:15:46.084689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:16:16.084620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:16:45.395965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:16:45.396093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:16:46.084579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:17:16.084749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:17:45.414345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:17:45.414408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:17:46.084677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:18:16.084723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:18:45.432915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:18:45.433062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:18:46.084665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:19:16.084806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:19:45.453008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:19:45.453066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:19:46.084708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:20:16.084872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:20:45.473045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:20:45.473120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:20:46.084897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:21:16.084679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:21:45.491859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:21:45.491911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:21:46.084756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:22:16.084639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:22:45.510937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:22:45.511096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:22:46.084623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:23:16.084683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:23:45.517978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:23:45.518036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:23:46.084675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:24:16.084626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:24:45.525285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:24:45.525456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:24:46.084682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:25:16.084693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:25:45.534027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:25:45.534077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:25:46.084776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:26:16.084698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:26:45.541940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:26:45.541991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:26:46.084599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:27:16.084686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:27:45.548657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:27:45.548709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:27:46.084724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:28:16.084651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:28:45.555998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:28:45.556042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:28:46.084963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:29:16.084726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:29:45.562581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:29:45.562635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:29:46.084821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:30:16.084646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:30:45.569311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:30:45.569360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:30:46.084720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:31:16.084915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:31:45.576746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:31:45.576790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:31:46.084654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:32:16.084635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:32:45.583305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:32:45.583346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:32:46.084634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:33:16.084787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:33:45.589686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:33:45.589776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:33:46.084674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:34:16.084592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:34:45.596882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:34:45.596924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:34:46.084637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:35:16.084787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:35:45.602805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:35:45.602835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:35:46.085858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:36:16.084814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:36:45.610333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:36:45.610370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:36:46.084699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:37:16.084683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:37:45.617624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:37:45.617662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:37:46.084661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:38:16.084716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:38:45.624828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:38:45.624953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:38:46.084955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:39:16.084680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:39:45.631920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:39:45.631966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:39:46.084703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:40:16.084637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:40:45.640230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:40:45.640273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:40:46.084825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:41:16.084575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:41:45.647530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:41:45.647601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:41:46.085027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:42:16.084956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:42:45.654660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:42:45.654698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:42:46.084675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:43:16.084699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:43:45.661086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:43:45.661144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:43:46.084681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:44:16.084712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:44:45.669698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:44:45.669756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:44:46.084638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:45:16.084667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:45:45.676496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:45:45.676550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:45:46.084738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:46:16.084615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:46:45.687300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:46:45.687352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:46:46.084735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:47:16.084674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:47:45.698038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:47:45.698080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:47:46.084753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:48:16.084677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:48:45.704582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:48:45.704737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:48:46.084672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:49:16.084598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:49:45.711255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:49:45.711305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:49:46.084680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:50:16.084700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:50:45.718064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:50:45.718123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:50:46.084731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:51:16.085305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:51:45.724811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:51:45.724848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:51:46.084785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:52:16.084642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:52:45.733111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:52:45.733172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:52:46.084664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:53:16.084751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:53:45.741295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:53:45.741370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:53:46.084753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:54:16.084720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:54:45.747923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:54:45.747967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:54:46.086339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:55:16.084771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:55:45.756184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:55:45.756349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:55:46.084787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:56:16.084992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:56:45.764437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:56:45.764478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:56:46.084641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:57:16.084779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:57:45.772996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:57:45.773059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:57:46.084780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:58:16.085618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:58:45.780499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:58:45.780676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:58:46.084691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:59:16.084847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:59:45.789350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:59:45.789402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:59:46.084733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:00:16.084655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:00:45.795672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:00:45.795828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:00:46.084676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:01:16.084788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:01:45.804193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:01:45.804239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:01:46.086294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:02:16.084759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:02:45.812540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:02:45.812578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:02:46.084709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:03:16.084656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:03:45.819153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:03:45.819317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:03:46.084787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:04:16.084742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:04:45.826332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:04:45.826369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:04:46.084665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:05:16.084794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:05:45.834314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:05:45.834401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:05:46.084767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:06:16.084768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:06:45.841529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:06:45.841577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:06:46.084740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:07:16.084779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:07:45.850525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:07:45.850579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:07:46.084724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:08:16.084832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:08:45.858925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:08:45.858962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:08:46.084750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:09:16.084786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:09:45.867496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:09:45.867588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:09:46.084779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:10:16.084769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:10:45.875349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:10:45.875429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:10:46.084793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:11:16.084715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:11:45.887063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:11:45.887122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:11:46.084803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:12:16.084646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:12:45.895171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:12:45.895209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:12:46.084898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:13:16.084723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:13:45.907819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:13:45.907879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:13:46.084816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:14:16.084709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:14:45.915735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:14:45.915873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:14:46.084810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:15:16.084757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:15:45.922249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:15:45.922305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:15:46.084940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:16:16.084708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:16:45.930896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:16:45.931095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:16:46.084877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:17:16.084733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:17:45.941333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:17:45.941373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:17:46.084939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:18:16.084816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:18:45.949350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:18:45.949502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:18:46.084690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:19:16.084893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:19:45.957445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:19:45.957495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:19:46.084800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:20:16.084596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 05:20:45.970347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:20:45.970402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 05:20:46.084672 metrics.go:34: INFO No non-zero metrics in the last 30s