Results

          2022/01/20 06:14:10.798631 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/20 06:14:10.798689 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/20 06:14:10.798772 logstash.go:90: INFO Max Retries set to: 3
2022/01/20 06:14:10.798816 metrics.go:23: INFO Metrics logging every 30s
2022/01/20 06:14:10.798837 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/20 06:14:10.798953 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-j5nps
2022/01/20 06:14:10.799131 async.go:63: INFO Flush Interval set to: 1s
2022/01/20 06:14:10.799153 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/20 06:14:10.799458 beat.go:221: INFO filebeat start running.
2022/01/20 06:14:10.799529 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/20 06:14:10.860436 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/20 06:14:10.860560 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/20 06:14:10.860629 crawler.go:38: INFO Loading Prospectors: 1
2022/01/20 06:14:10.860768 registrar.go:236: INFO Starting Registrar
2022/01/20 06:14:10.860928 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/20 06:14:10.860988 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/20 06:14:10.860986 sync.go:41: INFO Start sending events to output
2022/01/20 06:14:10.861177 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/20 06:14:10.861227 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/20 06:14:10.862589 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/20 06:14:10.862640 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/20 06:14:10.862679 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/20 06:14:10.862779 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/20 06:14:10.862809 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/20 06:14:15.875209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:15.875244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:16.880969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:16.881008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:18.889986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:18.890057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:22.897698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:22.897765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:30.908505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:30.908548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:40.799247 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=356 registrar.writes=1
2022/01/20 06:14:46.922336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:14:46.922369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:15:10.799627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:15:18.928592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:15:18.928640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:15:40.799239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:16:10.800248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:16:18.936836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:16:18.936863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:16:40.799415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:17:10.799230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:17:18.941764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:17:18.941790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:17:40.799223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:18:10.799248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:18:18.950756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:18:18.950791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:18:40.799352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:19:10.799335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:19:15.874209 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/20 06:19:15.874297 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/20 06:19:15.874330 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/20 06:19:15.874462 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/20 06:19:15.877707 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/01/20 06:19:18.956988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:19:18.957022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:19:40.799376 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/01/20 06:20:10.799165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:20:18.963239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:20:18.963271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:20:40.799090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:21:10.799265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:21:18.972861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:21:18.972908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:21:40.799310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:22:10.799190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:22:18.981065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:22:18.981099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:22:40.799062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:23:10.799135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:23:18.995354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:23:18.995402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:23:40.799315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:24:10.799382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:24:19.004980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:24:19.005024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:24:40.799194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:25:10.799166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:25:19.011195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:25:19.011227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:25:40.799135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:26:10.799207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:26:19.019704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:26:19.019728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:26:40.799224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:27:10.799190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:27:19.027193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:27:19.027239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:27:40.799287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:28:10.799298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:28:19.037869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:28:19.037914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:28:40.799203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:29:10.799187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:29:19.048165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:29:19.048214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:29:40.799194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:30:10.799378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:30:19.057491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:30:19.057516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:30:40.799230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:31:10.799347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:31:19.064066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:31:19.064104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:31:40.799248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:32:10.799271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:32:19.073704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:32:19.073752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:32:40.799233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:33:10.799282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:33:19.082494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:33:19.082513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:33:40.799367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:34:10.799246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:34:19.091280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:34:19.091301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:34:40.799388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:35:10.799228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:35:19.099813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:35:19.099835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:35:40.799330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:36:10.799378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:36:19.112101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:36:19.112143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:36:40.799235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:37:10.799282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:37:19.118649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:37:19.118690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:37:40.799280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:38:10.799273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:38:19.128067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:38:19.128119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:38:40.799344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:39:10.799374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:39:19.134306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:39:19.134346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:39:40.799163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:40:10.799345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:40:19.143973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:40:19.144004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:40:40.799225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:41:10.799241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:41:19.150779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:41:19.150813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:41:40.799165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:42:10.799161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:42:19.160511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:42:19.160531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:42:40.799275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:43:10.799416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:43:19.167517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:43:19.167552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:43:40.799235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:44:10.799351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:44:19.176163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:44:19.176185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:44:40.799299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:45:10.799335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:45:19.185104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:45:19.185131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:45:40.799285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:46:10.799174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:46:19.194696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:46:19.194745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:46:40.799241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:47:10.799228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:47:19.202219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:47:19.202251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:47:40.799203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:48:10.799218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:48:19.210463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:48:19.210521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:48:40.800176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:49:10.799295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:49:19.217282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:49:19.217424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:49:40.799029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:50:10.799330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:50:19.224701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:50:19.224725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:50:40.799229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:51:10.799141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:51:19.234923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:51:19.234949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:51:40.799228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:52:10.799172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:52:19.244564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:52:19.244604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:52:40.799173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:53:10.799135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:53:19.252467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:53:19.252505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:53:40.799253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:54:10.799200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:54:19.262065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:54:19.262108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:54:40.799136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:55:10.799211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:55:19.269897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:55:19.269928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:55:40.799179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:56:10.799249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:56:19.275903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:56:19.275925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:56:40.799300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:57:10.799270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:57:19.283854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:57:19.283891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:57:40.799365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:58:10.799391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:58:19.290596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:58:19.290625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:58:40.799252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:59:10.799063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 06:59:19.300763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:59:19.300816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 06:59:40.799305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:00:10.799185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:00:19.311400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:00:19.311430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:00:40.799260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:01:10.799148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:01:19.319739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:01:19.319785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:01:40.799322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:02:10.799192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:02:19.328103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:02:19.328133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:02:40.799160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:03:10.799295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:03:19.334906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:03:19.334932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:03:40.799236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:04:10.799191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:04:19.342618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:04:19.342647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:04:40.799350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:05:10.799223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:05:19.352194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:05:19.352232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:05:40.799368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:06:10.799146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:06:19.363575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:06:19.363609 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:06:40.799203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:07:10.799140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:07:19.370707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:07:19.370773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:07:40.799438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:08:10.799220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:08:19.379250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:08:19.379279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:08:40.799219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:09:10.799093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:09:19.386145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:09:19.386169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:09:40.799277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:10:10.799344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:10:19.395763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:10:19.395781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:10:40.799308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:11:10.799261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:11:19.404379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:11:19.404728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:11:40.799283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:12:10.799288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:12:19.413902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:12:19.414013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:12:40.799291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:13:10.799194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:13:19.422038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:13:19.422059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:13:40.799302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:14:10.799199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:14:19.436725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:14:19.436746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:14:40.799302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:15:10.799085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:15:19.443430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:15:19.443462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:15:40.799313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:16:10.799311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:16:19.451903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:16:19.451937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:16:40.799302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:17:10.799383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:17:19.458945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:17:19.458978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:17:40.799347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:18:10.799344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:18:19.467316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:18:19.467352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:18:40.799166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:19:10.799273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:19:19.476311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:19:19.476336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:19:40.799274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:20:10.799202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:20:19.484411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:20:19.484437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:20:40.799118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:21:10.799234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:21:19.492084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:21:19.492121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:21:40.799278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:22:10.799250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:22:19.502713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:22:19.502747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:22:40.799280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:23:10.799146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:23:19.509046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:23:19.509066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:23:40.799046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:24:10.799130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:24:19.518926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:24:19.518950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:24:40.799188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:25:10.799249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:25:19.527665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:25:19.527694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:25:40.799301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:26:10.799232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:26:19.536303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:26:19.536342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:26:40.799306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:27:10.799401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:27:19.544366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:27:19.544396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:27:40.799539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:28:10.799199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:28:19.553535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:28:19.553570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:28:40.799187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:29:10.799360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:29:19.561277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:29:19.561362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:29:40.799378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:30:10.799290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:30:19.570347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:30:19.570365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:30:40.799162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:31:10.799178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:31:19.578442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:31:19.578465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:31:40.799244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:32:10.799275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:32:19.587359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:32:19.587382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:32:40.799100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:33:10.799232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:33:19.597421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:33:19.597470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:33:40.799323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:34:10.799105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:34:19.606706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:34:19.606750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:34:40.799267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:35:10.799187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:35:19.621775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:35:19.621974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:35:40.799165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:36:10.799089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:36:19.630781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:36:19.630824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:36:40.799114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:37:10.799253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:37:19.638157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:37:19.638190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:37:40.799335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:38:10.800000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:38:19.648908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:38:19.648955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:38:40.799171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:39:10.799417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:39:19.658332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:39:19.658374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:39:40.799226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:40:10.799262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:40:19.666260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:40:19.666304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:40:40.799252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:41:10.799384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:41:19.674955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:41:19.674987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:41:40.799307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:42:10.799302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:42:19.683836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:42:19.683886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:42:40.799257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:43:10.799267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:43:19.692525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:43:19.692568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:43:40.799341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:44:10.799179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:44:19.702102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:44:19.702145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:44:40.799205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:45:10.799276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:45:19.710039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:45:19.710075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:45:40.799231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:46:10.799298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:46:19.718782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:46:19.718814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:46:40.799153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:47:10.799332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:47:19.727878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:47:19.727928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:47:40.799134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:48:10.799248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:48:19.737350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:48:19.737393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:48:40.799257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:49:10.799300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:49:19.745245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:49:19.745318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:49:40.799282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:50:10.799052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:50:19.753616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:50:19.753646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:50:40.799180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:51:10.799201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:51:19.761986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:51:19.762036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:51:40.799196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:52:10.799155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:52:19.770180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:52:19.770222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:52:40.799358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:53:10.799173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:53:19.780502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:53:19.780541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:53:40.799272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:54:10.799133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/20 07:54:19.792812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/20 07:54:19.792850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host