By type
2022/02/05 03:11:34.923072 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/02/05 03:11:34.923173 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/05 03:11:34.923221 metrics.go:23: INFO Metrics logging every 30s
2022/02/05 03:11:34.923296 logstash.go:90: INFO Max Retries set to: 3
2022/02/05 03:11:34.923388 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/05 03:11:34.923532 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-5br65
2022/02/05 03:11:34.923735 async.go:63: INFO Flush Interval set to: 1s
2022/02/05 03:11:34.923786 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/05 03:11:34.924234 beat.go:221: INFO filebeat start running.
2022/02/05 03:11:34.924311 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/05 03:11:34.952769 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/05 03:11:34.952872 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/05 03:11:34.952929 crawler.go:38: INFO Loading Prospectors: 1
2022/02/05 03:11:34.953037 registrar.go:236: INFO Starting Registrar
2022/02/05 03:11:34.953186 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/05 03:11:34.953222 sync.go:41: INFO Start sending events to output
2022/02/05 03:11:34.953329 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/05 03:11:34.953376 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/05 03:11:34.953341 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/05 03:11:54.955884 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/02/05 03:11:54.956171 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/02/05 03:11:54.956724 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/02/05 03:11:54.956977 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/02/05 03:11:54.957123 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/02/05 03:11:59.963674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:11:59.963717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:00.968489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:00.968532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:02.973440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:02.973523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:04.923844 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/02/05 03:12:06.986098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:06.986135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:14.993078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:14.993125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:31.001708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:31.001742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:12:34.923589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:13:03.012240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:13:03.012299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:13:04.923628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:13:34.923773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:14:03.023411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:14:03.023454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:14:04.923525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:14:34.923543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:15:03.032952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:15:03.033008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:15:04.923573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:15:34.923553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:16:03.044063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:16:03.044104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:16:04.923531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:16:34.923768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:16:59.968435 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/05 03:17:03.052546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:17:03.052583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:17:04.923638 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/05 03:17:34.923584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:18:03.060028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:18:03.060066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:18:04.923631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:18:34.923534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:19:03.071246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:19:03.071290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:19:04.923622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:19:34.923796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:20:03.082031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:20:03.082077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:20:04.923608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:20:34.923590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:21:03.091848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:21:03.091887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:21:04.923682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:21:34.924361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:22:03.102881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:22:03.102919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:22:04.923752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:22:34.923623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:23:03.111056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:23:03.111089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:23:04.923705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:23:34.923560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:24:03.121947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:24:03.122026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:24:04.923758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:24:34.923651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:25:03.132481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:25:03.132539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:25:04.923557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:25:34.923690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:26:03.143799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:26:03.143859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:26:04.923582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:26:34.923739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:27:03.152644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:27:03.152676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:27:04.923615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:27:34.923815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:28:03.161446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:28:03.161611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:28:04.923580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:28:34.923666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:29:03.170430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:29:03.170497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:29:04.923578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:29:34.923583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:30:03.180343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:30:03.180386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:30:04.923630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:30:34.923645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:31:03.189689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:31:03.189723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:31:04.923634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:31:34.923832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:32:03.199553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:32:03.199610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:32:04.923653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:32:34.923724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:33:03.208081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:33:03.208128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:33:04.923634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:33:34.923691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:34:03.215286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:34:03.215343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:34:04.923654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:34:34.923718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:35:03.222936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:35:03.222965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:35:04.923570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:35:34.923758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:36:03.231882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:36:03.231986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:36:04.923634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:36:34.923528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:37:03.242590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:37:03.242641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:37:04.923597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:37:34.923621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:38:03.251451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:38:03.251497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:38:04.923570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:38:34.923664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:39:03.261390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:39:03.261419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:39:04.923677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:39:34.923649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:40:03.272398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:40:03.272463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:40:04.923452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:40:34.923546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:41:03.281798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:41:03.281824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:41:04.923660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:41:34.923566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:42:03.292934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:42:03.292992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:42:04.923442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:42:34.923614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:43:03.303350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:43:03.303411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:43:04.923619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:43:34.923561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:44:03.313484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:44:03.313525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:44:04.923552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:44:34.923595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:45:03.322502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:45:03.322555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:45:04.923622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:45:34.923539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:46:03.332095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:46:03.332304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:46:04.923516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:46:34.923710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:47:03.342762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:47:03.342826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:47:04.923652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:47:34.923651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:48:03.352430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:48:03.352608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:48:04.923607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:48:34.923733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:49:03.361025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:49:03.361081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:49:04.923582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:49:34.923518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:50:03.369957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:50:03.370006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:50:04.923570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:50:34.923703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:51:03.379866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:51:03.379995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:51:04.923573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:51:34.923527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:52:03.390601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:52:03.390652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:52:04.923614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:52:34.923577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:53:03.400846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:53:03.400898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:53:04.923594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:53:34.923651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:54:03.410177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:54:03.410219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:54:04.923585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:54:34.923564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:55:03.419028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:55:03.419084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:55:04.923673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:55:34.923552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:56:03.428297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:56:03.428377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:56:04.923670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:56:34.926770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:57:03.440296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:57:03.440356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:57:04.923602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:57:34.923717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:58:03.449837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:58:03.449878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:58:04.923617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:58:34.923719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:59:03.457987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:59:03.458034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 03:59:04.923599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 03:59:34.923632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:00:03.466462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:00:03.466554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:00:04.923625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:00:34.923640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:01:03.477051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:01:03.477135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:01:04.923613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:01:34.923662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:02:03.486337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:02:03.486407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:02:04.923568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:02:34.923625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:03:03.494604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:03:03.494649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:03:04.923536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:03:34.923675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:04:03.503226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:04:03.503271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:04:04.923602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:04:34.923683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:05:03.514505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:05:03.514570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:05:04.923672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:05:34.923571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:06:03.522868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:06:03.522901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:06:04.923701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:06:34.923745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:07:03.533071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:07:03.533119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:07:04.923638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:07:34.923545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:08:03.542161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:08:03.542202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:08:04.923631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:08:34.923782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:09:03.553054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:09:03.553107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:09:04.923663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:09:34.923570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:10:03.562732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:10:03.562775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:10:04.923649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:10:34.923586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:11:03.572609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:11:03.572810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:11:04.923718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:11:34.923668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:12:03.582640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:12:03.582690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:12:04.923573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:12:34.923723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:13:03.595088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:13:03.595138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:13:04.923639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:13:34.923653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:14:03.604641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:14:03.604684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:14:04.923671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:14:34.923627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:15:03.613982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:15:03.614036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:15:04.923617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:15:34.923596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:16:03.622392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:16:03.622435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:16:04.923628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:16:34.923897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:17:03.632133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:17:03.632164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:17:04.923770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:17:34.923647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:18:03.641057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:18:03.641106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:18:04.923656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:18:34.923682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:19:03.652589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:19:03.652644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:19:04.923604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:19:34.923655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:20:03.661511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:20:03.661561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:20:04.923616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:20:34.923545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:21:03.671558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:21:03.671585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:21:04.923595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:21:34.923719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:22:03.680944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:22:03.680999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:22:04.923691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:22:34.923586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:23:03.690493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:23:03.690566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:23:04.923613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:23:34.923668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:24:03.699190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:24:03.699236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:24:04.923633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:24:34.923553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:25:03.709438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:25:03.709474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:25:04.923641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:25:34.923645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:26:03.718388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:26:03.718440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:26:04.923510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:26:34.923636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:27:03.727704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:27:03.727756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:27:04.923526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:27:34.923633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:28:03.735377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:28:03.735434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:28:04.923662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:28:34.923660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:29:03.743176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:29:03.743215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:29:04.923565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:29:34.923647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:30:03.753056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:30:03.753122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:30:04.923646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:30:34.923586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:31:03.762928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:31:03.762976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:31:04.923555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:31:34.923705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:32:03.772735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:32:03.772773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:32:04.923521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:32:34.923704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:33:03.782933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:33:03.782992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:33:04.923653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:33:34.923569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:34:03.792761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:34:03.792807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:34:04.923627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:34:34.923653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:35:03.804223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:35:03.804264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:35:04.923619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:35:34.923558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:36:03.814922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:36:03.814971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:36:04.923919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:36:34.923681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:37:03.824933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:37:03.824996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:37:04.923532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:37:34.923607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:38:03.835064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:38:03.835107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:38:04.923622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:38:34.923823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:39:03.846871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:39:03.846915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:39:04.923626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:39:34.923676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:40:03.859958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:40:03.859998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:40:04.923549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:40:34.923771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:41:03.867538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:41:03.867571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:41:04.923606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:41:34.923671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:42:03.879152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:42:03.879222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:42:04.923525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:42:34.923642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:43:03.888483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:43:03.888608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:43:04.923587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:43:34.923579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:44:03.899556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:44:03.899619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:44:04.923550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:44:34.923621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:45:03.910071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:45:03.910126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:45:04.923509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:45:34.923660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:46:03.918467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:46:03.918570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:46:04.923624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:46:34.923731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:47:03.929223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:47:03.929257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:47:04.923595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:47:34.923572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:48:03.938752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:48:03.938806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:48:04.923622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:48:34.923535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:49:03.948238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:49:03.948279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:49:04.923721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:49:34.923712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:50:03.959088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:50:03.959147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:50:04.923660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:50:34.923647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:51:03.968264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:51:03.968305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:51:04.923687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:51:34.923583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:52:03.978804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:52:03.978985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:52:04.923617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:52:34.923638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:53:03.988787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:53:03.988832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:53:04.923539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:53:34.923689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:54:03.998378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:54:03.998417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:54:04.923575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:54:34.923653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:55:04.010430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:55:04.010482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:55:04.923680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:55:34.923595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:56:04.020671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:56:04.020710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:56:04.923578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:56:34.923637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:57:04.028976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:57:04.029021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:57:04.923523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:57:34.923573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:58:04.040151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:58:04.040182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:58:04.923646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:58:34.923802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:59:04.049390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:59:04.049432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 04:59:04.923613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 04:59:34.923846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:00:04.059779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:00:04.059891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:00:04.923592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:00:34.923531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:01:04.070022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:01:04.070080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:01:04.923566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:01:34.923719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:02:04.079724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:02:04.079811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:02:04.923540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:02:34.923810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:03:04.089377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:03:04.089429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:03:04.923626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:03:34.923641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:04:04.102076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:04:04.102128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:04:04.923629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:04:34.923738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:05:04.112031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:05:04.112119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:05:04.923619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:05:34.923867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:06:04.122895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:06:04.122981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:06:04.923597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:06:34.923636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:07:04.133418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:07:04.133468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:07:04.923574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:07:34.923677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:08:04.147075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:08:04.147102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:08:04.923604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:08:34.923524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:09:04.157524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:09:04.157586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:09:04.923739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:09:34.923769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:10:04.169070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:10:04.169123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:10:04.923447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:10:34.923715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:11:04.178721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:11:04.178765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:11:04.923697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:11:34.923739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:12:04.190604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:12:04.190663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/05 05:12:04.923825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/05 05:12:34.923846 metrics.go:34: INFO No non-zero metrics in the last 30s