By type
2022/03/23 02:13:48.195260 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/23 02:13:48.195310 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/23 02:13:48.195532 metrics.go:23: INFO Metrics logging every 30s
2022/03/23 02:13:48.195545 logstash.go:90: INFO Max Retries set to: 3
2022/03/23 02:13:48.195739 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/23 02:13:48.195913 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-sdfpp
2022/03/23 02:13:48.196269 async.go:63: INFO Flush Interval set to: 1s
2022/03/23 02:13:48.196311 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/23 02:13:48.196784 beat.go:221: INFO filebeat start running.
2022/03/23 02:13:48.196838 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/23 02:13:48.476913 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/23 02:13:48.477055 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/23 02:13:48.477161 crawler.go:38: INFO Loading Prospectors: 1
2022/03/23 02:13:48.477461 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/23 02:13:48.477724 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/23 02:13:48.477808 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/23 02:13:48.477830 registrar.go:236: INFO Starting Registrar
2022/03/23 02:13:48.477897 sync.go:41: INFO Start sending events to output
2022/03/23 02:13:48.477975 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/23 02:13:58.480555 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/23 02:13:58.480758 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/23 02:13:58.481043 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/23 02:13:58.480916 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/23 02:13:58.481239 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/23 02:14:03.488452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:03.488499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:04.492610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:04.492643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:06.497770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:06.497805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:10.506523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:10.506570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:18.195922 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=70 registrar.writes=1
2022/03/23 02:14:18.517993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:18.518037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:34.527190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:34.527241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:48.195875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:15:06.536556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:15:06.536594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:15:18.195988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:15:48.196031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:16:06.545382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:16:06.545425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:16:18.195924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:16:48.196032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:17:06.555346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:17:06.555501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:17:18.195940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:17:48.195977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:18:06.565812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:18:06.565863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:18:18.195889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:18:48.195850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:19:03.496049 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/23 02:19:06.576525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:19:06.576564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:19:18.195915 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/23 02:19:48.196053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:20:06.586961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:20:06.587093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:20:18.195979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:20:48.195924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:21:06.596868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:21:06.596923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:21:18.195984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:21:48.195937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:22:06.606417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:22:06.606468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:22:18.195977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:22:48.196082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:23:06.615745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:23:06.615782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:23:18.195923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:23:48.195832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:24:06.626916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:24:06.626955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:24:18.195950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:24:48.196003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:25:06.644468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:25:06.644506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:25:18.196014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:25:48.196170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:26:06.653797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:26:06.653852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:26:18.195992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:26:48.195888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:27:06.663510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:27:06.663580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:27:18.196225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:27:48.195964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:28:06.672241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:28:06.672287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:28:18.196036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:28:48.195870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:29:06.682202 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:29:06.682236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:29:18.195884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:29:48.196031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:30:06.692372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:30:06.692412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:30:18.196032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:30:48.195944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:31:06.703141 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:31:06.703185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:31:18.195933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:31:48.195978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:32:06.711826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:32:06.711909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:32:18.196038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:32:48.196002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:33:06.721242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:33:06.721287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:33:18.195937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:33:48.196036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:34:06.730626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:34:06.730661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:34:18.195964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:34:48.195943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:35:06.740600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:35:06.740648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:35:18.195959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:35:48.195902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:36:06.750865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:36:06.750902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:36:18.196028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:36:48.196002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:37:06.760809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:37:06.760847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:37:18.195942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:37:48.195934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:38:06.771400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:38:06.771452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:38:18.195997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:38:48.196049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:39:06.782002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:39:06.782081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:39:18.195978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:39:48.195870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:40:06.793003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:40:06.793042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:40:18.196001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:40:48.196003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:41:06.802246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:41:06.802291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:41:18.196019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:41:48.196024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:42:06.812153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:42:06.812190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:42:18.195947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:42:48.196021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:43:06.821979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:43:06.822038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:43:18.195933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:43:48.195966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:44:06.831806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:44:06.831872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:44:18.196106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:44:48.195918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:45:06.841620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:45:06.841691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:45:18.196018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:45:48.195956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:46:06.851124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:46:06.851160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:46:18.195911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:46:48.195882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:47:06.863366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:47:06.863413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:47:18.196018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:47:48.195898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:48:06.873351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:48:06.873393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:48:18.195954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:48:48.195841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:49:06.883115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:49:06.883176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:49:18.196004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:49:48.195956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:50:06.892820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:50:06.892874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:50:18.195981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:50:48.195934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:51:06.903463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:51:06.903506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:51:18.195910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:51:48.196045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:52:06.914469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:52:06.914527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:52:18.195826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:52:48.195991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:53:06.923870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:53:06.923920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:53:18.196027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:53:48.195915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:54:06.934158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:54:06.934203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:54:18.196054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:54:48.195998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:55:06.945413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:55:06.945471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:55:18.195996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:55:48.196163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:56:06.956655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:56:06.956696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:56:18.196044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:56:48.196146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:57:06.968049 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:57:06.968140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:57:18.195885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:57:48.195874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:58:06.979582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:58:06.979639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:58:18.195907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:58:48.195963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:59:06.988947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:59:06.988988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:59:18.195966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:59:48.195848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:00:06.999362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:06.999569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:18.196030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:00:48.195893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:01:07.009542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:07.009583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:18.196012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:01:48.195948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:02:07.020776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:07.020827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:18.196019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:02:48.195964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:03:07.031178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:03:07.031218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:03:18.196273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:03:48.195967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:04:07.041743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:04:07.041776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:04:18.196029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:04:48.195988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:05:07.052682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:05:07.052735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:05:18.196008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:05:48.196000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:06:07.062725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:06:07.062797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:06:18.195925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:06:48.196218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:07:07.073154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:07:07.073192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:07:18.195882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:07:48.195911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:08:07.082666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:08:07.082707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:08:18.195853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:08:48.196001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:09:07.235567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:09:07.235621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:09:18.195982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:09:48.196184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:10:07.245812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:10:07.245870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:10:18.196162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:10:48.195845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:11:07.278800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:11:07.278878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:11:18.196027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:11:48.196088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:12:07.291103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:12:07.291145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:12:18.195925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:12:48.196130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:13:07.301015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:13:07.301058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:13:18.196000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:13:48.196091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:14:07.311976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:14:07.312023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:14:18.195990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:14:48.196015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:07.323508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:15:07.323540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:15:18.195979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:48.196014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:07.333767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:16:07.333800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:16:18.195981 metrics.go:34: INFO No non-zero metrics in the last 30s