2022/03/25 02:25:37.818339 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/25 02:25:37.818407 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/25 02:25:37.818462 metrics.go:23: INFO Metrics logging every 30s
2022/03/25 02:25:37.818469 logstash.go:90: INFO Max Retries set to: 3
2022/03/25 02:25:37.818528 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/25 02:25:37.818627 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-6ljcp
2022/03/25 02:25:37.818783 async.go:63: INFO Flush Interval set to: 1s
2022/03/25 02:25:37.818807 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/25 02:25:37.819223 beat.go:221: INFO filebeat start running.
2022/03/25 02:25:37.819305 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/25 02:25:37.994537 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/25 02:25:37.994598 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/25 02:25:37.994640 crawler.go:38: INFO Loading Prospectors: 1
2022/03/25 02:25:37.994741 registrar.go:236: INFO Starting Registrar
2022/03/25 02:25:37.994806 sync.go:41: INFO Start sending events to output
2022/03/25 02:25:37.994859 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/25 02:25:37.994906 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/25 02:25:37.994955 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/25 02:25:37.994996 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/25 02:25:47.996007 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/25 02:25:47.996047 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/25 02:25:47.996016 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/25 02:25:47.996121 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/25 02:25:47.996265 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/25 02:25:53.003403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:53.003444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:54.006611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:54.006642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:56.012348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:56.012379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:00.015928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:00.015964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:07.818792 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/03/25 02:26:08.019543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:08.019574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:24.022815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:24.022846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:37.818810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:26:56.028396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:56.028432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:27:07.818741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:27:37.818803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:27:56.034719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:27:56.034750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:28:07.818802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:28:37.818745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:28:56.040377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:28:56.040422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:29:07.818709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:29:37.818719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:29:56.045897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:29:56.045921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:30:07.818765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:30:37.818728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:30:53.005389 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/25 02:30:56.048728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:30:56.048753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:31:07.818723 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/25 02:31:37.818630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:31:56.051469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:31:56.051505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:32:07.818728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:32:37.818744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:32:56.054026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:32:56.054053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:33:07.818757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:33:37.819004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:33:56.056979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:33:56.057011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:34:07.818739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:34:37.818693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:34:56.060127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:34:56.060168 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:35:07.818732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:35:37.818694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:35:56.063942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:35:56.063966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:36:07.818772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:36:37.822613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:36:56.067425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:36:56.067458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:37:07.818723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:37:37.818742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:37:56.071054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:37:56.071097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:38:07.818776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:38:37.818707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:38:56.076252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:38:56.076304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:39:07.818762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:39:37.818800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:39:56.079942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:39:56.079975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:40:07.818689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:40:37.818794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:40:56.083405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:40:56.083462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:41:07.818735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:41:37.818723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:41:56.087237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:41:56.087269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:42:07.818749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:42:37.818788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:42:56.091173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:42:56.091208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:43:07.818877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:43:37.818667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:43:56.094250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:43:56.094281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:44:07.818745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:44:37.818705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:44:56.097828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:44:56.097896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:45:07.818690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:45:37.818728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:45:56.101759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:45:56.101793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:46:07.818710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:46:37.818744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:46:56.105093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:46:56.105123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:47:07.818729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:47:37.818849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:47:56.108621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:47:56.108651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:48:07.818706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:48:37.818771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:48:56.112261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:48:56.112294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:49:07.818760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:49:37.818672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:49:56.116092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:49:56.116123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:50:07.818758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:50:37.818726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:50:56.119704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:50:56.119739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:51:07.818722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:51:37.818932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:51:56.123130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:51:56.123170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:52:07.818705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:52:37.818732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:52:56.126543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:52:56.126586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:53:07.818813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:53:37.818721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:53:56.130802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:53:56.130829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:54:07.818771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:54:37.818750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:54:56.134903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:54:56.134935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:55:07.818743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:55:37.818698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:55:56.139011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:55:56.139052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:56:07.818728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:56:37.818707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:56:56.142953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:56:56.142987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:57:07.818695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:57:37.818804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:57:56.146524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:57:56.146555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:58:07.818742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:58:37.818751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:58:56.150056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:58:56.150089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:59:07.818671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:59:37.818717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:59:56.153153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:59:56.153186 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:00:07.818723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:00:37.818725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:00:56.156598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:00:56.156633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:01:07.818760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:01:37.818752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:01:56.160305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:01:56.160331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:02:07.818722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:02:37.818721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:02:56.163826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:02:56.163860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:07.818784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:03:37.818738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:03:56.167519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:56.167550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:07.818769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:04:37.818850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:04:56.171070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:56.171119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:07.818733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:37.818683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:56.175039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:56.175076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:07.818714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:37.818716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:56.178611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:56.178654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:07.818713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:37.818723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:56.181918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:56.181963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:07.818698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:37.818723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:56.185687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:56.185731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:09:07.818729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:09:37.818732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:09:56.189399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:09:56.189433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:07.818694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:37.818743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:56.193093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:56.193125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:07.818757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:37.818726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:56.197265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:56.197312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:07.818753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:37.818736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:56.203433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:56.203462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:07.818767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:37.818735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:56.207406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:56.207444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:07.818736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:37.818732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:56.211002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:56.211034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:07.818767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:37.818743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:56.213894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:56.213928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:07.818794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:37.818748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:56.218818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:56.218852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:07.818710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:37.818748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:56.222291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:56.222329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:07.818761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:37.818736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:56.225985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:56.226032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:07.818735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:37.818749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:56.229710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:56.229739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:07.818778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:37.818768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:56.233788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:56.233827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:07.818734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:37.818794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:56.237550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:56.237581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:07.818764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:37.818756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:56.241570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:56.241601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:07.818750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:37.818660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:56.244945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:56.244981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:07.818723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:37.818777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:56.248486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:56.248522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:07.818759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:37.818687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:56.251950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:56.251992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:07.818811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:37.818794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:56.256013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:56.256054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:07.818691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:37.818731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:56.259886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:56.259914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:07.818699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:37.818735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:56.263625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:56.263665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:07.818747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:37.818704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:56.267451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:56.267490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:07.818745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:37.818756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:56.271488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:56.271519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:07.818721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:37.818692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:56.275275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:56.275316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:07.818708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:37.818746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:56.278771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:56.278794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:07.818759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:37.818729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:56.282691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:56.282728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:07.818723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:37.818724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:56.285943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:56.285977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:07.818777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:37.818732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:56.289683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:56.289742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:36:07.818727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:37.818725 metrics.go:34: INFO No non-zero metrics in the last 30s