By type
2022/03/09 11:49:30.866529 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/09 11:49:30.866600 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 11:49:30.866750 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 11:49:30.866865 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 11:49:30.867010 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-qck9t
2022/03/09 11:49:30.867276 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 11:49:30.867298 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 11:49:30.868148 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 11:49:30.868856 beat.go:221: INFO filebeat start running.
2022/03/09 11:49:30.869020 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 11:49:30.876255 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 11:49:30.876332 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 11:49:30.876373 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 11:49:30.876547 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 11:49:30.876660 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/09 11:49:30.876690 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 11:49:30.876702 registrar.go:236: INFO Starting Registrar
2022/03/09 11:49:30.876735 sync.go:41: INFO Start sending events to output
2022/03/09 11:49:30.876775 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 11:49:50.879138 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/09 11:49:50.879295 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/09 11:49:50.879393 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/09 11:49:50.879657 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/09 11:49:50.879793 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/09 11:49:55.897389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:55.897424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:56.902259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:56.902295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:58.910372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:58.910404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:00.868482 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=76 registrar.writes=1
2022/03/09 11:50:02.918405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:02.918439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:10.927994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:10.928090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:26.945739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:26.945784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:30.869782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:50:58.962536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:58.962572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:51:00.868486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:51:30.868466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:51:58.989987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:51:58.990031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:52:00.868485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:52:30.868520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:52:59.008515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:52:59.008552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:53:00.868443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:53:30.868476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:53:59.028827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:53:59.028877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:54:00.868547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:54:30.868393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:54:55.889561 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 11:54:59.046240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:54:59.046275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:55:00.868487 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/09 11:55:30.868423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:55:59.064215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:55:59.064253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:56:00.868475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:56:30.868444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:56:59.081491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:56:59.081550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:57:00.868517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:57:30.868450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:57:59.103656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:57:59.103696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:58:00.868472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:58:30.868728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:58:59.122831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:58:59.122881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:59:00.868521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:59:30.868396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:59:59.140983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:59:59.141035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:00:00.868476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:00:30.868513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:00:59.161970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:00:59.162007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:01:00.868433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:01:30.868536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:01:59.188059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:01:59.188123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:02:00.868540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:02:30.868483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:02:59.213362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:02:59.213395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:03:00.868516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:03:30.868648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:03:59.231216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:03:59.231266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:04:00.868533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:04:30.868471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:04:59.251680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:04:59.251718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:05:00.868463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:05:30.868555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:05:59.269751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:05:59.269967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:06:00.868454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:06:30.868509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:06:59.288090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:06:59.288139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:07:00.868584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:07:30.868699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:07:59.307062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:07:59.307110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:08:00.868473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:08:30.868464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:08:59.325727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:08:59.325763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:09:00.868393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:09:30.868558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:09:59.347488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:09:59.347531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:10:00.868465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:10:30.868531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:10:59.365711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:10:59.365747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:11:00.868463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:11:30.868703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:11:59.383971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:11:59.384202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:12:00.868599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:12:30.868542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:12:59.402564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:12:59.402697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:13:00.868399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:13:30.868447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:13:59.418466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:13:59.418505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:14:00.868528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:14:30.868483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:14:59.437493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:14:59.437607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:15:00.868468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:15:30.868500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:15:59.456092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:15:59.456173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:16:00.868470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:16:30.868415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:16:59.474272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:16:59.474309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:17:00.868427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:17:30.868472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:17:59.492411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:17:59.492625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:18:00.868437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:18:30.868476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:18:59.509802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:18:59.509831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:19:00.868374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:19:30.868408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:19:59.529376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:19:59.529408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:20:00.868461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:20:30.868577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:20:59.546436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:20:59.546483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:21:00.868545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:21:30.868507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:21:59.562411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:21:59.562450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:22:00.868463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:22:30.868453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:22:59.580717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:22:59.580757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:23:00.868433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:23:30.868469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:23:59.597846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:23:59.597886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:24:00.868468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:24:30.868486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:24:59.613961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:24:59.614003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:25:00.868522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:25:30.868473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:25:59.635981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:25:59.636017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:26:00.868578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:26:30.868540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:26:59.656912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:26:59.656956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:27:00.868438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:27:30.868483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:27:59.674779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:27:59.674918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:28:00.868467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:28:30.868451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:28:59.693398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:28:59.693435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:29:00.868501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:29:30.868422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:29:59.710330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:29:59.710476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:30:00.868434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:30:30.868469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:30:59.726670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:30:59.726705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:31:00.868462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:31:30.868488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:31:59.742909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:31:59.742955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:32:00.868417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:32:30.868604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:32:59.761991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:32:59.762027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:33:00.868503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:33:30.868417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:33:59.780200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:33:59.780238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:34:00.868508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:34:30.868434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:34:59.798911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:34:59.798948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:35:00.868510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:35:30.868430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:35:59.817866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:35:59.817904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:36:00.868490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:36:30.868460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:36:59.836193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:36:59.836235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:37:00.868510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:37:30.868507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:37:59.854768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:37:59.854812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:38:00.868535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:38:30.868606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:38:59.878029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:38:59.878085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:39:00.868653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:39:30.868512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:39:59.885094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:39:59.885142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:40:00.868542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:40:30.868435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:40:59.904428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:40:59.904465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:41:00.868573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:41:30.868471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:41:59.922901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:41:59.922957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:42:00.868431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:42:30.868474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:42:59.940562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:42:59.940615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:43:00.868465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:43:30.868473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:43:59.957009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:43:59.957044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:44:00.868424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:44:30.868595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:44:59.974799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:44:59.974875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:45:00.868567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:45:30.868496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:45:59.993774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:45:59.993853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:46:00.868485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:46:30.868461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:47:00.010422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:47:00.010467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:47:00.868496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:47:30.868434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:48:00.027712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:48:00.027940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:48:00.868427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:48:30.868463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:49:00.045953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:49:00.046000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:49:00.868500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:49:30.868405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:50:00.063539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:50:00.063780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:50:00.868592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:50:30.868437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:51:00.082564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:51:00.082608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:51:00.868534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:51:30.868558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:52:00.101150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:52:00.101189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:52:00.868490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:52:30.868492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:53:00.119317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:53:00.119398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:53:00.868721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:53:30.868462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:54:00.136118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:54:00.136339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:54:00.868462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:54:30.868516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:55:00.154546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:55:00.154588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:55:00.868496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:55:30.868507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:56:00.173738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:56:00.173778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:56:00.868557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:56:30.868485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:57:00.191937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:57:00.191998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:57:00.868493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:57:30.868651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:58:00.211485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:58:00.211546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:58:00.868467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:58:30.868508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:59:00.230498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:59:00.230566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:59:00.868596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:59:30.868524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:00:00.250601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:00:00.250654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:00:00.868469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:00:30.868478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:01:00.270586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:01:00.270636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:01:00.868555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:01:30.868381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:02:00.292026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:02:00.292075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:02:00.868455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:02:30.868449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:03:00.310261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:03:00.310298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:03:00.868482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:03:30.868642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:04:00.328832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:04:00.328888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:04:00.868574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:04:30.868462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:05:00.349748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:05:00.349807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:05:00.868481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:05:30.868420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:06:00.372590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:06:00.372637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:06:00.868478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:06:30.868465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:07:00.389306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:07:00.389337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:07:00.868420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:07:30.868472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:08:00.408838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:08:00.408875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:08:00.868491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:08:30.868458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:09:00.431212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:09:00.431813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:09:00.868416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:09:30.868533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:10:00.453946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:10:00.454007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:10:00.868533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:10:30.868579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:11:00.474670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:11:00.474724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:11:00.868511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:11:30.868491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:12:00.492152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:12:00.492327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:12:00.868454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:12:30.868426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:13:00.511494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:13:00.511547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:13:00.868631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:13:30.868483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:14:00.530771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:14:00.530826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:14:00.868407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:14:30.868411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:15:00.549480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:15:00.549564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:15:00.868463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:15:30.868400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:16:00.567874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:16:00.568043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:16:00.868502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:16:30.868562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:17:00.586338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:17:00.586395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:17:00.868532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:17:30.868481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:18:00.606968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:18:00.607019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:18:00.868659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:18:30.868460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:19:00.625751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:19:00.625794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:19:00.868468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:19:30.868533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:20:00.644709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:20:00.644744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:20:00.868466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:20:30.868482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:21:00.661402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:21:00.661456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:21:00.868500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:21:30.868438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:22:00.679635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:22:00.679668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:22:00.868431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:22:30.868458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:23:00.697028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:23:00.697066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:23:00.868437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:23:30.868520 metrics.go:34: INFO No non-zero metrics in the last 30s