By type
2022/03/16 03:09:11.788384 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:11.788480 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/16 03:09:11.788536 metrics.go:23: INFO Metrics logging every 30s
2022/03/16 03:09:11.788899 logstash.go:90: INFO Max Retries set to: 3
2022/03/16 03:09:11.789019 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/16 03:09:11.789154 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-jkkw4
2022/03/16 03:09:11.789395 async.go:63: INFO Flush Interval set to: 1s
2022/03/16 03:09:11.789438 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/16 03:09:11.789966 beat.go:221: INFO filebeat start running.
2022/03/16 03:09:11.790068 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/16 03:09:11.794354 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/16 03:09:11.794426 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/16 03:09:11.794461 crawler.go:38: INFO Loading Prospectors: 1
2022/03/16 03:09:11.794743 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/16 03:09:11.794846 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/16 03:09:11.794878 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/16 03:09:11.794891 registrar.go:236: INFO Starting Registrar
2022/03/16 03:09:11.794982 sync.go:41: INFO Start sending events to output
2022/03/16 03:09:11.795015 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/16 03:09:31.803974 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/16 03:09:31.804288 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/16 03:09:31.804697 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/16 03:09:31.804831 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/16 03:09:31.804965 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/16 03:09:36.825009 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:36.825058 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:37.836046 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:37.836089 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:39.846079 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:39.846461 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:41.789233 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=72 registrar.writes=1
2022/03/16 03:09:43.858321 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:43.858354 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:51.869993 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:51.870062 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:07.890274 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:07.890324 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:11.788975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:10:39.909327 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:39.909369 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:41.789118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:11:11.788902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:11:39.936124 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:39.936165 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:41.789443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:12:11.790331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:12:39.956307 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:39.956370 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:41.788909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:13:11.788928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:13:39.974940 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:39.975114 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:41.788929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:14:11.788914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:14:36.830338 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/16 03:14:40.004046 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:40.004107 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:41.788938 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/16 03:15:11.788886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:15:40.023879 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:40.023927 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:41.788967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:16:11.788913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:16:40.044946 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:40.045320 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:41.788947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:17:11.788900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:17:40.066974 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:40.067038 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:41.788936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:18:11.788799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:18:40.086952 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:40.087018 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:41.788883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:19:11.789110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:19:40.104264 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:40.104301 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:41.790219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:20:11.788823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:20:40.123756 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:40.123816 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:41.788835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:21:11.788895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:21:40.144365 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:40.144412 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:41.788868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:22:11.788895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:22:40.164212 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:40.164251 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:41.792003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:23:11.788885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:23:40.183737 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:40.183823 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:41.788906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:24:11.788854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:24:40.202246 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:40.202285 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:41.788877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:25:11.788987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:25:40.223068 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:40.223202 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:41.788960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:26:11.788896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:26:40.266428 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:40.266471 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:41.788943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:27:11.788950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:27:40.284499 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:40.284534 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:41.788979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:28:11.788998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:28:40.302098 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:40.302160 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:41.788937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:29:11.788811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:29:40.322292 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:40.322336 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:41.788887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:30:11.788902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:30:40.340390 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:40.340429 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:41.788898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:31:11.788874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:31:40.360887 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:40.360923 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:41.788866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:32:11.788896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:32:40.387563 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:40.387609 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:41.788920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:33:11.788901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:33:40.406644 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:40.406682 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:41.788916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:34:11.788834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:34:40.425241 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:40.425396 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:41.788928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:35:11.792308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:35:40.444751 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:40.444794 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:41.788934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:36:11.788880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:36:40.463801 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:40.463848 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:41.788901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:37:11.788824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:37:40.485758 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:40.485802 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:41.788874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:38:11.788894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:38:40.503211 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:40.503254 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:41.788954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:39:11.788912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:39:40.521633 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:40.521691 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:41.788905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:40:11.788969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:40:40.540775 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:40.540815 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:41.788907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:41:11.788882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:41:40.560638 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:40.560717 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:41.788953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:42:11.788842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:42:40.582913 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:40.582978 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:41.788805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:43:11.788953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:43:40.603104 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:40.603155 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:41.788905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:44:11.788915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:44:40.627982 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:40.628375 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:41.788973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:45:11.788931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:45:40.647198 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:40.647244 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:41.788915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:46:11.788821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:46:40.666925 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:40.666974 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:41.789020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:47:11.788949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:47:40.686857 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:40.686899 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:41.788925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:48:11.788847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:48:40.706156 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:40.706194 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:41.788875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:49:11.789017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:49:40.725507 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:40.725548 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:41.788879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:50:11.788896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:50:40.748486 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:40.748779 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:41.788944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:51:11.788876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:51:40.774549 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:40.774591 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:41.788911 metrics.go:34: INFO No non-zero metrics in the last 30s