By type
2022/02/17 02:57:26.333372 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/17 02:57:26.333417 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/17 02:57:26.333536 logstash.go:90: INFO Max Retries set to: 3
2022/02/17 02:57:26.333595 metrics.go:23: INFO Metrics logging every 30s
2022/02/17 02:57:26.333664 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/17 02:57:26.333816 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-rrnks
2022/02/17 02:57:26.334049 async.go:63: INFO Flush Interval set to: 1s
2022/02/17 02:57:26.334076 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/17 02:57:26.334535 beat.go:221: INFO filebeat start running.
2022/02/17 02:57:26.334607 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/17 02:57:26.545488 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/17 02:57:26.545567 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/17 02:57:26.545645 crawler.go:38: INFO Loading Prospectors: 1
2022/02/17 02:57:26.545708 registrar.go:236: INFO Starting Registrar
2022/02/17 02:57:26.545846 sync.go:41: INFO Start sending events to output
2022/02/17 02:57:26.545921 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/17 02:57:26.545965 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/17 02:57:26.546010 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/17 02:57:26.546027 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/17 02:57:36.547219 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/02/17 02:57:36.547400 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/02/17 02:57:36.547495 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/02/17 02:57:36.547502 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/02/17 02:57:36.547847 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/02/17 02:57:41.622037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:41.622068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:42.624659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:42.624686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:44.627272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:44.627297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:48.632633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:48.632666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:56.333920 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/02/17 02:57:56.638451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:57:56.638499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:58:12.649002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:58:12.649025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:58:26.333846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 02:58:44.657822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:58:44.657855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:58:56.333906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 02:59:26.333920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 02:59:44.697358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:59:44.697428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 02:59:56.333935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:00:26.333873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:00:44.705220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:00:44.705252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:00:56.333859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:01:26.333843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:01:44.742865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:01:44.742896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:01:56.333847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:02:26.333899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:02:41.556380 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/17 03:02:44.782870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:02:44.782896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:02:56.333853 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/17 03:03:26.333846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:03:44.789351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:03:44.789381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:03:56.333907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:04:26.333876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:04:44.796562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:44.796594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:56.333913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:05:26.333878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:05:44.833864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:05:44.833901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:05:56.333864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:06:26.333851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:06:44.840301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:06:44.840333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:06:56.333851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:07:26.333887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:07:44.847717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:07:44.847762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:07:56.333906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:08:26.333903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:08:44.853852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:08:44.853886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:08:56.333855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:09:26.333882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:09:44.862625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:09:44.862653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:09:56.333874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:10:26.333929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:10:44.870989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:10:44.871024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:10:56.333862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:11:26.333852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:11:44.877729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:11:44.877759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:11:56.333882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:12:26.333899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:12:44.885270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:12:44.885298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:12:56.333854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:13:26.333877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:13:44.892203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:13:44.892234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:13:56.333902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:14:26.333935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:14:44.899105 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:14:44.899276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:14:56.333897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:15:26.333963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:15:44.906512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:15:44.906542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:15:56.333831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:16:26.333867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:16:44.913274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:16:44.913306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:16:56.333847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:17:26.333892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:17:44.919911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:17:44.919958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:17:56.333856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:18:26.333906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:18:44.926767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:18:44.926803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:18:56.333889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:19:26.333854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:19:44.934681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:19:44.934812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:19:56.333854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:20:26.333934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:20:44.942034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:20:44.942073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:20:56.333879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:21:26.333856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:21:44.949169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:21:44.949283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:21:56.333891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:22:26.333910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:22:44.955332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:22:44.955362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:22:56.333853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:23:26.333895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:23:44.961734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:23:44.961770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:23:56.333843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:24:26.333960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:24:44.967456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:24:44.967487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:24:56.333890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:25:26.333870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:25:44.973334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:25:44.973462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:25:56.333831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:26:26.333897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:26:44.979860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:26:44.979891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:26:56.333858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:27:26.333875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:27:44.986094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:27:44.986130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:27:56.333884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:28:26.333906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:28:44.992755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:28:44.992781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:28:56.333848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:29:26.333904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:29:44.998940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:29:44.998973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:29:56.333904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:30:26.333931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:30:45.006198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:30:45.006225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:30:56.333868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:31:26.333848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:31:45.013187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:31:45.013219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:31:56.333845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:32:26.333903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:32:45.020705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:32:45.020742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:32:56.333913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:33:26.333909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:33:45.027770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:33:45.027823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:33:56.333888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:34:26.333924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:34:45.034547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:34:45.034587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:34:56.333881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:35:26.333866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:35:45.044096 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:35:45.044199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:35:56.333879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:36:26.335396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:36:45.052341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:36:45.052378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:36:56.333859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:37:26.333834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:37:45.058775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:37:45.058801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:37:56.333877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:38:26.333836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:38:45.065193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:38:45.065221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:38:56.333831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:39:26.333844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:39:45.071993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:39:45.072032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:39:56.333857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:40:26.333909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:40:45.083395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:40:45.083427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:40:56.333931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:41:26.333958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:41:45.090690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:41:45.090740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:41:56.333891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:42:26.333887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:42:45.098462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:42:45.098501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:42:56.333897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:43:26.333892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:43:45.105704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:43:45.105735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:43:56.333894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:44:26.333888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:44:45.113379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:44:45.113415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:44:56.333867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:45:26.333807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:45:45.120904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:45:45.120938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:45:56.333877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:46:26.333889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:46:45.128328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:46:45.128351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:46:56.333895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:47:26.333872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:47:45.134942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:47:45.134976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:47:56.333900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:48:26.333876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:48:45.141521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:48:45.141553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:48:56.333864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:49:26.333914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:49:45.152352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:49:45.152396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:49:56.333922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:50:26.333856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:50:45.159665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:50:45.159692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:50:56.333915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:51:26.333854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:51:45.166297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:51:45.166340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:51:56.333917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:52:26.333886 metrics.go:34: INFO No non-zero metrics in the last 30s