By type
2022/01/31 02:35:00.361610 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/01/31 02:35:00.361648 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/31 02:35:00.361699 logstash.go:90: INFO Max Retries set to: 3
2022/01/31 02:35:00.361745 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/31 02:35:00.361867 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-nnzvn
2022/01/31 02:35:00.362016 async.go:63: INFO Flush Interval set to: 1s
2022/01/31 02:35:00.362041 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/31 02:35:00.362309 metrics.go:23: INFO Metrics logging every 30s
2022/01/31 02:35:00.362423 beat.go:221: INFO filebeat start running.
2022/01/31 02:35:00.362479 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/31 02:35:00.381850 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/31 02:35:00.381895 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/31 02:35:00.381927 crawler.go:38: INFO Loading Prospectors: 1
2022/01/31 02:35:00.381993 sync.go:41: INFO Start sending events to output
2022/01/31 02:35:00.382047 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/31 02:35:00.382026 registrar.go:236: INFO Starting Registrar
2022/01/31 02:35:00.382125 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/31 02:35:00.382166 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/31 02:35:00.382132 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/31 02:35:10.383094 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/31 02:35:10.383462 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/31 02:35:10.383474 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/31 02:35:10.383543 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/31 02:35:10.383577 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/31 02:35:15.464301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:15.464339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:16.468136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:16.468167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:18.471666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:18.471692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:22.478269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:22.478385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:30.362580 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=72 registrar.writes=1
2022/01/31 02:35:30.497472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:30.497500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:46.503899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:46.503940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:00.362524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:36:18.551158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:18.551198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:30.362635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:37:00.362586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:37:18.637430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:37:18.637483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:37:30.362595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:38:00.362544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:38:18.645617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:38:18.645754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:38:30.362550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:39:00.362647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:39:18.670866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:39:18.670909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:39:30.362562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:40:00.362547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:40:15.395196 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/31 02:40:18.813090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:40:18.813160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:40:30.362576 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/31 02:41:00.362538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:41:18.820262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:41:18.820312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:41:30.362570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:42:00.362585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:42:18.963290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:42:18.963332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:42:30.362576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:43:00.362550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:43:18.997964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:43:18.998006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:43:30.362553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:44:00.362531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:44:19.005882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:44:19.005919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:44:30.362595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:45:00.362575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:45:19.012623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:45:19.012664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:45:30.362554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:46:00.362527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:46:19.020977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:46:19.021012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:46:30.362521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:47:00.362515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:47:19.026691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:47:19.026718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:47:30.362604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:48:00.362627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:48:19.035644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:48:19.035695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:48:30.362538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:49:00.362561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:49:19.044121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:49:19.044175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:49:30.362537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:50:00.362576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:50:19.051540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:50:19.051589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:50:30.362570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:51:00.362578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:51:19.059570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:51:19.059603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:51:30.363930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:52:00.362564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:52:19.069673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:52:19.069725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:52:30.362555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:53:00.362528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:53:19.076569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:53:19.076601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:53:30.362629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:54:00.362607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:54:19.084994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:54:19.085024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:54:30.362544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:55:00.362531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:55:19.092055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:55:19.092094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:55:30.362568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:56:00.362545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:56:19.100101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:56:19.100142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:56:30.362577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:57:00.362562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:57:19.106381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:57:19.106413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:57:30.362562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:58:00.362540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:58:19.114148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:58:19.114180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:58:30.362559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:59:00.362561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:59:19.121335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:59:19.121364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:59:30.362552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:00:00.362552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:00:19.128757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:00:19.128806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:00:30.362561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:01:00.362549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:01:19.135082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:01:19.135111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:01:30.362548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:02:00.362591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:02:19.144003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:02:19.144041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:02:30.362539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:03:00.362535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:03:19.151724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:03:19.151771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:03:30.362539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:04:00.362552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:04:19.158602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:04:19.158630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:04:30.362476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:05:00.362618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:05:19.165790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:05:19.165895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:05:30.362568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:06:00.362587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:06:19.171504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:06:19.171543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:06:30.362610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:07:00.362527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:07:19.178075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:07:19.178115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:07:30.362543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:08:00.362590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:08:19.184910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:08:19.184940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:08:30.362561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:09:00.362528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:09:19.192152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:09:19.192321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:09:30.362551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:10:00.362690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:10:19.204457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:10:19.204782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:10:30.362630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:11:00.362549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:11:19.211730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:11:19.211769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:11:30.362511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:12:00.362567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:12:19.218514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:12:19.218544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:12:30.362543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:13:00.362533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:13:19.226229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:13:19.226269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:13:30.362532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:14:00.362548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:14:19.233641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:14:19.233672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:14:30.362524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:15:00.362628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:15:19.240224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:15:19.240256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:15:30.362534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:16:00.362587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:16:19.247525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:16:19.247567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:16:30.362535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:17:00.362561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:17:19.254754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:17:19.254792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:17:30.362551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:18:00.362596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:18:19.262819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:18:19.262995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:18:30.362522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:19:00.362586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:19:19.268887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:19:19.268923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:19:30.362581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:20:00.362546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:20:19.276088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:20:19.276117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:20:30.362548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:21:00.362578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:21:19.283989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:21:19.284034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:21:30.362546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:22:00.362542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:22:19.294924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:22:19.294956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:22:30.362584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:23:00.362575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:23:19.301338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:23:19.301366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:23:30.362545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:24:00.362547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:24:19.308667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:24:19.308697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:24:30.362541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:25:00.362565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:25:19.314905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:25:19.314933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:25:30.362579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:26:00.362637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:26:19.322703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:26:19.322737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:26:30.362588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:27:00.362538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:27:19.329580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:27:19.329620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:27:30.362529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:28:00.362586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:28:19.336925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:28:19.336976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:28:30.362662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:29:00.362587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:29:19.345020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:29:19.345066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:29:30.362568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:30:00.362572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:30:19.351946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:30:19.351982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:30:30.362536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:31:00.362563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:31:19.358292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:31:19.358325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:31:30.362575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:32:00.362606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:32:19.364895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:32:19.364923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:32:30.362529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:33:00.362549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:33:19.371489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:33:19.371528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:33:30.362609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:34:00.362577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:34:19.377943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:34:19.377974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:34:30.362559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:35:00.362611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:35:19.386333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:35:19.386363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:35:30.362599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:36:00.362701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:36:19.395013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:36:19.395051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:36:30.362604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:37:00.362557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:37:19.404998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:37:19.405032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:37:30.362561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:38:00.362754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:38:19.416487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:38:19.416535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:38:30.362560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:39:00.362627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:39:19.423352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:39:19.423383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:39:30.362522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:40:00.362621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:40:19.431654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:40:19.431707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host