By type
2022/01/31 02:34:59.919489 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/01/31 02:34:59.919523 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/31 02:34:59.919585 logstash.go:90: INFO Max Retries set to: 3
2022/01/31 02:34:59.919636 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/31 02:34:59.919714 metrics.go:23: INFO Metrics logging every 30s
2022/01/31 02:34:59.919792 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-bj2bs
2022/01/31 02:34:59.919929 async.go:63: INFO Flush Interval set to: 1s
2022/01/31 02:34:59.919944 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/31 02:34:59.920298 beat.go:221: INFO filebeat start running.
2022/01/31 02:34:59.920376 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/31 02:35:00.020740 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/31 02:35:00.020809 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/31 02:35:00.020846 crawler.go:38: INFO Loading Prospectors: 1
2022/01/31 02:35:00.020930 registrar.go:236: INFO Starting Registrar
2022/01/31 02:35:00.021128 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/31 02:35:00.021190 sync.go:41: INFO Start sending events to output
2022/01/31 02:35:00.021220 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/31 02:35:00.021238 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/31 02:35:00.021267 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/31 02:35:29.920190 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/01/31 02:35:50.024193 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/31 02:35:50.024423 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/31 02:35:50.024607 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/31 02:35:50.024637 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/31 02:35:50.024618 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/31 02:35:55.032722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:55.032756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:56.036031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:56.036080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:58.040180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:58.040224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:35:59.920085 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=55
2022/01/31 02:36:02.048681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:02.048731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:10.058874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:10.058911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:26.069561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:26.069604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:29.920062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:36:58.078122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:58.078169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:36:59.920087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:37:29.920216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:37:58.088533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:37:58.088587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:37:59.920143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:38:29.920128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:38:58.131904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:38:58.131942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:38:59.920133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:39:29.920148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:39:58.170532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:39:58.170597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:39:59.920083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:40:29.920199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:40:55.036381 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/31 02:40:58.180964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:40:58.181004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:40:59.920295 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/31 02:41:10.038152 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/31 02:41:10.038139 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/31 02:41:10.038165 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/31 02:41:29.920079 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/01/31 02:41:58.220144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:41:58.220196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:41:59.920199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:42:29.920202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:42:58.232899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:42:58.232943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:42:59.920021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:43:29.920059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:43:58.240763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:43:58.240801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:43:59.920098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:44:29.920132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:44:58.280222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:44:58.280329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:44:59.920366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:45:29.920217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:45:58.290473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:45:58.290531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:45:59.920158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:46:29.920088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:46:58.300522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:46:58.300591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:46:59.920171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:47:29.920144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:47:58.312809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:47:58.312852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:47:59.920149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:48:29.920271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:48:58.325085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:48:58.325137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:48:59.920142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:49:29.920126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:49:58.340692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:49:58.340732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:49:59.920119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:50:29.920146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:50:58.350673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:50:58.350745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:50:59.920140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:51:29.920069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:51:58.360696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:51:58.360781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:51:59.920328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:52:29.920056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:52:58.372044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:52:58.372100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:52:59.920176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:53:29.920116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:53:58.382851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:53:58.382902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:53:59.920112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:54:29.920200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:54:58.392856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:54:58.392889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:54:59.920065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:55:29.920146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:55:58.403475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:55:58.403536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:55:59.920124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:56:29.920101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:56:58.414510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:56:58.414556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:56:59.920150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:57:29.920169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:57:58.424386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:57:58.424417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:57:59.920228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:58:29.919926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:58:58.435139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:58:58.435200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:58:59.920339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:59:29.920209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 02:59:58.444242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:59:58.444351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 02:59:59.920103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:00:29.920318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:00:58.454115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:00:58.454146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:00:59.920086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:01:29.920153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:01:58.462121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:01:58.462162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:01:59.920092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:02:29.920104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:02:58.471386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:02:58.471422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:02:59.920182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:03:29.920262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:03:58.482019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:03:58.482073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:03:59.920098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:04:29.920071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:04:58.491882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:04:58.491926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:04:59.920105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:05:29.920093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:05:58.501331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:05:58.501380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:05:59.920118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:06:29.920227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:06:58.510644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:06:58.510709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:06:59.920117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:07:29.920123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:07:58.520348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:07:58.520386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:07:59.920197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:08:29.920147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:08:58.529885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:08:58.529915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:08:59.920101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:09:29.920123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:09:58.540503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:09:58.540536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:09:59.920166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:10:29.920059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:10:58.551541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:10:58.551565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:10:59.920003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:11:29.920197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:11:58.560890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:11:58.560937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:11:59.920117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:12:29.920246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:12:58.570963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:12:58.571014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:12:59.920137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:13:29.920230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:13:58.580338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:13:58.580404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:13:59.920159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:14:29.920138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:14:58.590588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:14:58.590635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:14:59.920148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:15:29.920225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:15:58.599670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:15:58.599707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:15:59.920133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:16:29.920245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:16:58.608221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:16:58.608267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:16:59.920206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:17:29.920197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:17:58.618905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:17:58.618948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:17:59.920183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:18:29.920079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:18:58.628157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:18:58.628190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:18:59.920026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:19:29.920154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:19:58.636780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:19:58.636843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:19:59.920214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:20:29.920076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:20:58.646007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:20:58.646041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:20:59.920236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:21:29.920121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:21:58.655292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:21:58.655338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:21:59.920132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:22:29.920078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:22:58.664626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:22:58.664697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:22:59.920184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:23:29.920165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:23:58.675032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:23:58.675101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:23:59.920142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:24:29.920133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:24:58.683248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:24:58.683296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:24:59.920090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:25:29.920235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:25:58.695367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:25:58.695437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:25:59.920266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:26:29.920093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:26:58.705636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:26:58.705674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:26:59.920251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:27:29.920183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:27:58.719728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:27:58.719766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:27:59.920222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:28:29.920167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:28:58.729516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:28:58.729568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:28:59.919969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:29:29.920090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:29:58.738518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:29:58.738564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:29:59.920227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:30:29.920307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:30:58.749860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:30:58.749912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:30:59.920149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:31:29.920177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:31:58.759611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:31:58.759661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:31:59.920219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:32:29.920161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:32:58.767496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:32:58.767643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:32:59.920124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:33:29.920141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:33:58.776457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:33:58.776495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:33:59.920062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:34:29.920199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:34:58.786358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:34:58.786401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:34:59.920097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:35:29.920124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:35:58.794883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:35:58.794921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:35:59.920090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:36:29.920081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:36:58.806802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:36:58.806841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:36:59.920165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:37:29.919998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:37:58.817758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:37:58.817786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:37:59.920032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:38:29.920090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:38:58.827364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:38:58.827437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:38:59.920093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:39:29.920093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/31 03:39:58.837618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:39:58.837657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/31 03:39:59.920168 metrics.go:34: INFO No non-zero metrics in the last 30s