2022/04/06 03:11:41.950552 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/04/06 03:11:41.950624 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0 2022/04/06 03:11:41.950788 metrics.go:23: INFO Metrics logging every 30s 2022/04/06 03:11:41.950859 logstash.go:90: INFO Max Retries set to: 3 2022/04/06 03:11:41.951070 outputs.go:108: INFO Activated logstash as output plugin. 2022/04/06 03:11:41.951391 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-s24ls 2022/04/06 03:11:41.951733 async.go:63: INFO Flush Interval set to: 1s 2022/04/06 03:11:41.951751 async.go:64: INFO Max Bulk Size set to: 2048 2022/04/06 03:11:41.953476 beat.go:221: INFO filebeat start running. 2022/04/06 03:11:41.953636 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file. 2022/04/06 03:11:41.966053 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry 2022/04/06 03:11:41.966145 registrar.go:123: INFO States Loaded from registrar: 0 2022/04/06 03:11:41.966187 crawler.go:38: INFO Loading Prospectors: 1 2022/04/06 03:11:41.966501 prospector_log.go:65: INFO Prospector with previous states loaded: 0 2022/04/06 03:11:41.966657 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 2022/04/06 03:11:41.966721 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1 2022/04/06 03:11:41.966744 registrar.go:236: INFO Starting Registrar 2022/04/06 03:11:41.966813 sync.go:41: INFO Start sending events to output 2022/04/06 03:11:41.966854 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s 2022/04/06 03:12:01.975511 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log 2022/04/06 03:12:01.975733 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log 2022/04/06 03:12:01.975906 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log 2022/04/06 03:12:01.976138 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log 2022/04/06 03:12:01.976135 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log 2022/04/06 03:12:06.995403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:06.995452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:08.000067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:08.000113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:10.004397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:10.004639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:11.953185 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/04/06 03:12:14.015118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:14.015160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:22.024314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:22.024358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:38.044723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:38.044824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:12:41.952366 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:13:10.092520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:13:10.099669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:13:11.951211 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:13:41.952282 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:14:10.123097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:14:10.123154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:14:11.951779 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:14:41.951413 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:15:10.147715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:15:10.147767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:15:11.951237 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:15:41.953209 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:16:10.174826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:16:10.174886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:16:11.953299 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:16:41.951320 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:17:07.004969 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached. 2022/04/06 03:17:07.005025 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached. 2022/04/06 03:17:07.004990 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached. 2022/04/06 03:17:07.005402 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached. 2022/04/06 03:17:10.192531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:17:10.192580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:17:11.951245 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/04/06 03:17:23.004756 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached. 2022/04/06 03:17:41.953092 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/04/06 03:18:10.210905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:18:10.210965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:18:11.951273 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:18:41.951187 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:19:10.231972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:19:10.232024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:19:11.961033 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:19:41.951287 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:20:10.250600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:20:10.250658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:20:11.951402 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:20:41.951269 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:21:10.290599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:21:10.290655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:21:11.951196 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:21:41.958667 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:22:10.311140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:22:10.311208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:22:11.951677 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:22:41.953182 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:23:10.333553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:23:10.333612 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:23:11.951194 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:23:41.952445 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:24:10.357075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:24:10.357122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:24:11.952373 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:24:41.951233 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:25:10.396119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:25:10.396213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:25:11.951391 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:25:41.954793 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:26:10.415641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:26:10.415703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:26:11.953534 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:26:41.953113 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:27:10.439232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:27:10.439305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:27:11.951339 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:27:41.951508 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:28:10.477235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:28:10.477368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:28:11.953803 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:28:41.958246 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:29:10.506576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:29:10.506631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:29:11.952140 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:29:41.951255 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:30:10.526971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:30:10.527030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:30:11.951246 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:30:41.951232 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:31:10.548085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:31:10.548131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:31:11.957129 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:31:41.953225 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:32:10.573318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:32:10.573489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:32:11.953080 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:32:41.952373 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:33:10.594726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:33:10.594928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:33:11.953256 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:33:41.951398 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:34:10.613986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:34:10.614084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:34:11.953354 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:34:41.951668 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:35:10.638455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:35:10.638528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:35:11.951739 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:35:41.951282 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:36:10.657345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:36:10.657398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:36:11.951381 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:36:41.951248 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:37:10.678475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:37:10.678538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:37:11.951254 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:37:41.951200 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:38:10.707238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:38:10.707308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:38:11.953069 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:38:41.951220 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:39:10.740727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:39:10.740833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:39:11.951269 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:39:41.951291 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:40:10.764188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:40:10.764257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:40:11.951203 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:40:41.951309 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:41:10.785164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:41:10.785229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:41:11.951369 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:41:41.951309 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:42:10.803312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:42:10.803353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:42:11.951252 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:42:41.951277 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:43:10.822529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:43:10.822580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:43:11.951283 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:43:41.951174 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:44:10.839666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:44:10.839710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:44:11.951165 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:44:41.951410 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:45:10.872281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:45:10.872336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:45:11.953110 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:45:41.951336 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:46:10.890267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:46:10.890315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:46:11.951360 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:46:41.951197 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:47:10.913281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:47:10.913350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:47:11.951287 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:47:41.951368 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:48:10.931520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:48:10.931575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:48:11.951304 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:48:41.951218 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:49:10.952193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:49:10.952258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:49:11.951249 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:49:41.951761 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:50:10.969103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:50:10.969164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:50:11.951302 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:50:41.951521 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:51:11.002398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:51:11.002873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:51:11.951295 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:51:41.953128 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:52:11.029013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:52:11.029128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:52:11.953192 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:52:41.951278 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:53:11.051052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:53:11.051146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:53:11.952984 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:53:41.951278 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/04/06 03:54:11.114118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:54:11.114171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/04/06 03:54:11.951295 metrics.go:34: INFO No non-zero metrics in the last 30s