By type
2022/01/06 03:07:29.873974 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/06 03:07:29.874019 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/06 03:07:29.874105 logstash.go:90: INFO Max Retries set to: 3
2022/01/06 03:07:29.874121 metrics.go:23: INFO Metrics logging every 30s
2022/01/06 03:07:29.874316 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/06 03:07:29.874438 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-6jttm
2022/01/06 03:07:29.874688 async.go:63: INFO Flush Interval set to: 1s
2022/01/06 03:07:29.874713 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/06 03:07:29.875218 beat.go:221: INFO filebeat start running.
2022/01/06 03:07:29.875291 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/06 03:07:30.151521 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/06 03:07:30.151642 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/06 03:07:30.151724 crawler.go:38: INFO Loading Prospectors: 1
2022/01/06 03:07:30.151843 registrar.go:236: INFO Starting Registrar
2022/01/06 03:07:30.151908 sync.go:41: INFO Start sending events to output
2022/01/06 03:07:30.152002 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/06 03:07:30.151997 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/06 03:07:30.152202 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/06 03:07:30.152266 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/06 03:07:59.874555 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/01/06 03:08:10.155093 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/06 03:08:10.155310 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/06 03:08:10.155466 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/06 03:08:10.155595 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/06 03:08:10.155778 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/06 03:08:15.161284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:15.161351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:16.165281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:16.165315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:18.168902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:18.168931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:22.175373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:22.175400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:29.874480 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=55
2022/01/06 03:08:30.183349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:30.183397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:46.190588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:46.190634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:08:59.874395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:09:18.198171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:09:18.198215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:09:29.874479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:09:59.874460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:10:18.205114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:10:18.205143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:10:29.874490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:10:59.874413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:11:18.212325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:11:18.212369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:11:29.874362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:11:59.874442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:12:18.220136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:12:18.220163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:12:29.874384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:12:59.874409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:13:15.164084 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/06 03:13:18.227609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:13:18.227746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:13:29.874425 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/06 03:13:30.165089 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/06 03:13:30.165090 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/06 03:13:30.165107 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/06 03:13:59.874522 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/01/06 03:14:18.234518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:14:18.234546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:14:29.874435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:14:59.874699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:15:18.242299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:15:18.242330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:15:29.874408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:15:59.874515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:16:18.249289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:16:18.249323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:16:29.874448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:16:59.874429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:17:18.256697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:17:18.256728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:17:29.874707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:17:59.874492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:18:18.263747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:18:18.263858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:18:29.874408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:18:59.874428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:19:18.271862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:19:18.271898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:19:29.874424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:19:59.874473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:20:18.277909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:20:18.277944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:20:29.874425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:20:59.874537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:21:18.284709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:21:18.284759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:21:29.874392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:21:59.874462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:22:18.291636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:22:18.291674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:22:29.874524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:22:59.874448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:23:18.300744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:23:18.300784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:23:29.874383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:23:59.874467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:24:18.307645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:24:18.307677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:24:29.874492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:24:59.874401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:25:18.314892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:25:18.314925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:25:29.874408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:25:59.874404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:26:18.322594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:26:18.322648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:26:29.874419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:26:59.874627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:27:18.330386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:27:18.330426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:27:29.874431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:27:59.874544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:28:18.337619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:28:18.337649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:28:29.874402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:28:59.874560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:29:18.344992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:29:18.345033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:29:29.874404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:29:59.874406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:30:18.352091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:30:18.352123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:30:29.874443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:30:59.874440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:31:18.359111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:31:18.359148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:31:29.874394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:31:59.874392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:32:18.366561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:32:18.366596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:32:29.874396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:32:59.874431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:33:18.373234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:33:18.373278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:33:29.874405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:33:59.874380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:34:18.379919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:34:18.379951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:34:29.874412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:34:59.874572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:35:18.386919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:35:18.386948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:35:29.874416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:35:59.874475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:36:18.394931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:36:18.394966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:36:29.874372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:36:59.874555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:37:18.401453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:37:18.401495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:37:29.874407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:37:59.874375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:38:18.408664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:38:18.408697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:38:29.874510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:38:59.874463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:39:18.415527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:39:18.415555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:39:29.874475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:39:59.874476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:40:18.422325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:40:18.422358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:40:29.874425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:40:59.874449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:41:18.428943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:41:18.428989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:41:29.874388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:41:59.874429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:42:18.435691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:42:18.435726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:42:29.874414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:42:59.874387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:43:18.443260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:43:18.443298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:43:29.874463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:43:59.874422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:44:18.450174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:44:18.450212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:44:29.874456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:44:59.874456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:45:18.456400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:45:18.456429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:45:29.874455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:45:59.874430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:46:18.463364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:46:18.463401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:46:29.874483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:46:59.874421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:47:18.474424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:47:18.474457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:47:29.874426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:47:59.874472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:48:18.481101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:48:18.481152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:48:29.874432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:48:59.874460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:49:18.487150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:49:18.487178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:49:29.874396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:49:59.874448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:50:18.493989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:50:18.494033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:50:29.874379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:50:59.874487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:51:18.500556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:51:18.500595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:51:29.874497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:51:59.874386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:52:18.507673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:52:18.507710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:52:29.874510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:52:59.874477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:53:18.515019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:53:18.515095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:53:29.874437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:53:59.874466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:54:18.521474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:54:18.521502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:54:29.874466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:54:59.874542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:55:18.527508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:55:18.527536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:55:29.874529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:55:59.874426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:56:18.534403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:56:18.534437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:56:29.874426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:56:59.874431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:57:18.541336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:57:18.541381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:57:29.874421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:57:59.874415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:58:18.547755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:58:18.547791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:58:29.874417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:58:59.874437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:59:18.554839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:59:18.554875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 03:59:29.874424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 03:59:59.874439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:00:18.603491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:00:18.603543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:00:29.874489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:00:59.874520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:01:18.610742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:01:18.610788 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:01:29.874433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:01:59.874419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:02:18.617855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:02:18.617890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:02:29.874514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:02:59.874391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:03:18.624190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:03:18.624217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:03:29.874474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:03:59.874427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:04:18.631033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:04:18.631075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:04:29.874478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:04:59.874419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:05:18.638295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:05:18.638326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:05:29.874401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:05:59.874436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:06:18.645284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:06:18.645311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:06:29.874437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:06:59.874466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:07:18.651990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:07:18.652038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:07:29.874485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:07:59.874424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:08:18.659263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:08:18.659298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:08:29.874397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:08:59.874443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:09:18.666329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:09:18.666359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:09:29.874401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:09:59.874389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:10:18.673941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:10:18.673971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:10:29.874410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:10:59.874464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:11:18.681600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:11:18.681640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:11:29.874436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:11:59.874414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:12:18.688026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:12:18.688057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:12:29.874458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:12:59.874497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:13:18.694809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:13:18.694844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:13:29.874403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:13:59.874396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:14:18.701651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:14:18.701687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:14:29.874380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:14:59.874446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:15:18.708899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:15:18.708936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:15:29.874461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:15:59.874431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:16:18.715483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:16:18.715517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:16:29.874462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:16:59.874438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:17:18.722090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:17:18.722133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:17:29.874430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:17:59.874370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:18:18.728639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:18:18.728684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:18:29.874494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:18:59.874382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:19:18.735323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:19:18.735358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:19:29.874362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:19:59.874477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:20:18.742351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:20:18.742382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:20:29.874400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:20:59.874422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:21:18.749701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:21:18.749734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:21:29.874408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:21:59.874462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:22:18.756954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:22:18.756986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:22:29.874443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:22:59.874460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:23:18.764865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:23:18.764904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:23:29.874409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:23:59.874453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:24:18.771240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:24:18.771274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:24:29.874500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:24:59.874539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:25:18.777941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:25:18.777970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:25:29.874430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:25:59.874420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:26:18.784975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:26:18.785013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:26:29.874400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:26:59.874410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:27:18.791511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:27:18.791536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:27:29.874422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:27:59.874399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:28:18.798284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:28:18.798316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:28:29.874493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:28:59.874451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:29:18.805152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:29:18.805196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:29:29.874386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:29:59.874373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:30:18.812786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:30:18.812833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:30:29.874404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:30:59.874450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:31:18.820321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:31:18.820358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:31:29.874423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:31:59.874373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/06 04:32:18.831819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/06 04:32:18.831865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host