By type
2022/03/13 03:04:15.623264 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/13 03:04:15.623412 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/13 03:04:15.623453 metrics.go:23: INFO Metrics logging every 30s
2022/03/13 03:04:15.623619 logstash.go:90: INFO Max Retries set to: 3
2022/03/13 03:04:15.623750 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/13 03:04:15.625459 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-kn7fv
2022/03/13 03:04:15.625903 async.go:63: INFO Flush Interval set to: 1s
2022/03/13 03:04:15.625944 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/13 03:04:15.626841 beat.go:221: INFO filebeat start running.
2022/03/13 03:04:15.627037 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/13 03:04:15.634802 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/13 03:04:15.634940 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/13 03:04:15.635078 crawler.go:38: INFO Loading Prospectors: 1
2022/03/13 03:04:15.635216 sync.go:41: INFO Start sending events to output
2022/03/13 03:04:15.635254 registrar.go:236: INFO Starting Registrar
2022/03/13 03:04:15.635561 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/13 03:04:15.635664 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/13 03:04:15.636111 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/13 03:04:15.636262 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/13 03:04:35.641599 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/13 03:04:35.643379 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/13 03:04:35.643544 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/13 03:04:35.643576 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/13 03:04:35.643559 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/13 03:04:40.670848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:40.670901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:41.679044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:41.679089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:43.690332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:43.690366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:45.623933 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=76 registrar.writes=1
2022/03/13 03:04:47.698129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:47.698164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:55.705340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:55.705407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:11.732371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:11.732433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:15.623970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:05:43.750821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:43.750858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:45.624166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:06:15.623807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:06:43.770727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:06:43.770790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:06:45.623890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:07:15.623881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:07:43.789774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:07:43.789804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:07:45.623803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:08:15.623806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:08:43.815491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:08:43.815535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:08:45.623788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:09:15.623819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:09:40.665688 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:09:43.833588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:09:43.833645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:09:45.623776 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/13 03:10:15.623768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:10:43.852543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:10:43.852593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:10:45.623775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:11:15.623923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:11:43.871910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:11:43.871987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:11:45.625529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:12:15.623831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:12:43.889644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:12:43.889694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:12:45.623785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:13:15.623805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:13:43.908575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:13:43.908615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:13:45.623731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:14:15.623818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:14:43.926187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:14:43.926224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:14:45.624016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:15:15.624208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:15:43.945013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:15:43.945149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:15:45.623842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:16:15.623798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:16:43.963949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:16:43.964003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:16:45.623748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:17:15.623793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:17:43.983836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:17:43.983890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:17:45.623801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:18:15.623775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:18:44.010180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:18:44.010226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:18:45.623870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:19:15.626345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:19:44.030226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:19:44.030269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:19:45.625687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:15.623777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:44.050410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:20:44.050467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:20:45.623832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:15.623844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:44.066150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:21:44.066190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:21:45.623763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:15.623765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:44.084037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:22:44.084085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:22:45.623855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:15.623840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:44.102261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:23:44.102309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:23:45.623814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:24:15.623771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:24:44.121659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:24:44.121697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:24:45.623733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:15.623770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:44.142239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:25:44.142278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:25:45.623797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:15.623826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:44.163071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:26:44.163124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:26:45.623817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:15.623802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:44.180782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:27:44.181203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:27:45.623743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:15.623773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:44.199682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:28:44.199718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:28:45.623743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:15.623730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:44.216873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:29:44.216910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:29:45.623742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:15.623750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:44.235478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:30:44.235521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:30:45.623852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:15.623778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:44.257040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:31:44.257084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:31:45.623841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:15.623784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:44.275333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:32:44.275376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:32:45.623788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:15.623785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:44.293261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:33:44.293297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:33:45.623796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:15.623777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:44.311159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:34:44.311205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:34:45.623854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:15.623856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:44.331178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:35:44.331221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:35:45.623783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:15.623738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:44.348741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:36:44.348779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:36:45.623766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:15.623826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:44.367086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:37:44.367139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:37:45.623759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:15.623791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:44.384365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:38:44.384520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:38:45.623970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:15.623832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:44.402322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:39:44.402369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:39:45.623848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:15.623729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:44.421605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:40:44.421649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:40:45.623746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:15.623707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:44.438725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:41:44.438871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:41:45.627453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:15.624008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:44.455842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:42:44.455892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:42:45.623731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:15.623789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:44.473222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:43:44.473292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:43:45.623835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:15.623736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:44.494594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:44:44.494642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:44:45.623784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:15.623717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:44.512760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:45:44.512815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:45:45.623894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:15.623806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:44.530871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:46:44.530931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:46:45.623688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:15.624156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:44.552043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:47:44.552110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:47:45.623790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:15.623834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:44.555338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:44.555373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:45.623756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:15.623707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:44.563328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:44.563362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:45.623827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:15.623744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:44.570269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:44.570314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:45.623942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:15.623781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:44.575982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:44.576043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:45.623913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:15.623976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:44.582876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:44.582914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:45.623838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:15.623768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:44.589259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:44.589298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:45.623811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:15.623751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:44.595572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:44.595753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:45.624058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:15.623764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:44.601628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:44.601663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:45.623739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:15.623815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:44.609278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:44.609322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:45.624051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:15.623791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:44.617180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:44.617247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:45.623851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:15.623832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:44.622731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:44.622774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:45.623740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:15.623814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:44.629218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:44.629259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:45.623844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:15.623765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:44.634402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:44.634450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:45.623888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:15.623817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:44.642976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:44.643011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:45.623743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:15.623866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:44.650493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:44.650537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:45.624468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:15.623779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:44.657103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:44.657142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:45.623744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:15.623795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:44.664835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:44.664894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:45.623802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:15.623736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:44.672523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:44.672566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:45.623778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:15.623907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:44.680614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:44.680648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:45.623798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:15.623791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:44.687346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:44.687382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:45.623784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:15.623732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:44.696025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:44.696107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:45.623822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:15.623786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:44.703775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:44.703833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:45.623831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:15.623752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:44.711723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:44.711760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:45.623809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:15.623777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:44.719128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:44.719163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:45.623755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:15.624240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:44.726656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:44.726694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:45.623760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:15.623787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:44.735649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:44.735717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:45.623798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:15.623705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:44.742918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:44.742963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:45.623772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:15.623790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:44.750362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:44.750446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:45.623889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:15.623884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:44.760529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:44.760599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:45.623806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:15.624535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:44.769316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:44.769371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:45.623792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:15.623810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:44.777684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:44.777728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:45.623768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:15.624010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:44.784213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:44.784551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:45.623806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:15.623786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:44.792446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:44.792513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:45.623785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:15.623809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:44.798799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:44.798836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:45.623735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:15.623796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:44.805860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:44.805898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:45.623823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:15.623818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:44.813160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:44.813217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:45.623732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:15.623737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:44.822816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:44.822894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:45.623814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:15.624590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:44.830915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:44.830948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:45.623795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:15.623844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:44.837739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:44.837781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:45.623737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:15.623848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:44.843939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:44.844080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:45.623820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:15.623738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:44.850918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:44.850974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:45.623896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:15.623783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:44.857911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:44.858278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:45.623815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:15.623803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:44.864741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:44.864776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:45.623897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:15.635393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:44.871503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:44.871541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:45.623764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:15.623716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:44.878241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:44.878291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:45.623797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:15.623799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:44.885417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:44.885449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:45.623782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:15.623736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:44.892150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:44.892201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:45.623811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:15.624058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:44.899510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:44.899550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:45.623785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:15.623791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:44.907005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:44.907064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:45.623932 metrics.go:34: INFO No non-zero metrics in the last 30s