2022/03/31 03:06:28.486139 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/31 03:06:28.486202 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/31 03:06:28.486307 logstash.go:90: INFO Max Retries set to: 3
2022/03/31 03:06:28.486401 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/31 03:06:28.486533 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-nswf5
2022/03/31 03:06:28.486771 async.go:63: INFO Flush Interval set to: 1s
2022/03/31 03:06:28.486796 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/31 03:06:28.487290 beat.go:221: INFO filebeat start running.
2022/03/31 03:06:28.487396 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/31 03:06:28.488891 metrics.go:23: INFO Metrics logging every 30s
2022/03/31 03:06:28.492223 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/31 03:06:28.492310 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/31 03:06:28.492355 crawler.go:38: INFO Loading Prospectors: 1
2022/03/31 03:06:28.492581 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/31 03:06:28.492718 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/31 03:06:28.492762 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/31 03:06:28.492838 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/31 03:06:28.492862 registrar.go:236: INFO Starting Registrar
2022/03/31 03:06:28.492881 sync.go:41: INFO Start sending events to output
2022/03/31 03:06:48.495020 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/31 03:06:48.495449 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/31 03:06:48.495819 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/31 03:06:48.496050 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/31 03:06:48.496112 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/31 03:06:48.518617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:48.518653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:49.522878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:49.522935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:51.529520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:51.529568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:55.535749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:55.535797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:58.489359 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/31 03:07:03.543984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:03.544023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:19.574795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:19.574830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:28.489228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:07:51.593032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:51.593069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:58.489355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:08:28.489308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:08:51.613291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:08:51.613347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:08:58.489209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:09:28.489206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:09:51.633813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:09:51.633851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:09:58.489215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:10:28.489167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:10:51.653643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:10:51.653695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:10:58.489206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:11:28.489224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:11:51.672030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:11:51.672076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:11:53.510893 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/31 03:11:58.489292 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/31 03:12:28.489335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:12:51.690762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:12:51.690817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:12:58.489196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:13:28.489320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:13:51.709443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:13:51.709487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:13:58.489198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:14:28.489147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:14:51.731403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:14:51.731441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:14:58.489242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:15:28.489214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:15:51.749839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:15:51.749895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:15:58.489193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:16:28.489157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:16:51.771511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:16:51.771545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:16:58.489255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:17:28.489211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:17:51.790939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:17:51.790979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:17:58.489393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:18:28.489207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:18:51.808881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:18:51.808918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:18:58.489321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:19:28.489138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:19:51.826815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:19:51.826996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:19:58.489214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:20:28.489210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:20:51.845247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:20:51.845284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:20:58.489161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:21:28.489221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:21:51.866839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:21:51.866876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:21:58.489164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:22:28.489351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:22:51.885972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:22:51.886030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:22:58.489311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:23:28.489242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:23:51.904724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:23:51.904775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:23:58.489219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:24:28.489203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:24:51.922515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:24:51.922563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:24:58.489218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:25:28.489170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:25:51.941054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:25:51.941094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:25:58.489229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:26:28.489229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:26:51.959429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:26:51.959464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:26:58.489188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:27:28.489220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:27:51.978378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:27:51.978528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:27:58.489194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:28:28.489232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:28:52.000106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:28:52.000166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:28:58.489342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:29:28.489278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:29:52.017212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:29:52.017338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:29:58.489216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:30:28.489173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:30:52.035400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:30:52.035434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:30:58.489184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:31:28.489187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:31:52.056500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:31:52.056545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:31:58.489185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:32:28.489207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:32:52.074474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:32:52.074523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:32:58.489231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:33:28.489225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:33:52.094344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:33:52.094491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:33:58.489250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:34:28.489178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:34:52.114505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:34:52.114691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:34:58.489233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:35:28.489278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:35:52.133912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:35:52.134063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:35:58.489228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:36:28.489247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:36:52.153651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:36:52.153689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:36:58.489201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:37:28.489207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:37:52.172307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:37:52.172455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:37:58.489193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:38:28.489309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:38:52.191416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:38:52.191450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:38:58.489199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:39:28.489201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:39:52.210857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:39:52.210901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:39:58.489173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:40:28.489194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:40:52.229768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:40:52.229806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:40:58.489186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:41:28.489215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:41:52.247070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:41:52.247112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:41:58.489207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:42:28.489349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:42:52.263913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:42:52.263962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:42:58.489217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:43:28.489566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:43:52.280963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:43:52.281015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:43:58.489211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:44:28.489234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:44:52.300665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:44:52.300972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:44:58.489229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:45:28.489211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:45:52.324837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:45:52.324874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:45:58.489274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:46:28.489483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:46:52.344850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:46:52.344906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:46:58.489245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:47:28.489238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:47:52.362191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:47:52.362239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:47:58.489162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:48:28.489178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:48:52.386880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:48:52.386934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:48:58.489150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:49:28.489351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:49:52.406252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:49:52.406293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:49:58.489179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:50:28.489220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:50:52.425950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:50:52.426013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:50:58.489358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:51:28.489315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:51:52.445588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:51:52.445626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:51:58.489224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:52:28.489183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:52:52.452943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:52.452979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:52:58.489204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:53:28.489220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:53:52.471836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:53:52.471877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:53:58.489288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:54:28.489200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:54:52.489873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:54:52.489920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:54:58.489203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:55:28.489199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:55:52.506201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:55:52.506238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:55:58.489264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:56:28.489377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:56:52.528654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:56:52.528693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:56:58.489205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:57:28.489325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:57:52.548337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:57:52.548388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:57:58.489256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:58:28.489282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:58:52.566574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:58:52.566608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:58:58.489236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:59:28.489217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:59:52.585352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:59:52.585415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:59:58.489212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:00:28.489253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:00:52.604149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:00:52.604201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:00:58.489335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:01:28.489170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:01:52.623127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:01:52.623160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:01:58.489174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:02:28.489252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:02:52.643813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:02:52.643857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:02:58.489268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:03:28.489258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:03:52.662942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:03:52.662975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:03:58.489181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:04:28.489172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:04:52.681691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:04:52.681773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:04:58.489226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:05:28.489431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:05:52.703286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:05:52.703679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:05:58.489187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:06:28.489165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:06:52.723288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:06:52.723329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:06:58.489287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:07:28.489216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:07:52.741663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:07:52.741697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:07:58.489156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:08:28.489232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:08:52.760557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:08:52.760604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:08:58.489173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:09:28.489238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:09:52.778638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:09:52.778683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:09:58.489223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:10:28.489253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:10:52.796832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:10:52.796864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:10:58.489189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:11:28.489247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:11:52.815310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:11:52.815345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:11:58.489483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:12:28.489434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:12:52.832498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:12:52.832574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:12:58.489249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:13:28.489242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:13:52.853780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:13:52.853821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:13:58.489193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:14:28.489293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:14:52.872576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:14:52.872613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:14:58.489203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:15:28.489249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:15:52.891716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:15:52.891775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:15:58.489222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:16:28.489147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:16:52.908852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:16:52.908988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:16:58.489251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:17:28.489226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:17:52.928345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:17:52.928384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:17:58.489324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:18:28.489165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:18:52.950295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:18:52.950332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:18:58.489198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:19:28.489548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:19:52.970454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:19:52.970493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:19:58.489307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:20:28.489263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:20:53.000406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:20:53.000568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:20:58.489198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:21:28.489321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:21:53.019003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:21:53.019045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:21:58.489168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:22:28.489189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:22:53.035283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:22:53.035333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:22:58.489149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:23:28.489217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:23:53.053886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:23:53.053927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:23:58.489240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:24:28.489161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:24:53.072456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:24:53.072512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:24:58.489197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:25:28.489253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:25:53.091687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:25:53.091722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:25:58.489162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:26:28.489262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:26:53.113917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:26:53.113988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:26:58.489143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:27:28.489305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:27:53.137636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:27:53.137685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:27:58.489464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:28:28.489249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:28:53.154337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:28:53.154398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:28:58.489207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:29:28.489208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:29:53.174159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:29:53.174237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:29:58.489158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:30:28.489173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:30:53.195364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:30:53.195405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:30:58.489236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:31:28.489171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 04:31:53.216256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:31:53.216346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 04:31:58.489191 metrics.go:34: INFO No non-zero metrics in the last 30s