2022/04/05 02:57:06.761593 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/05 02:57:06.761662 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/05 02:57:06.761712 metrics.go:23: INFO Metrics logging every 30s
2022/04/05 02:57:06.761789 logstash.go:90: INFO Max Retries set to: 3
2022/04/05 02:57:06.761882 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/05 02:57:06.762062 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-9pt8j
2022/04/05 02:57:06.762391 async.go:63: INFO Flush Interval set to: 1s
2022/04/05 02:57:06.762424 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/05 02:57:06.763044 beat.go:221: INFO filebeat start running.
2022/04/05 02:57:06.763114 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/05 02:57:06.767543 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/05 02:57:06.767624 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/05 02:57:06.767682 crawler.go:38: INFO Loading Prospectors: 1
2022/04/05 02:57:06.767749 sync.go:41: INFO Start sending events to output
2022/04/05 02:57:06.767901 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/05 02:57:06.768123 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/05 02:57:06.768162 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/05 02:57:06.768201 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/05 02:57:06.767865 registrar.go:236: INFO Starting Registrar
2022/04/05 02:57:26.770144 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/05 02:57:26.770318 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/05 02:57:26.770627 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/05 02:57:26.771090 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/05 02:57:26.771093 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/05 02:57:31.777963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:31.778003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:32.783014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:32.783154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:34.789246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:34.789298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:36.763886 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=72 registrar.writes=1
2022/04/05 02:57:38.794904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:38.794954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:46.808308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:46.808357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:02.814280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:02.814347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:06.762197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:58:34.822318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:34.822360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:36.762131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:59:06.762174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:59:34.835985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:59:34.836049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:59:36.762336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:00:06.762035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:00:34.842359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:00:34.842395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:00:36.762049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:01:06.762134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:01:34.847880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:01:34.847973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:01:36.762012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:02:06.761979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:02:31.790913 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:02:34.855984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:02:34.856025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:02:36.762128 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/05 03:03:06.762061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:03:34.862170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:03:34.862233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:03:36.762149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:04:06.762037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:04:34.868427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:04:34.868474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:04:36.762027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:05:06.762277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:05:34.875988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:05:34.876033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:05:36.762060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:06:06.762057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:06:34.882500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:06:34.882565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:06:36.762157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:07:06.762141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:07:34.888949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:07:34.888984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:07:36.762051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:08:06.762056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:08:34.894497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:08:34.894539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:08:36.762102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:09:06.762061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:09:34.901100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:09:34.901149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:09:36.762064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:10:06.761991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:10:34.936810 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:10:34.936846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:10:36.763000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:11:06.762020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:11:34.954901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:11:34.954977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:11:36.762234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:12:06.762177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:12:34.962060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:12:34.962238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:12:36.762025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:06.762183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:34.967898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:13:34.967952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:13:36.762006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:06.763329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:34.977703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:14:34.977752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:14:36.762120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:06.762006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:34.983267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:15:34.983316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:15:36.762019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:06.761979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:34.990006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:16:34.990059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:16:36.762081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:17:06.762241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:17:34.996143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:17:34.996206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:17:36.762249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:06.762874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:35.001816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:18:35.001855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:18:36.762054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:06.764177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:35.023902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:19:35.023992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:19:36.762044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:06.764199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:35.032193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:20:35.032356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:20:36.762174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:06.762118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:35.038279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:21:35.038335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:21:36.762030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:06.762123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:35.043876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:22:35.043909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:22:36.762087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:06.762135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:35.049686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:23:35.049732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:23:36.762090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:06.762162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:35.055389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:24:35.055429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:24:36.762042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:06.761999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:35.071427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:25:35.071653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:25:36.762107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:06.762065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:35.074971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:26:35.075196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:26:36.762140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:06.762501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:35.079019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:27:35.079193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:27:36.762076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:06.761984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:35.082971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:28:35.083007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:28:36.762127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:06.762208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:35.090501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:29:35.090573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:29:36.762161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:06.762067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:35.094412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:30:35.094446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:30:36.762077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:06.762084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:35.098855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:31:35.098896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:31:36.762078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:06.762213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:35.102549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:32:35.102583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:32:36.762053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:06.762022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:35.106123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:33:35.106159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:33:36.762101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:06.764314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:35.110074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:34:35.110128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:34:36.762638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:35:06.762070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:35:35.129254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:35:35.129295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:35:36.762148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:36:06.762076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:36:35.132528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:36:35.132575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:36:36.762118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:37:06.762004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:37:35.136440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:37:35.136476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:37:36.762044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:38:06.762574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:38:35.140399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:38:35.140596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:38:36.762061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:39:06.762047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:39:35.145020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:39:35.145392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:39:36.762416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:40:06.762186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:40:35.149362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:35.149412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:36.762236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:41:06.761990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:41:35.154605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:41:35.154644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:41:36.762139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:42:06.762026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:42:35.158814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:42:35.158903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:42:36.763799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:43:06.762004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:43:35.162495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:43:35.162535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:43:36.762050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:44:06.762060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:44:35.166447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:44:35.166491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:44:36.762017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:45:06.762163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:45:35.170202 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:45:35.170257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:45:36.762009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:46:06.762069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:46:35.173893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:46:35.173945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:46:36.762808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:47:06.762040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:47:35.177887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:47:35.177933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:47:36.762146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:48:06.761995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:48:35.181853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:48:35.181888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:48:36.762044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:49:06.762163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:49:35.186903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:49:35.186949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:49:36.762081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:50:06.762070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:50:35.189755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:50:35.189797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:50:36.762049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:51:06.762119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:51:35.194923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:51:35.194962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:51:36.762157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:52:06.762160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:52:35.198878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:52:35.198920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:52:36.762248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:53:06.762092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:53:35.203297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:53:35.203337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:53:36.762067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:54:06.762066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:54:35.207195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:54:35.207482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:54:36.762315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:55:06.762259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:55:35.211880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:55:35.211919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:55:36.762061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:56:06.764179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:56:35.229518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:56:35.229569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:56:36.762073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:57:06.762355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:57:35.233271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:57:35.233341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:57:36.762052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:58:06.770460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:58:35.237122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:58:35.237161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:58:36.762155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:59:06.762060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:59:35.242670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:59:35.242722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:59:36.762062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:00:06.762271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:00:35.246930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:00:35.246983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:00:36.762207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:01:06.762120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:01:35.250599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:01:35.250731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:01:36.762010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:02:06.768216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:02:35.253801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:02:35.253841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:02:36.762170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:03:06.762048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:03:35.258002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:03:35.258138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:03:36.762133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:04:06.763286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:04:35.261875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:04:35.261922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:04:36.762165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:05:06.762201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:05:35.265894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:05:35.265947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:05:36.762085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:06:06.762072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:06:35.269934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:06:35.270030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:06:36.762056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:07:06.762118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:07:35.273911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:07:35.273953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:07:36.762064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:08:06.762134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:08:35.277474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:08:35.277522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:08:36.762621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:09:06.762057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:09:35.281327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:09:35.281365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:09:36.762063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:10:06.762809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:10:35.284991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:10:35.285027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:10:36.762491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:11:06.762080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:11:35.288589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:11:35.288632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:11:36.763650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:12:06.762099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:12:35.292575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:12:35.292617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:12:36.762023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:13:06.763596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:13:35.298159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:13:35.298222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:13:36.762115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:14:06.762069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:14:35.302289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:14:35.302326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:14:36.761997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:15:06.762005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:15:35.306484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:15:35.306518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:15:36.762121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:16:06.762198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:16:35.309761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:16:35.309801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:16:36.762076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:17:06.762051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:17:35.312912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:17:35.313080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:17:36.762060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:18:06.761963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:18:35.326988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:18:35.327023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:18:36.762008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:19:06.762144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:19:35.337016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:19:35.337053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:19:36.762041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:20:06.762049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:20:35.340188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:20:35.340236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:20:36.762081 metrics.go:34: INFO No non-zero metrics in the last 30s