2022/03/30 03:04:10.475312 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/30 03:04:10.475370 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/30 03:04:10.475459 metrics.go:23: INFO Metrics logging every 30s
2022/03/30 03:04:10.475609 logstash.go:90: INFO Max Retries set to: 3
2022/03/30 03:04:10.475725 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/30 03:04:10.475884 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-62fqn
2022/03/30 03:04:10.476089 async.go:63: INFO Flush Interval set to: 1s
2022/03/30 03:04:10.476106 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/30 03:04:10.476860 beat.go:221: INFO filebeat start running.
2022/03/30 03:04:10.476980 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/30 03:04:10.482496 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/30 03:04:10.482572 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/30 03:04:10.482617 crawler.go:38: INFO Loading Prospectors: 1
2022/03/30 03:04:10.482824 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/30 03:04:10.482924 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/30 03:04:10.482952 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/30 03:04:10.482964 registrar.go:236: INFO Starting Registrar
2022/03/30 03:04:10.482997 sync.go:41: INFO Start sending events to output
2022/03/30 03:04:10.483034 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/30 03:04:30.486013 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/30 03:04:30.486176 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/30 03:04:30.486174 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/30 03:04:30.486259 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/30 03:04:30.486473 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/30 03:04:35.490776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:35.490819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:36.494044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:36.494094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:38.500172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:38.500217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:40.475874 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=76 registrar.writes=1
2022/03/30 03:04:42.505006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:42.505040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:50.508187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:50.508217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:06.511578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:06.511662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:10.477060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:05:38.523412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:38.523444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:40.475933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:06:10.475773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:06:38.532722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:06:38.532765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:06:40.475780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:07:10.475875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:07:38.542219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:07:38.542273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:07:40.475852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:08:10.475695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:08:38.549554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:08:38.549602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:08:40.475780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:09:10.475769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:09:35.502600 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/30 03:09:38.557133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:09:38.557173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:09:40.475884 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/30 03:10:10.475747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:10:38.563506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:10:38.563532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:10:40.475793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:11:10.475847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:11:38.571622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:11:38.571655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:11:40.475723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:12:10.475761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:12:38.578945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:12:38.578997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:12:40.475756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:13:10.475788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:13:38.588522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:13:38.588589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:13:40.475752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:14:10.475809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:14:38.595739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:14:38.595772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:14:40.475781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:15:10.476362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:15:38.603774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:15:38.603810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:15:40.475813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:16:10.476246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:16:38.610465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:16:38.610504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:16:40.475770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:17:10.475742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:17:38.618635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:17:38.618679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:17:40.475862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:18:10.475732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:18:38.625681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:18:38.625720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:18:40.475777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:19:10.475820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:19:38.633601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:19:38.633637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:19:40.475792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:20:10.475729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:20:38.640992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:20:38.641025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:20:40.475926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:21:10.475835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:21:38.648570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:21:38.648637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:21:40.475933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:22:10.475914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:22:38.661406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:22:38.661443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:22:40.475754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:23:10.475827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:23:38.668029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:23:38.668069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:23:40.475725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:24:10.475775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:24:38.681769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:24:38.681802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:24:40.475740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:25:10.475803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:25:38.688259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:25:38.688300 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:25:40.475733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:26:10.475789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:26:38.695360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:26:38.695413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:26:40.475806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:27:10.475696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:27:38.702253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:27:38.702289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:27:40.475834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:28:10.475866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:28:38.712597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:28:38.712645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:28:40.476006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:29:10.475774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:29:38.720525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:29:38.720582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:29:40.475799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:30:10.475753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:30:38.727340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:30:38.727660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:30:40.475755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:31:10.475754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:31:38.730964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:31:38.730998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:31:40.475761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:32:10.475713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:32:38.734361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:32:38.734399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:32:40.475765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:33:10.475726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:33:38.738261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:33:38.738304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:33:40.475972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:34:10.475735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:34:38.741902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:34:38.741946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:34:40.475714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:35:10.475732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:35:38.744884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:35:38.744929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:35:40.475698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:36:10.475809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:36:38.750682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:36:38.750714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:36:40.475753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:37:10.475733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:37:38.753615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:37:38.753649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:37:40.475742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:38:10.475764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:38:38.757664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:38:38.757693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:38:40.475777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:39:10.475783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:39:38.761084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:39:38.761140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:39:40.475883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:40:10.475847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:40:38.766793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:40:38.766838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:40:40.475755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:41:10.475795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:41:38.771377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:41:38.771429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:41:40.475831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:42:10.475809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:42:38.774879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:42:38.774912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:42:40.475739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:43:10.475744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:43:38.778212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:43:38.778246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:43:40.475800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:44:10.475786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:44:38.783006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:44:38.783043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:44:40.475760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:45:10.475786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:45:38.786456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:45:38.786489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:45:40.475742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:46:10.475821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:46:38.790896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:46:38.790936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:46:40.475829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:47:10.475773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:47:38.794684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:38.794716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:40.475783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:48:10.475824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:48:38.802205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:48:38.802252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:48:40.475741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:49:10.475798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:49:38.807383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:49:38.807414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:49:40.475710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:50:10.475779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:50:38.817961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:50:38.818067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:50:40.475834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:51:10.475774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:51:38.825383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:51:38.825431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:51:40.475763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:52:10.475786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:52:38.833645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:52:38.833780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:52:40.475843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:53:10.475859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:53:38.836691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:53:38.836723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:53:40.475745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:54:10.475781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:54:38.840676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:54:38.840714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:54:40.475815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:55:10.476022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:55:38.845143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:55:38.845181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:55:40.475691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:56:10.475757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:56:38.848475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:56:38.848511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:56:40.475775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:57:10.475761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:57:38.851392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:57:38.851434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:57:40.475787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:58:10.475819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:58:38.854449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:58:38.854482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:58:40.475727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:59:10.475812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:59:38.857663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:59:38.857862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:59:40.475868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:00:10.475890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:00:38.862328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:00:38.862379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:00:40.475770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:01:10.475821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:01:38.865889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:01:38.865939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:01:40.475804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:02:10.475821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:02:38.869989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:02:38.870117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:02:40.475899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:03:10.476055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:03:38.873212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:03:38.873247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:03:40.476004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:04:10.475847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:04:38.877164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:04:38.877206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:04:40.475771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:05:10.475751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:05:38.881076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:05:38.881106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:05:40.475805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:06:10.475749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:06:38.884577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:06:38.884611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:06:40.475922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:07:10.475823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:07:38.887903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:07:38.887936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:07:40.475724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:08:10.475780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:08:38.892490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:08:38.892556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:08:40.475806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:09:10.475796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:09:38.895662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:09:38.895705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:09:40.475919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:10:10.475801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:10:38.899260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:10:38.899291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:10:40.475796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:11:10.475841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:11:38.902361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:11:38.902394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:11:40.475750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:12:10.475722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:12:38.905735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:12:38.905771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:12:40.475731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:13:10.475844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:13:38.909922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:13:38.909969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:13:40.475848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:14:10.475697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:14:38.913698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:14:38.913750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:14:40.475806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:15:10.475789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:15:38.917163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:15:38.917428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:15:40.475873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:16:10.475813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:16:38.920404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:16:38.920554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:16:40.475768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:17:10.475764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:17:38.924468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:17:38.924504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:17:40.475729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:18:10.475902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:18:38.927688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:18:38.927721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:18:40.475775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:19:10.475739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:19:38.930649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:19:38.930685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:19:40.475824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:20:10.475850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:20:38.934133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:20:38.934171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:20:40.475749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:21:10.475848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:21:38.937499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:21:38.937554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:21:40.475704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:22:10.475897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:22:38.944977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:22:38.945058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:22:40.475739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:23:10.475770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:23:38.948031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:23:38.948064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:23:40.475741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:24:10.475726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:24:38.950876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:24:38.950905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:24:40.475839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:25:10.475757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:25:38.954232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:25:38.954273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:25:40.475718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:26:10.475818 metrics.go:34: INFO No non-zero metrics in the last 30s