By type
2022/03/20 03:24:13.351252 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/20 03:24:13.351360 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/20 03:24:13.352134 metrics.go:23: INFO Metrics logging every 30s
2022/03/20 03:24:13.363309 logstash.go:90: INFO Max Retries set to: 3
2022/03/20 03:24:13.363606 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/20 03:24:13.363882 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-dhsjs
2022/03/20 03:24:13.364302 async.go:63: INFO Flush Interval set to: 1s
2022/03/20 03:24:13.364335 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/20 03:24:13.367094 beat.go:221: INFO filebeat start running.
2022/03/20 03:24:13.367227 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/20 03:24:13.405154 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/20 03:24:13.405294 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/20 03:24:13.405383 crawler.go:38: INFO Loading Prospectors: 1
2022/03/20 03:24:13.405770 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/20 03:24:13.405961 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/20 03:24:13.405990 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/20 03:24:13.406020 registrar.go:236: INFO Starting Registrar
2022/03/20 03:24:13.406095 sync.go:41: INFO Start sending events to output
2022/03/20 03:24:13.406278 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/20 03:24:43.352812 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/20 03:24:43.417838 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/20 03:24:43.418156 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/20 03:24:43.418253 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/20 03:24:43.418413 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/20 03:24:43.418484 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/20 03:24:43.451409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:43.451487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:44.504020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:44.504071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:46.517219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:46.517596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:50.562297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:50.562356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:58.616802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:58.616864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:25:13.352735 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=49
2022/03/20 03:25:14.727567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:25:14.727644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:25:43.353390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:25:46.755848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:25:46.755920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:26:13.352737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:26:43.353180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:26:46.821789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:26:46.821849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:27:13.353139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:27:43.352727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:27:46.945868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:27:46.945938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:28:13.352976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:28:43.352821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:28:47.045842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:28:47.046623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:29:13.352881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:29:43.352742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:29:47.080058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:29:47.080130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:29:48.476873 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/20 03:30:03.597698 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/20 03:30:03.597846 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/20 03:30:03.597919 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/20 03:30:13.353753 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-4
2022/03/20 03:30:43.352649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:30:47.132856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:30:47.132926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:31:13.352749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:31:43.352744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:31:47.181840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:31:47.182189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:32:13.365465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:32:43.353517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:32:47.231965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:32:47.232047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:33:13.353087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:33:43.353167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:33:47.258740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:33:47.258792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:34:13.353207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:34:43.352633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:34:47.285560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:34:47.285615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:35:13.352962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:35:43.352666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:35:47.402991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:35:47.403042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:36:13.353162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:36:43.354191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:36:47.438650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:36:47.438712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:37:13.352999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:37:43.352594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:37:47.469757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:37:47.469804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:38:13.352870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:38:43.353716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:38:47.506364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:38:47.506458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:39:13.353221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:39:43.353290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:39:47.541508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:39:47.541587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:40:13.356886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:40:43.355262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:40:47.581831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:40:47.581897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:41:13.354432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:41:43.352859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:41:47.608514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:41:47.608558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:42:13.358897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:42:43.353339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:42:47.703969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:42:47.704070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:43:13.352801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:43:43.354747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:43:47.740256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:43:47.740321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:44:13.362812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:44:43.377494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:44:47.845703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:44:47.845774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:45:13.372765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:45:43.361234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:45:47.939308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:45:47.939385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:46:13.358889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:46:43.353094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:46:48.063172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:46:48.063235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:47:13.365925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:47:43.356650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:47:48.157957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:47:48.158022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:48:13.354428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:48:43.355398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:48:48.236718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:48:48.236787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:49:13.361825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:49:43.353044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:49:48.267924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:49:48.268011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:50:13.352705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:50:43.352737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:50:48.295723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:50:48.295789 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:51:13.353015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:51:43.352780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:51:48.319791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:51:48.319934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:52:13.352617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:52:43.352780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:52:48.345363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:52:48.345420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:53:13.355684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:53:43.352671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:53:48.368952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:53:48.369015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:54:13.353180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:54:43.352686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:54:48.405592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:54:48.406039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:55:13.352975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:55:43.377807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:55:48.432897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:55:48.432968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:56:13.352702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:56:43.352749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:56:48.478724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:56:48.478781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:57:13.356819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:57:43.352730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:57:48.505229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:57:48.505281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:58:13.352659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:58:43.352662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:58:48.528781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:58:48.528840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:59:13.352508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:59:43.352674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:59:48.607572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:59:48.607682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:00:13.355059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:00:43.352798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:00:48.672165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:00:48.672227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:01:13.354060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:01:43.352619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:01:48.697590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:01:48.697653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:02:13.352570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:02:43.352742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:02:48.726186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:02:48.726239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:03:13.352772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:03:43.353086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:03:48.756212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:03:48.756281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:04:13.353460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:04:43.352784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:04:48.782777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:04:48.782852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:05:13.352778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:05:43.352793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:05:48.837351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:05:48.842679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:06:13.355111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:06:43.352644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:06:48.888555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:06:48.888634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:07:13.352796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:07:43.352735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:07:48.926360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:07:48.926818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:08:13.353907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:08:43.352630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:08:48.956309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:08:48.956696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:09:13.352864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:09:43.352684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:09:48.991342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:09:48.991460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:10:13.353048 metrics.go:34: INFO No non-zero metrics in the last 30s