By type
2022/03/16 03:09:05.471697 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/16 03:09:05.471797 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/16 03:09:05.471977 logstash.go:90: INFO Max Retries set to: 3
2022/03/16 03:09:05.472128 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/16 03:09:05.472479 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-slksz
2022/03/16 03:09:05.472864 async.go:63: INFO Flush Interval set to: 1s
2022/03/16 03:09:05.472893 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/16 03:09:05.472502 metrics.go:23: INFO Metrics logging every 30s
2022/03/16 03:09:05.474699 beat.go:221: INFO filebeat start running.
2022/03/16 03:09:05.474792 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/16 03:09:05.480127 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/16 03:09:05.480401 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/16 03:09:05.480590 registrar.go:236: INFO Starting Registrar
2022/03/16 03:09:05.481152 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/16 03:09:05.480657 sync.go:41: INFO Start sending events to output
2022/03/16 03:09:05.480509 crawler.go:38: INFO Loading Prospectors: 1
2022/03/16 03:09:05.481881 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/16 03:09:05.482060 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/16 03:09:05.482127 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/16 03:09:25.484891 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/16 03:09:25.485043 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/16 03:09:25.485223 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/16 03:09:25.485309 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/16 03:09:25.485398 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/16 03:09:25.539668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:25.539719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:26.546634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:26.546668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:28.550963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:28.551076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:32.561980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:32.562076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:35.475394 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=64 registrar.writes=1
2022/03/16 03:09:40.568691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:40.568752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:56.592306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:09:56.592385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:10:05.474840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:10:28.619850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:10:28.620196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:10:35.475017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:11:05.475030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:11:28.647077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:11:28.647136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:11:35.474861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:12:05.475450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:12:28.671152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:12:28.671214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:12:35.474961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:13:05.474963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:13:28.700709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:13:28.700750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:13:35.474810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:14:05.474911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:14:28.721366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:14:28.721438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:14:30.515612 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/16 03:14:30.515612 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/16 03:14:30.515696 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/16 03:14:30.515614 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/16 03:14:35.475142 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/16 03:14:41.508266 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/16 03:15:05.474888 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/16 03:15:28.744011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:15:28.744064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:15:35.474948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:16:05.474924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:16:28.765999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:16:28.766072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:16:35.475039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:17:05.474954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:17:28.786986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:17:28.787026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:17:35.474911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:18:05.474939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:18:28.807391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:18:28.807467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:18:35.474929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:19:05.474882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:19:28.830630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:19:28.830699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:19:35.474948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:20:05.474876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:20:28.857439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:20:28.857482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:20:35.474900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:21:05.474841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:21:28.879869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:21:28.879927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:21:35.474929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:22:05.474918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:22:28.900172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:22:28.900462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:22:35.474905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:23:05.474958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:23:28.918726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:23:28.918771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:23:35.474957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:24:05.475018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:24:28.942399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:24:28.942460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:24:35.474897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:25:05.474930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:25:28.965567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:25:28.965606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:25:35.474856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:26:05.475034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:26:29.007905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:26:29.007950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:26:35.476907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:27:05.475184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:27:29.043134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:27:29.043201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:27:35.476779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:28:05.476545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:28:29.068611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:28:29.068672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:28:35.474923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:29:05.475043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:29:29.092861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:29:29.092973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:29:35.474914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:30:05.474928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:30:29.112009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:30:29.112070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:30:35.474959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:31:05.474990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:31:29.140535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:31:29.140584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:31:35.474916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:32:05.474906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:32:29.158248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:32:29.158302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:32:35.474891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:33:05.474858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:33:29.179295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:33:29.179558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:33:35.474849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:34:05.475092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:34:29.200799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:34:29.200844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:34:35.474852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:35:05.474931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:35:29.221189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:35:29.221244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:35:35.474850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:36:05.474949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:36:29.241017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:36:29.241065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:36:35.474873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:37:05.475168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:37:29.259064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:37:29.259144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:37:35.474963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:38:05.474955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:38:29.278292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:38:29.278504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:38:35.474909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:39:05.474930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:39:29.296574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:39:29.296629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:39:35.475053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:40:05.474956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:40:29.317672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:40:29.317725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:40:35.475051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:41:05.475040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:41:29.336585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:41:29.336684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:41:35.474863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:42:05.475112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:42:29.357946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:42:29.358084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:42:35.474945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:43:05.474912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:43:29.377097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:43:29.377156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:43:35.474831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:44:05.474868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:44:29.400070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:44:29.400112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:44:35.474920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:45:05.475632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:45:29.419657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:45:29.419719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:45:35.474883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:46:05.475002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:46:29.439980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:46:29.440038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:46:35.474926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:47:05.474989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:47:29.462462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:47:29.462544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:47:35.475025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:48:05.474892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:48:29.483106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:48:29.483147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:48:35.474877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:49:05.476163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:49:29.504777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:49:29.504867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:49:35.474803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:50:05.474850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:50:29.527482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:50:29.527540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:50:35.474876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:51:05.474955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:51:29.546572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:51:29.546639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:51:35.474845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:52:05.474933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:52:29.565849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:52:29.565904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:52:35.474857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:53:05.474937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:53:29.585915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:53:29.585974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:53:35.474883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:54:05.475023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:54:29.604519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:54:29.604576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:54:35.474927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:55:05.474960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:55:29.626691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:55:29.626728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:55:35.474839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:56:05.474900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:56:29.657716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:56:29.657771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:56:35.474974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:57:05.475301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:57:29.691441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:29.691508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:57:35.474926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:58:05.474928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:58:29.716894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:58:29.717171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:58:35.474917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:59:05.474864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:59:29.735881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:59:29.735934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 03:59:35.475011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:00:05.474908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:00:29.774994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:00:29.775167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:00:35.475126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:01:05.475073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:01:29.798990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:01:29.799198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:01:35.474790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:02:05.474814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:02:29.818397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:02:29.818557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:02:35.475080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:03:05.475012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:03:29.840119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:03:29.840167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:03:35.474879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:04:05.475024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:04:29.866985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:04:29.867035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:04:35.474885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:05:05.475083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:05:29.885305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:05:29.885358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:05:35.474953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:06:05.474921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:06:29.905485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:06:29.905532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:06:35.474887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:07:05.475105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:07:29.928408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:07:29.928460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:07:35.474970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:08:05.474903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:08:29.947159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:08:29.947214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:08:35.474805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:09:05.474903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:09:29.973334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:09:29.973382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:09:35.474878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:10:05.474932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:10:29.992914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:10:29.993072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:10:35.474931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:11:05.474822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:11:30.019555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:11:30.019618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:11:35.475005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:12:05.474933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:12:30.041301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:12:30.041354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:12:35.475019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:13:05.475028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:13:30.065563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:13:30.065625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:13:35.475594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:14:05.475104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:14:30.095957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:14:30.096012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:14:35.480613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:15:05.474958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:15:30.114257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:15:30.114296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:15:35.480072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:16:05.474862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:16:30.134294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:16:30.134443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:16:35.475037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:17:05.474941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:17:30.154762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:17:30.154817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:17:35.474888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:18:05.474867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:18:30.175073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:18:30.175119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:18:35.476558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:19:05.474994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:19:30.201304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:19:30.201371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:19:35.474936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:20:05.474973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:20:30.218164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:20:30.218200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:20:35.475025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:21:05.474881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:21:30.238328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:21:30.238399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:21:35.475075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:22:05.474862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:22:30.257478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:22:30.257573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:22:35.474897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:23:05.475187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:23:30.315160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:23:30.315199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:23:35.474846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:24:05.476591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:24:30.349598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:24:30.349650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:24:35.474872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:25:05.476474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:25:30.386191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:25:30.386254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:25:35.474898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:26:05.474941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:26:30.419638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:26:30.419676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:26:35.474854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:27:05.474957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:27:30.438858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:27:30.438924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:27:35.474925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:28:05.474858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:28:30.459847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:28:30.459890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:28:35.474851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:29:05.474964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:29:30.507119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:29:30.507170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:29:35.474847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:30:05.474856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:30:30.532150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:30:30.532215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:30:35.474862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:31:05.474853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:31:30.555055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:31:30.555175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:31:35.475021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:32:05.474879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:32:30.576195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:32:30.576255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:32:35.474892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:33:05.474790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:33:30.599106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:33:30.599166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:33:35.474911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:34:05.475112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:34:30.623468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:34:30.623553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:34:35.474965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:35:05.474864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:35:30.640733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:35:30.640777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:35:35.474917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:36:05.474876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:36:30.667982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:36:30.668028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:36:35.474849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:37:05.474846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:37:30.688595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:37:30.688636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:37:35.475026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:38:05.474908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:38:30.709855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:38:30.709916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:38:35.474820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:39:05.474916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:39:30.730694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:39:30.730755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:39:35.474834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:40:05.475134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:40:30.751569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/16 04:40:30.751614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host