By type
2022/03/07 03:09:33.578625 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/07 03:09:33.578676 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/07 03:09:33.578761 logstash.go:90: INFO Max Retries set to: 3
2022/03/07 03:09:33.578865 metrics.go:23: INFO Metrics logging every 30s
2022/03/07 03:09:33.578867 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/07 03:09:33.579018 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-4c24r
2022/03/07 03:09:33.579213 async.go:63: INFO Flush Interval set to: 1s
2022/03/07 03:09:33.579229 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/07 03:09:33.580202 beat.go:221: INFO filebeat start running.
2022/03/07 03:09:33.580324 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/07 03:09:33.585110 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/07 03:09:33.585400 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/07 03:09:33.587684 sync.go:41: INFO Start sending events to output
2022/03/07 03:09:33.587732 registrar.go:236: INFO Starting Registrar
2022/03/07 03:09:33.587622 crawler.go:38: INFO Loading Prospectors: 1
2022/03/07 03:09:33.587839 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/07 03:09:33.588222 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/07 03:09:33.588354 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/07 03:09:33.588387 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/07 03:09:53.590911 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/07 03:09:53.591773 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/07 03:09:53.591908 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/07 03:09:53.592115 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/07 03:09:53.592151 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/07 03:09:58.608989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:09:58.609050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:09:59.613104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:09:59.613139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:01.617218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:01.617249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:03.579396 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/07 03:10:05.626951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:05.627008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:13.633600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:13.633631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:29.651479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:29.651540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:10:33.579236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:11:01.669483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:11:01.669529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:11:03.579262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:11:33.579505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:12:01.689662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:01.689699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:12:03.579216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:12:33.579142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:13:01.710910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:13:01.710942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:13:03.579179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:13:33.579154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:14:01.729740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:14:01.729776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:14:03.579238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:14:33.579159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:14:58.602245 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/07 03:14:58.602246 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/07 03:14:58.602253 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/07 03:14:58.602287 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/07 03:15:01.748884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:15:01.748913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:15:03.579316 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/07 03:15:06.608769 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/07 03:15:33.579366 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/07 03:16:01.767921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:16:01.767989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:16:03.579235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:16:33.579349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:17:01.786742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:17:01.786789 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:17:03.580239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:17:33.579128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:18:01.807880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:18:01.807920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:18:03.579554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:18:33.579295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:19:01.825560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:19:01.825597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:19:03.579202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:19:33.579375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:20:01.843119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:20:01.843163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:20:03.579229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:20:33.579197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:21:01.860426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:21:01.860550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:21:03.579265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:21:33.579226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:22:01.876575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:22:01.876611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:22:03.579193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:22:33.579148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:23:01.897342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:23:01.897403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:23:03.580653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:23:33.579197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:24:01.913546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:24:01.913580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:24:03.579181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:24:33.579427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:25:01.937267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:25:01.937308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:25:03.579154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:25:33.579157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:26:01.957109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:26:01.957310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:26:03.579192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:26:33.579166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:27:01.974359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:27:01.974401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:27:03.579201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:27:33.579515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:28:01.993414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:28:01.993622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:28:03.579162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:28:33.579275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:29:02.012107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:29:02.012147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:29:03.579194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:29:33.579188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:30:02.031161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:30:02.031242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:30:03.579381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:30:33.579279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:31:02.050825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:31:02.050867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:31:03.579314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:31:33.579156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:32:02.068730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:32:02.068882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:32:03.579207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:32:33.579260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:33:02.087458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:33:02.087590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:33:03.579530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:33:33.579283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:34:02.105770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:34:02.105810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:34:03.579241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:34:33.579201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:35:02.124747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:35:02.124784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:35:03.579300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:35:33.579223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:36:02.143936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:36:02.143975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:36:03.579119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:36:33.579218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:37:02.162930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:37:02.162972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:37:03.579199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:37:33.579182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:38:02.181531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:38:02.181592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:38:03.579264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:38:33.579281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:39:02.202455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:39:02.202625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:39:03.579323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:39:33.579257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:40:02.220124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:40:02.220172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:40:03.579179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:40:33.579279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:41:02.237036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:41:02.237082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:41:03.579606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:41:33.579272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:42:02.258001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:42:02.258040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:42:03.579241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:42:33.579237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:43:02.276261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:43:02.276310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:43:03.579222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:43:33.579244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:44:02.294580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:44:02.294997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:44:03.579239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:44:33.579201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:45:02.315550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:45:02.315599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:45:03.579199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:45:33.579199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:46:02.334672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:46:02.334716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:46:03.579239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:46:33.579523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:47:02.354722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:47:02.354793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:47:03.579378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:47:33.579337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:48:02.372219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:48:02.372278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:48:03.579275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:48:33.579375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:49:02.391397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:49:02.391440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:49:03.579193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:49:33.579164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:50:02.411060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:50:02.411108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:50:03.579307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:50:33.579520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:51:02.428314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:51:02.428461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:51:03.579160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:51:33.579159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:52:02.449381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:52:02.449432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:52:03.579257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:52:33.579285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:53:02.471098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:53:02.471150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:53:03.579290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:53:33.579213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:54:02.490766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:54:02.490805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:54:03.579349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:54:33.579271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:55:02.509002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:55:02.509085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:55:03.579415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:55:33.579533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:56:02.526375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:56:02.526423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:56:03.579231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:56:33.579190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:57:02.544023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:57:02.544082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:57:03.579201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:57:33.579307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:58:02.574503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:02.574571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:03.579316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:58:33.579246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:59:02.581398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:02.581452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:03.579195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:59:33.579185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:00:02.590760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:00:02.590828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:00:03.579157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:00:33.579192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:01:02.597432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:01:02.597483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:01:03.579150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:01:33.579222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:02:02.605208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:02:02.605291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:02:03.579358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:02:33.579242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:03:02.613010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:03:02.613053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:03:03.579173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:03:33.579190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:04:02.621316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:04:02.621363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:04:03.579351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:04:33.579163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:05:02.629500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:05:02.629538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:05:03.579215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:05:33.579214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:06:02.637120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:06:02.637171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:06:03.579178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:06:33.579152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:07:02.643743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:07:02.643783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:07:03.579216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:07:33.579176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:08:02.650553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:08:02.650608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:08:03.579213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:08:33.579177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:09:02.657713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:09:02.657779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:09:03.579217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:09:33.579192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:10:02.665516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:10:02.665601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:10:03.579391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:10:33.579299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:11:02.672622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:11:02.672667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:11:03.579214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:11:33.579475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:12:02.679216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:12:02.679257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:12:03.579182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:12:33.579180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:13:02.685955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:13:02.686022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:13:03.579198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:13:33.579431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:14:02.693465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:14:02.693516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:14:03.579695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:14:33.579251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:15:02.700719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:15:02.700768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:15:03.579604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:15:33.579240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:16:02.708737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:16:02.708778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:16:03.579187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:16:33.579232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:17:02.715937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:17:02.715991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:17:03.579191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:17:33.579188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:18:02.723540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:18:02.723578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:18:03.579221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:18:33.579352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:19:02.731493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:19:02.731549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:19:03.579277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:19:33.579338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:20:02.744624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:20:02.744668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:20:03.579265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:20:33.579180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:21:02.757070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:21:02.757113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:21:03.579255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:21:33.579213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:22:02.768221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:22:02.768280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:22:03.579220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:22:33.579227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:23:02.776246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:23:02.776318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:23:03.579163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:23:33.579161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:24:02.783658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:24:02.783923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:24:03.579222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:24:33.579168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:25:02.791614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:25:02.791650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:25:03.579289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:25:33.579239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:26:02.800991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:26:02.801035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:26:03.579198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:26:33.579476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:27:02.822885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:27:02.822939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:27:03.579296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:27:33.579279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:28:02.829668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:28:02.829706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:28:03.579872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:28:33.579165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:29:02.837405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:29:02.837444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:29:03.579203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:29:33.579264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:30:02.845435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:30:02.845488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:30:03.579166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:30:33.579225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:31:02.855947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:31:02.855986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:31:03.579293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:31:33.579221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:32:02.864401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:32:02.864458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:32:03.579172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:32:33.579314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:33:02.871884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:33:02.871957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:33:03.579201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:33:33.579157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:34:02.881367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:34:02.881405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:34:03.579256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:34:33.579250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:35:02.888218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:35:02.888263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:35:03.579277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:35:33.579369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:36:02.895396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:36:02.895454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:36:03.579379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:36:33.579365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:37:02.902275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:37:02.902316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:37:03.579343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:37:33.579216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:38:02.910073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:38:02.910116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:38:03.579221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:38:33.579325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:39:02.917914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:39:02.917957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:39:03.579182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:39:33.579200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:40:02.926824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:40:02.926857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:40:03.579382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:40:33.579219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:41:02.935892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:41:02.935942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:41:03.579290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:41:33.579229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:42:02.943932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:42:02.943972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:42:03.579219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:42:33.579274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:43:02.951858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:43:02.951904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:43:03.579173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:43:33.579215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:44:02.960888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:44:02.960933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:44:03.579262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:44:33.579244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:45:02.968757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:45:02.968843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:45:03.579633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:45:33.579301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:46:02.977386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:46:02.977511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:46:03.579212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:46:33.579317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:47:02.991081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:47:02.991157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:47:03.579831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:47:33.579303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:48:03.007299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:48:03.007353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:48:03.579384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:48:33.579207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:49:03.021450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:49:03.021887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:49:03.579156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:49:33.579189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:50:03.029966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:50:03.030006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:50:03.579214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:50:33.579261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:51:03.037593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:51:03.037630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:51:03.579274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:51:33.579199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:52:03.045883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:52:03.045935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:52:03.579166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:52:33.579138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:53:03.060214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:53:03.060365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:53:03.579281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:53:33.579220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:54:03.070328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:54:03.070372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:54:03.579178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:54:33.579224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:55:03.105397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:55:03.105448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:55:03.579436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:55:33.579282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:56:03.121212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:56:03.121250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:56:03.579147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:56:33.579223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:57:03.129954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:57:03.130007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:57:03.579201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:57:33.579158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:58:03.138519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:58:03.138558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:58:03.579600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:58:33.579139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:59:03.146325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:59:03.146365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:59:03.579090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:59:33.579606 metrics.go:34: INFO No non-zero metrics in the last 30s