By type
2022/02/07 02:43:15.074051 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/02/07 02:43:15.074082 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/07 02:43:15.074133 logstash.go:90: INFO Max Retries set to: 3
2022/02/07 02:43:15.074189 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/07 02:43:15.074279 metrics.go:23: INFO Metrics logging every 30s
2022/02/07 02:43:15.074302 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-fv4g9
2022/02/07 02:43:15.074452 async.go:63: INFO Flush Interval set to: 1s
2022/02/07 02:43:15.074471 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/07 02:43:15.074888 beat.go:221: INFO filebeat start running.
2022/02/07 02:43:15.074977 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/07 02:43:15.080270 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/07 02:43:15.080318 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/07 02:43:15.080348 crawler.go:38: INFO Loading Prospectors: 1
2022/02/07 02:43:15.080540 registrar.go:236: INFO Starting Registrar
2022/02/07 02:43:15.080550 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/07 02:43:15.080624 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/07 02:43:15.080711 sync.go:41: INFO Start sending events to output
2022/02/07 02:43:15.080751 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/07 02:43:15.080849 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/07 02:43:45.074698 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/02/07 02:44:05.084118 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/02/07 02:44:05.084255 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/02/07 02:44:05.084323 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/02/07 02:44:05.084375 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/02/07 02:44:05.084580 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/02/07 02:44:05.096623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:05.096660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:06.100126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:06.100166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:08.102727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:08.102767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:12.113680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:12.113728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:15.074803 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=55
2022/02/07 02:44:20.122486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:20.122521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:36.130269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:36.130298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:44:45.074659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:45:08.139711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:45:08.139779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:45:15.074753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:45:45.074600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:46:08.149539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:46:08.149595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:46:15.074719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:46:45.075005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:47:08.158909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:47:08.158978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:47:15.076567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:47:45.074709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:48:08.169001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:48:08.169063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:48:15.074614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:48:45.074630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:49:08.178651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:49:08.178685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:49:10.099109 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/02/07 02:49:15.074749 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/07 02:49:25.106663 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/02/07 02:49:25.107370 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/02/07 02:49:25.107894 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/07 02:49:45.074806 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/02/07 02:50:08.189709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:50:08.189764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:50:15.075047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:50:45.074779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:51:08.198264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:51:08.198303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:51:15.074646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:51:45.074687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:52:08.208694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:52:08.208731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:52:15.074518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:52:45.074686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:53:08.300339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:53:08.300802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:53:15.074664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:53:45.074661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:54:08.308102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:54:08.308136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:54:15.074800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:54:45.074848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:55:08.317847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:55:08.318054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:55:15.074724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:55:45.075071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:56:08.329783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:56:08.329834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:56:15.074640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:56:45.074726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:57:08.338025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:57:08.338071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:57:15.074841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:57:45.074715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:58:08.348530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:58:08.348569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:58:15.074801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:58:45.074723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:59:08.359969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:59:08.360063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 02:59:15.074780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 02:59:45.074651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:00:08.372194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:00:08.372240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:00:15.074747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:00:45.074582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:01:08.383596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:01:08.383664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:01:15.074684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:01:45.074605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:02:08.392495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:02:08.392558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:02:15.074722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:02:45.075038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:03:08.402293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:03:08.402346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:03:15.074745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:03:45.076893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:04:08.414059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:04:08.414115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:04:15.074706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:04:45.074679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:05:08.423092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:05:08.423124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:05:15.074693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:05:45.074741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:06:08.431888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:06:08.431937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:06:15.074693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:06:45.074668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:07:08.441321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:07:08.441440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:07:15.074781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:07:45.074632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:08:08.451808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:08:08.451837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:08:15.074694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:08:45.074701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:09:08.462650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:09:08.462690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:09:15.074514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:09:45.074533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:10:08.471119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:10:08.471156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:10:15.074640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:10:45.074820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:11:08.481021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:11:08.481083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:11:15.074777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:11:45.074785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:12:08.494745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:12:08.494777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:12:15.074697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:12:45.074759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:13:08.504960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:13:08.505004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:13:15.074739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:13:45.074736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:14:08.517304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:14:08.517418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:14:15.074683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:14:45.074604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:15:08.526649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:15:08.526706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:15:15.074722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:15:45.074705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:16:08.536576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:16:08.536645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:16:15.074581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:16:45.074632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:17:08.548528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:17:08.548578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:17:15.074766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:17:45.074682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:18:08.558373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:18:08.558416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:18:15.074704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:18:45.074673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:19:08.566645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:19:08.566697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:19:15.074789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:19:45.074614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:20:08.578700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:20:08.578769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:20:15.074719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:20:45.074696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:21:08.588600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:21:08.588653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:21:15.074622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:21:45.074655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:22:08.598811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:22:08.598845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:22:15.074712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:22:45.074695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:23:08.608436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:23:08.608476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:23:15.074744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:23:45.074552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:24:08.616831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:24:08.616890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:24:15.074857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:24:45.074704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:25:08.625878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:25:08.625942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:25:15.074611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:25:45.074757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:26:08.635219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:26:08.635259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:26:15.074628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:26:45.074766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:27:08.644062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:27:08.644129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:27:15.074841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:27:45.074807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:28:08.654554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:28:08.654598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:28:15.074700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:28:45.074690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:29:08.664495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:29:08.664625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:29:15.074687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:29:45.074637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:30:08.675250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:30:08.675301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:30:15.074745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:30:45.074755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:31:08.683215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:31:08.683275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:31:15.074662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:31:45.074682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:32:08.694474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:32:08.694520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:32:15.074729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:32:45.074731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:33:08.705421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:33:08.705480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:33:15.074675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:33:45.074706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:34:08.714504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:34:08.714545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:34:15.074725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:34:45.074683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:35:08.724441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:35:08.724494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:35:15.074632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:35:45.074652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:36:08.735284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:36:08.735330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:36:15.074721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:36:45.074826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:37:08.746062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:37:08.746108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:37:15.074683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:37:45.074651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:38:08.755613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:38:08.755643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:38:15.074650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:38:45.074694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:39:08.766489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:39:08.766531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:39:15.074717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:39:45.074694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:40:08.774482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:40:08.774520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:40:15.074639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:40:45.074743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:41:08.783238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:41:08.783283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:41:15.074657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:41:45.074822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:42:08.792395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:42:08.792432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:42:15.074725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:42:45.074654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:43:08.803837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:43:08.803907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:43:15.074896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:43:45.074738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:44:08.814017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:44:08.814053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:44:15.074572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:44:45.074657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:45:08.824481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:45:08.824527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:45:15.074753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:45:45.074669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:46:08.834158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:46:08.834207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:46:15.075080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:46:45.074917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:47:08.842833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:47:08.842878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:47:15.074763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:47:45.074776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/07 03:48:08.853199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:48:08.853277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/07 03:48:15.074719 metrics.go:34: INFO No non-zero metrics in the last 30s