By type
2022/04/18 03:07:30.927609 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/18 03:07:30.927673 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/18 03:07:30.927803 metrics.go:23: INFO Metrics logging every 30s
2022/04/18 03:07:30.927805 logstash.go:90: INFO Max Retries set to: 3
2022/04/18 03:07:30.927910 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/18 03:07:30.928065 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-lvpwv
2022/04/18 03:07:30.928411 async.go:63: INFO Flush Interval set to: 1s
2022/04/18 03:07:30.928443 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/18 03:07:30.928962 beat.go:221: INFO filebeat start running.
2022/04/18 03:07:30.929052 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/18 03:07:30.935152 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/18 03:07:30.935291 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/18 03:07:30.935356 crawler.go:38: INFO Loading Prospectors: 1
2022/04/18 03:07:30.935370 registrar.go:236: INFO Starting Registrar
2022/04/18 03:07:30.935454 sync.go:41: INFO Start sending events to output
2022/04/18 03:07:30.935609 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/18 03:07:30.935755 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/18 03:07:30.935868 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/18 03:07:30.935919 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/18 03:07:50.939162 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/18 03:07:50.939474 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/18 03:07:50.939601 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/18 03:07:50.939695 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/18 03:07:50.939808 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/18 03:07:55.977729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:07:55.977785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:07:56.984645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:07:56.984693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:07:58.997011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:07:58.997110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:00.928335 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=64 registrar.writes=1
2022/04/18 03:08:03.008573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:03.008845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:11.017977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:11.018033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:27.042362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:27.042401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:30.928324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:08:59.067356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:59.067413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:09:00.928159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:09:30.928157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:09:59.094324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:09:59.094380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:10:00.928153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:10:30.928241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:10:59.117557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:10:59.117604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:11:00.928127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:11:30.928178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:11:59.138364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:11:59.138419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:12:00.928243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:12:30.929371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:12:55.975496 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/18 03:12:56.956194 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/18 03:12:56.956217 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/18 03:12:57.967959 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/18 03:12:59.155818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:12:59.155858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:13:00.928176 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/04/18 03:13:13.998345 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/18 03:13:30.928194 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/04/18 03:13:59.175337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:13:59.175419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:14:00.928345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:14:30.928112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:14:59.214505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:14:59.214552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:15:00.928172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:15:30.928187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:15:59.239052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:15:59.239106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:16:00.928237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:16:30.928249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:16:59.259951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:16:59.260016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:17:00.928144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:17:30.928112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:17:59.287090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:17:59.287158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:18:00.928252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:18:30.928234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:18:59.314655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:18:59.314722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:19:00.928173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:19:30.928330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:19:59.343657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:19:59.343717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:20:00.929693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:20:30.928255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:20:59.362996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:20:59.363066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:21:00.928215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:21:30.928259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:21:59.387396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:21:59.387509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:22:00.928252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:22:30.928149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:22:59.408782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:22:59.408848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:23:00.928194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:23:30.928170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:23:59.435242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:23:59.435299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:24:00.928265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:24:30.928319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:24:59.462455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:24:59.462543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:25:00.928139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:25:30.928137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:25:59.484490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:25:59.484570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:26:00.928160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:26:30.928138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:26:59.509259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:26:59.509322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:27:00.928142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:27:30.928261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:27:59.529427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:27:59.529716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:28:00.928196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:28:30.928187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:28:59.551905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:28:59.551984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:29:00.929598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:29:30.928273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:29:59.570493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:29:59.570549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:30:00.928123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:30:30.928616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:30:59.593482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:30:59.593542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:31:00.928177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:31:30.928156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:31:59.614515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:31:59.614579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:32:00.928295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:32:30.928259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:32:59.636678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:32:59.636741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:33:00.928433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:33:30.928257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:33:59.657197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:33:59.657319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:34:00.928248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:34:30.928131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:34:59.679366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:34:59.679557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:35:00.928191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:35:30.928117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:35:59.701842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:35:59.701914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:36:00.928203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:36:30.928187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:36:59.724559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:36:59.724633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:37:00.928098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:37:30.928623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:37:59.744676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:37:59.744747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:38:00.928241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:38:30.928146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:38:59.766691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:38:59.766759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:39:00.928250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:39:30.928242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:39:59.790295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:39:59.790347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:40:00.928223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:40:30.928280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:40:59.811561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:40:59.811650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:41:00.928303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:41:30.928601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:41:59.834816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:41:59.834888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:42:00.928185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:42:30.928008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:42:59.856222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:42:59.856283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:43:00.928268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:43:30.928212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:43:59.882534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:43:59.883087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:44:00.928208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:44:30.928149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:44:59.908849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:44:59.908898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:45:00.928162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:45:30.928078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:45:59.929540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:45:59.929605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:46:00.928272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:46:30.928255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:46:59.950200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:46:59.950276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:47:00.928138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:47:30.928101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:47:59.971797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:47:59.971854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:48:00.928498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:48:30.928344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:48:59.992427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:48:59.992898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:49:00.928279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:49:30.928328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:50:00.013052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:50:00.013121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:50:00.928208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:50:30.928159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:51:00.032854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:51:00.032992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:51:00.928215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:51:30.928238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:52:00.053355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:52:00.053573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:52:00.928103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:52:30.928505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:53:00.080568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:53:00.080643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:53:00.928333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:53:30.928212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:54:00.104937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:54:00.105008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:54:00.928181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:54:30.928243 metrics.go:34: INFO No non-zero metrics in the last 30s