2022/03/25 02:24:52.007098 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/25 02:24:52.007133 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/25 02:24:52.007219 metrics.go:23: INFO Metrics logging every 30s
2022/03/25 02:24:52.007215 logstash.go:90: INFO Max Retries set to: 3
2022/03/25 02:24:52.007327 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/25 02:24:52.007530 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-8xdrp
2022/03/25 02:24:52.007741 async.go:63: INFO Flush Interval set to: 1s
2022/03/25 02:24:52.007764 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/25 02:24:52.008128 beat.go:221: INFO filebeat start running.
2022/03/25 02:24:52.008174 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/25 02:24:52.306139 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/25 02:24:52.306196 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/25 02:24:52.306259 crawler.go:38: INFO Loading Prospectors: 1
2022/03/25 02:24:52.306373 registrar.go:236: INFO Starting Registrar
2022/03/25 02:24:52.306411 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/25 02:24:52.306421 sync.go:41: INFO Start sending events to output
2022/03/25 02:24:52.306516 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/25 02:24:52.306536 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/25 02:24:52.306599 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/25 02:25:22.007524 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/25 02:25:32.308595 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/25 02:25:32.308659 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/25 02:25:32.308898 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/25 02:25:32.309133 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/25 02:25:32.309429 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/25 02:25:37.316749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:37.316782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:38.319441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:38.319475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:40.322678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:40.322708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:44.328600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:44.328624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:52.007510 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=59
2022/03/25 02:25:52.335531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:25:52.335671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:08.341719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:08.341768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:22.007458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:26:40.349206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:40.349237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:26:52.007465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:27:22.007497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:27:40.356446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:27:40.356480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:27:52.007430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:28:22.007498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:28:40.364971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:28:40.365114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:28:52.007560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:29:22.007495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:29:40.371230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:29:40.371257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:29:52.007709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:30:22.007478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:30:37.330839 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/25 02:30:40.391759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:30:40.391788 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:30:44.318601 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/25 02:30:44.318663 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/25 02:30:47.320588 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/25 02:30:52.007527 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-4
2022/03/25 02:31:22.007457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:31:40.399197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:31:40.399240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:31:52.007611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:32:22.007557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:32:40.742786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:32:40.742910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:32:52.007512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:33:22.007472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:33:40.763497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:33:40.763531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:33:52.007439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:34:22.007468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:34:40.770716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:34:40.770748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:34:52.007555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:35:22.007525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:35:40.778115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:35:40.778144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:35:52.007534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:36:22.007443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:36:40.785319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:36:40.785358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:36:52.007456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:37:22.007480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:37:40.793347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:37:40.793379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:37:52.007480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:38:22.007481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:38:40.799578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:38:40.799607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:38:52.007789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:39:22.007455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:39:40.808134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:39:40.808169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:39:52.007457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:40:22.007439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:40:40.813648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:40:40.813676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:40:52.007423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:41:22.007427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:41:40.820798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:41:40.820839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:41:52.007559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:42:22.007438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:42:40.828302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:42:40.828341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:42:52.007453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:43:22.007489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:43:40.835118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:43:40.835149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:43:52.007470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:44:22.007418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:44:40.841686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:44:40.841721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:44:52.007681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:45:22.007523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:45:40.848328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:45:40.848364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:45:52.007444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:46:22.007531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:46:40.854651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:46:40.854684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:46:52.007460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:47:22.007458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:47:40.860801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:47:40.860836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:47:52.007490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:48:22.007552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:48:40.868179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:48:40.868224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:48:52.007471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:49:22.007438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:49:40.874839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:49:40.874877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:49:52.007426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:50:22.007478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:50:40.881865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:50:40.881896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:50:52.007440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:51:22.007445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:51:40.888418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:51:40.888449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:51:52.007446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:52:22.007485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:52:40.894288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:52:40.894324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:52:52.007476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:53:22.007500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:53:40.900161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:53:40.900195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:53:52.007470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:54:22.007506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:54:40.906087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:54:40.906124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:54:52.008791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:55:22.007536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:55:40.912063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:55:40.912123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:55:52.007465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:56:22.007436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:56:40.918672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:56:40.918715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:56:52.007460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:57:22.007513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:57:40.924087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:57:40.924120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:57:52.007441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:58:22.007501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:58:40.930092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:58:40.930142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:58:52.007447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:59:22.007477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 02:59:40.935881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:59:40.935915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 02:59:52.007504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:00:22.007442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:00:40.942599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:00:40.942638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:00:52.007544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:01:22.007456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:01:40.948413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:01:40.948443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:01:52.007450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:02:22.007428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:02:40.955075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:02:40.955107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:02:52.007481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:03:22.007465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:03:40.961481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:40.961512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:52.007501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:04:22.007458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:04:40.968006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:40.968037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:52.007445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:22.007517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:40.974941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:40.974970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:52.007535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:22.007436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:40.981340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:40.981382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:52.007458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:22.007451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:40.987188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:40.987212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:52.007451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:22.007494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:40.992932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:40.992960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:52.007493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:09:22.007528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:09:40.999901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:09:40.999941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:09:52.007476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:22.007547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:41.006221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:41.006255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:52.007516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:22.007472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:41.013056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:41.013083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:52.007489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:22.007525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:41.019077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:41.019115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:52.007485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:22.007493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:41.025391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:41.025428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:52.007525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:22.007491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:41.031131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:41.031160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:52.007479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:22.007458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:41.037710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:41.037755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:52.007499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:22.007436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:41.044451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:41.044510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:52.007513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:22.007450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:41.049958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:41.049989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:52.007482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:22.007479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:41.056143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:41.056173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:52.007484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:22.007450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:41.062359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:41.062397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:52.007460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:22.007401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:41.068602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:41.068639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:52.007487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:22.007549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:41.074382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:41.074412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:52.007460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:22.007460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:41.081069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:41.081105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:52.007443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:22.007467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:41.086983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:41.087020 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:52.007492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:22.007531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:41.093358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:41.093390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:52.007440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:22.007847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:41.099166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:41.099208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:52.007451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:22.007463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:41.106228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:41.106276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:52.007497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:22.007529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:41.113017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:41.113050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:52.007466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:22.007448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:41.120319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:41.120357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:52.007475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:22.007678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:41.127148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:41.127177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:52.007535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:22.007453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:41.134863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:41.134904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:52.007503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:22.007424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:41.140809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:41.140855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:52.007433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:22.007527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:41.152751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:41.152802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:52.007533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:22.007496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:41.159036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:41.159095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:52.007448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:22.007407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:41.165906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:41.165952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:52.007490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:22.007798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:41.172274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:41.172305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:52.007448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:22.007475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:41.178356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:36:41.178396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host