2022/03/19 03:41:47.692457 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/19 03:41:47.692564 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/19 03:41:47.692663 metrics.go:23: INFO Metrics logging every 30s
2022/03/19 03:41:47.692861 logstash.go:90: INFO Max Retries set to: 3
2022/03/19 03:41:47.693017 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/19 03:41:47.693248 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-cb47d
2022/03/19 03:41:47.693676 async.go:63: INFO Flush Interval set to: 1s
2022/03/19 03:41:47.693719 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/19 03:41:47.694553 beat.go:221: INFO filebeat start running.
2022/03/19 03:41:47.694762 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/19 03:41:47.704189 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/19 03:41:47.704330 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/19 03:41:47.704419 crawler.go:38: INFO Loading Prospectors: 1
2022/03/19 03:41:47.704658 registrar.go:236: INFO Starting Registrar
2022/03/19 03:41:47.704650 sync.go:41: INFO Start sending events to output
2022/03/19 03:41:47.704924 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/19 03:41:47.705108 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/19 03:41:47.705146 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/19 03:41:47.705185 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/19 03:42:17.697322 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/19 03:42:17.712612 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/19 03:42:17.712855 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/19 03:42:17.713120 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/19 03:42:17.713287 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/19 03:42:17.713435 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/19 03:42:17.757647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:17.757715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:18.764075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:18.764115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:20.790634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:20.790682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:24.831284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:24.831535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:32.844253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:32.844314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:47.693464 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=62
2022/03/19 03:42:48.856329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:48.856405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:43:17.694999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:43:20.864033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:43:20.864075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:43:47.693113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:44:17.694256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:44:20.878887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:44:20.878928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:44:47.694064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:45:17.693754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:45:20.895248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:45:20.895309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:45:47.693274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:46:17.693151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:46:20.916471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:46:20.916531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:46:47.693112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:47:17.693266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:47:20.924851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:47:20.924916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:47:22.740655 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/19 03:47:22.740949 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/19 03:47:22.741210 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/19 03:47:23.795872 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/19 03:47:47.693195 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/19 03:47:47.762628 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/19 03:48:17.693151 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/19 03:48:20.930845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:48:20.930900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:48:47.693417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:49:17.694272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:49:20.940290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:49:20.940340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:49:47.693172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:50:17.694553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:50:20.945586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:50:20.945627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:50:47.695840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:51:17.694550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:51:20.973197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:51:20.973280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:51:47.695709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:52:17.693341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:52:20.982590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:52:20.982684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:52:47.693287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:53:17.693472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:53:21.005112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:53:21.005218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:53:47.693175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:54:17.693336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:54:21.013489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:54:21.020981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:54:47.698063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:55:17.693653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:55:21.028324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:55:21.028368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:55:47.693454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:56:17.694148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:56:21.035125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:56:21.035180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:56:47.693627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:57:17.693400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:57:21.045125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:57:21.045194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:57:47.695135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:58:17.694922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:58:21.064439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:58:21.064538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:58:47.693157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:59:17.700944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:59:21.086704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:59:21.086762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:59:47.696269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:00:17.694479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:00:21.121678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:00:21.121753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:00:47.693992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:01:17.693275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:01:21.161463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:01:21.161694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:01:47.694152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:02:17.703954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:02:21.224421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:02:21.224476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:02:47.693109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:03:17.693102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:03:21.280419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:03:21.281057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:03:47.695192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:04:17.704667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:04:21.313857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:04:21.313915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:04:47.693230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:05:17.693167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:05:21.366953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:05:21.367012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:05:47.693891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:06:17.695750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:06:21.407841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:06:21.407909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:06:47.694426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:07:17.693438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:07:21.426144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:07:21.426205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:07:47.693173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:08:17.694489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:08:21.475922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:08:21.475980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:08:47.693330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:09:17.698809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:09:21.506974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:09:21.507025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:09:47.693706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:10:17.693751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:10:21.553659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:10:21.553729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:10:47.703125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:11:17.701284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:11:21.574040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:11:21.574096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:11:47.716174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:12:17.703572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:12:21.609996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:12:21.610061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:12:47.693112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:13:17.695073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:13:21.695706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:13:21.695766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:13:47.693218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:14:17.693310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:14:21.775481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:14:21.775563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:14:47.693081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:15:17.693093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:15:21.820646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:15:21.820732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:15:47.693597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:16:17.711157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:16:21.890185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:16:21.890321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:16:47.693314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:17:17.695374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:17:21.913927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:17:21.913991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:17:47.693197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:18:17.693807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:18:21.950761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:18:21.950810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:18:47.693382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:19:17.693883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:19:21.967000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:19:21.967056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:19:47.693536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:20:17.697185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:20:21.997220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:20:21.997275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:20:47.693173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:21:17.693127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:21:22.055092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:21:22.055166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:21:47.693319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:22:17.693407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:22:22.072981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:22:22.073050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:22:47.693537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:23:17.695299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:23:22.129051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:23:22.129117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:23:47.694188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:24:17.693256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:24:22.164901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:24:22.164961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:24:47.693349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:25:17.693227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:25:22.187855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:25:22.187917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:25:47.693160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:26:17.706683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:26:22.219448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:26:22.219516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:26:47.695039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:27:17.693634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:27:22.272322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:27:22.272388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:27:47.693382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:28:17.699975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:28:22.315670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:28:22.315723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:28:47.693178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:29:17.695838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:29:22.349235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:29:22.349292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:29:47.693211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:30:17.693148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:30:22.381749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:30:22.381814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:30:47.693276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:31:17.693168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:31:22.466254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:31:22.466319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:31:47.693140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:32:17.693772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:32:22.514693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:32:22.514745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:32:47.693191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:33:17.701047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:33:22.527203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:33:22.527257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:33:47.693284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:34:17.697956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:34:22.600841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:34:22.601001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:34:47.694342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:35:17.693246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:35:22.645946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:35:22.645993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:35:47.693335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:36:17.696841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:36:22.689627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:36:22.689687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:36:47.695298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:37:17.703935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:37:22.722155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:37:22.722224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:37:47.693020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:38:17.693986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:38:22.747048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:38:22.747093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:38:47.693433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:39:17.693509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:39:22.771636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:39:22.771678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:39:47.693166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:40:17.694441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:40:22.797493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:40:22.797555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:40:47.693139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:41:17.693223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:41:22.842494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:41:22.842545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:41:47.694910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:42:17.693191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:42:22.872565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:42:22.872621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:42:47.693728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:43:17.693531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:43:22.927276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:43:22.927329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:43:47.693167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:44:17.693128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:44:22.974528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:44:22.974959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:44:47.693284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:45:17.693365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:45:23.018134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:45:23.018335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:45:47.693329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:46:17.693244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:46:23.208773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:46:23.208834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:46:47.703530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:47:17.697492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:47:23.244666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:47:23.244720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:47:47.693798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:48:17.694412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:48:23.362276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:48:23.362404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:48:47.698361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:49:17.694493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:49:23.421895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:49:23.421945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:49:47.693343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:50:17.693460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:50:23.472118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:50:23.472178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:50:47.700750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:51:17.693474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:51:23.571714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:51:23.571766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:51:47.693819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:52:17.693138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:52:23.605862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:52:23.606100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:52:47.693583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:53:17.693199 metrics.go:34: INFO No non-zero metrics in the last 30s