By type
2022/02/06 02:56:55.412071 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/02/06 02:56:55.412108 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/06 02:56:55.412188 logstash.go:90: INFO Max Retries set to: 3
2022/02/06 02:56:55.412207 metrics.go:23: INFO Metrics logging every 30s
2022/02/06 02:56:55.412259 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/06 02:56:55.412371 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-v7dkx
2022/02/06 02:56:55.412530 async.go:63: INFO Flush Interval set to: 1s
2022/02/06 02:56:55.412554 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/06 02:56:55.412913 beat.go:221: INFO filebeat start running.
2022/02/06 02:56:55.412995 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/06 02:56:55.830997 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/06 02:56:55.831063 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/06 02:56:55.831163 crawler.go:38: INFO Loading Prospectors: 1
2022/02/06 02:56:55.831241 registrar.go:236: INFO Starting Registrar
2022/02/06 02:56:55.831313 sync.go:41: INFO Start sending events to output
2022/02/06 02:56:55.831387 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/06 02:56:55.831498 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/06 02:56:55.831606 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/06 02:56:55.831640 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/06 02:57:25.412581 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/02/06 02:57:35.833771 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/02/06 02:57:35.833905 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/02/06 02:57:35.834071 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/02/06 02:57:35.834288 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/02/06 02:57:35.834502 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/02/06 02:57:40.840416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:40.840446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:41.844070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:41.844109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:43.847730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:43.847849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:47.857541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:47.857617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:55.412526 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=57
2022/02/06 02:57:55.864206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:55.864239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:58:11.871363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:58:11.871396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:58:25.412525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:58:43.878705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:58:43.878740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:58:55.412538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:59:25.412502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:59:43.886686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:59:43.886748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:59:55.412610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:00:25.412534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:00:43.894479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:00:43.894507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:00:55.412550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:01:25.412468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:01:43.901628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:01:43.901670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:01:55.412482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:02:25.412478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:02:40.842991 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/02/06 03:02:43.908658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:02:43.908692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:02:55.412505 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/06 03:02:55.844166 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/06 03:02:55.844186 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/02/06 03:02:55.844202 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/02/06 03:03:25.412510 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/02/06 03:03:43.915621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:03:43.915656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:03:55.412485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:04:25.412540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:04:43.922125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:04:43.922157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:04:55.412479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:05:25.412500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:05:43.930023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:05:43.930056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:05:55.412528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:06:25.412482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:06:43.938212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:06:43.938247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:06:55.412597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:07:25.412529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:07:43.944595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:07:43.944633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:07:55.412461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:08:25.412568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:08:43.951649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:08:43.951689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:08:55.412494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:09:25.412492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:09:43.959268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:09:43.959311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:09:55.412536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:10:25.412550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:10:43.967479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:10:43.967533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:10:55.412460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:11:25.412518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:11:43.974970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:11:43.975004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:11:55.412508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:12:25.412502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:12:43.982650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:12:43.982681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:12:55.412497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:13:25.412523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:13:43.988946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:13:43.988982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:13:55.412508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:14:25.412497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:14:43.996757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:14:43.996796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:14:55.412460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:15:25.412526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:15:44.005110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:15:44.005145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:15:55.412507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:16:25.412509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:16:44.014596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:16:44.014627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:16:55.412521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:17:25.412510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:17:44.021538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:17:44.021575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:17:55.412596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:18:25.412504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:18:44.028515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:18:44.028549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:18:55.412511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:19:25.412520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:19:44.037262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:19:44.037295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:19:55.412496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:20:25.412592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:20:44.044407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:20:44.044439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:20:55.412514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:21:25.412540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:21:44.051408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:21:44.051445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:21:55.412515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:22:25.412509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:22:44.060751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:22:44.060798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:22:55.412550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:23:25.412510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:23:44.068343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:23:44.068391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:23:55.412587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:24:25.412549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:24:44.081368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:24:44.081510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:24:55.412548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:25:25.412524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:25:44.089385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:25:44.089416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:25:55.412508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:26:25.412577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:26:44.097331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:26:44.097365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:26:55.412492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:27:25.412521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:27:44.105695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:27:44.105732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:27:55.412481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:28:25.412580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:28:44.112629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:28:44.112697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:28:55.412512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:29:25.412454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:29:44.119692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:29:44.119750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:29:55.412502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:30:25.412496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:30:44.128084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:30:44.128150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:30:55.412516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:31:25.412498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:31:44.135496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:31:44.135532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:31:55.412538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:32:25.412468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:32:44.142361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:32:44.142401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:32:55.412470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:33:25.412480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:33:44.150588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:33:44.150626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:33:55.412500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:34:25.412596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:34:44.157985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:34:44.158022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:34:55.412537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:35:25.412540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:35:44.165588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:35:44.165631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:35:55.412476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:36:25.412519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:36:44.173995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:36:44.174027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:36:55.412619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:37:25.412487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:37:44.182224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:37:44.182255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:37:55.412468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:38:25.412512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:38:44.189497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:38:44.189535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:38:55.412499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:39:25.412496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:39:44.197043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:39:44.197073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:39:55.412430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:40:25.412573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:40:44.203541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:40:44.203575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:40:55.412509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:41:25.412569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:41:44.215390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:41:44.215433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:41:55.412521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:42:25.412525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:42:44.222859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:42:44.222890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:42:55.412507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:43:25.412502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:43:44.229228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:43:44.229265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:43:55.412509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:44:25.412554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:44:44.237171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:44:44.237204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:44:55.412526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:45:25.412470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:45:44.244268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:45:44.244303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:45:55.412553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:46:25.412529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:46:44.250433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:46:44.250459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:46:55.412497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:47:25.412482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:47:44.257992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:47:44.258064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:47:55.412552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:48:25.412541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:48:44.268749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:48:44.268807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:48:55.412606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:49:25.412578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:49:44.275934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:49:44.275971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:49:55.412493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:50:25.412455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:50:44.283167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:50:44.283205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:50:55.412543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:51:25.412560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:51:44.291910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:51:44.291947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:51:55.412577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:52:25.412502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:52:44.300970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:52:44.301001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:52:55.412539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:53:25.412486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:53:44.307353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:53:44.307390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:53:55.412500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:54:25.412513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:54:44.314498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:54:44.314539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:54:55.412537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:55:25.412565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:55:44.321689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:55:44.321718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:55:55.412515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:56:25.412498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:56:44.330183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:56:44.330224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:56:55.412583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:57:25.412495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:57:44.337751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:57:44.337782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:57:55.412498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:58:25.412578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:58:44.344831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:58:44.344864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:58:55.412548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:59:25.412452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:59:44.353056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:59:44.353099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:59:55.412472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:00:25.412473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:00:44.360139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:00:44.360174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:00:55.412474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:01:25.412534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:01:44.367780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:01:44.367810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:01:55.412487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:02:25.412556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:02:44.382853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:02:44.382884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:02:55.412515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:03:25.412482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:03:44.390314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:03:44.390348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:03:55.412558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:04:25.412521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:04:44.396685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:04:44.396722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:04:55.412484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:05:25.412499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:05:44.403815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:05:44.403862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:05:55.412537 metrics.go:34: INFO No non-zero metrics in the last 30s