By type
2022/03/18 03:20:36.410323 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/18 03:20:36.410394 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/18 03:20:36.410764 logstash.go:90: INFO Max Retries set to: 3
2022/03/18 03:20:36.411002 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/18 03:20:36.411250 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-bk2qq
2022/03/18 03:20:36.411612 async.go:63: INFO Flush Interval set to: 1s
2022/03/18 03:20:36.411637 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/18 03:20:36.412466 beat.go:221: INFO filebeat start running.
2022/03/18 03:20:36.412546 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/18 03:20:36.417193 metrics.go:23: INFO Metrics logging every 30s
2022/03/18 03:20:36.422361 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/18 03:20:36.422550 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/18 03:20:36.422651 crawler.go:38: INFO Loading Prospectors: 1
2022/03/18 03:20:36.422741 registrar.go:236: INFO Starting Registrar
2022/03/18 03:20:36.422814 sync.go:41: INFO Start sending events to output
2022/03/18 03:20:36.422978 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/18 03:20:36.423396 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/18 03:20:36.423639 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/18 03:20:36.423688 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/18 03:20:56.428114 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/18 03:20:56.429139 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/18 03:20:56.429301 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/18 03:20:56.429468 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/18 03:20:56.429582 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/18 03:21:01.467955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:01.468003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:02.472233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:02.472271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:04.484848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:04.485240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:06.417730 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=70 registrar.writes=1
2022/03/18 03:21:08.567585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:08.567636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:16.586567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:16.586622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:32.618909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:32.619109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:36.417565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:22:04.624362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:22:04.624416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:22:06.417563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:22:36.417636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:23:04.629868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:23:04.629934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:23:06.417586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:23:36.417678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:24:04.635448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:24:04.635557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:24:06.417619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:24:36.417512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:25:04.641357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:25:04.641546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:25:06.418127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:25:36.417640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:26:01.487990 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/18 03:26:04.645919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:26:04.645963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:26:06.417658 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/18 03:26:36.417674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:27:04.650236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:27:04.650298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:27:06.417634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:27:36.417549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:28:04.669536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:28:04.669606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:28:06.417568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:28:36.417671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:29:04.680208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:29:04.680258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:29:06.419904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:29:36.417657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:30:04.693681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:30:04.693739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:30:06.417557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:30:36.418794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:31:04.701332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:31:04.701379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:31:06.417577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:31:36.417641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:32:04.708575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:32:04.708626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:32:06.417789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:32:36.417613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:33:04.716478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:33:04.716523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:33:06.417568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:33:36.417535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:34:04.720205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:34:04.720240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:34:06.417652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:34:36.418084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:35:04.726197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:35:04.726463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:35:06.417702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:35:36.417780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:36:04.739168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:36:04.739206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:36:06.417654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:36:36.417608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:37:04.742633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:37:04.742692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:37:06.417566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:37:36.417632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:38:04.756085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:38:04.756165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:38:06.417994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:38:36.417738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:39:04.771159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:39:04.771225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:39:06.417675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:39:36.417569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:40:04.783141 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:40:04.783191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:40:06.417550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:40:36.417496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:41:04.804729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:41:04.804775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:41:06.417575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:41:36.417588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:42:04.832399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:42:04.832724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:42:06.417570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:42:36.417641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:43:04.840262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:43:04.840328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:43:06.417654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:43:36.417685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:44:04.847702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:44:04.847737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:44:06.417554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:44:36.417535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:45:04.861527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:45:04.861591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:45:06.417660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:45:36.419932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:46:04.877314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:46:04.877388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:46:06.417592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:46:36.417626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:47:04.891824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:47:04.891860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:47:06.417661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:47:36.417641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:48:04.906525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:48:04.906573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:48:06.417516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:48:36.419580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:49:04.967667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:49:04.967710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:49:06.417612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:49:36.417568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:50:04.984978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:50:04.985030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:50:06.420716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:50:36.417505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:51:05.027459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:51:05.027506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:51:06.417560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:51:36.417692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:52:05.050085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:52:05.050154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:52:06.417733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:52:36.417539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:53:05.065214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:53:05.065271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:53:06.417810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:53:36.417801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:54:05.075698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:54:05.076077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:54:06.417833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:54:36.417548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:55:05.102466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:55:05.102525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:55:06.417631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:55:36.417551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:56:05.110903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:56:05.110937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:56:06.417635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:56:36.417655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:57:05.121523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:57:05.121587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:57:06.417655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:57:36.417659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:58:05.131794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:58:05.131843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:58:06.417542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:58:36.417625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:59:05.146140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:59:05.146246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:59:06.417551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:59:36.417885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:00:05.157461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:00:05.157511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:00:06.417647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:00:36.417691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:01:05.167794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:01:05.168075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:01:06.417644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:01:36.417682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:02:05.182072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:02:05.182137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:02:06.417527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:02:36.419709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:03:05.190429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:03:05.190483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:03:06.417547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:03:36.417613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:04:05.198451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:04:05.198494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:04:06.417583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:04:36.417567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:05:05.207414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:05:05.207492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:05:06.417642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:05:36.417990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:06:05.218833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:06:05.218883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:06:06.417981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:06:36.417598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:07:05.229315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:07:05.229384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:07:06.417642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:07:36.417604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:08:05.244602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:08:05.244640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:08:06.417601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:08:36.417608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:09:05.252413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:09:05.252608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:09:06.417534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:09:36.417477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:10:05.267146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:10:05.267207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:10:06.417575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:10:36.417727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:11:05.280536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:11:05.280611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:11:06.417694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:11:36.417552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:12:05.294451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:12:05.294485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:12:06.417534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:12:36.417477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:13:05.311081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:13:05.311113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:13:06.417505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:13:36.417552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:14:05.325222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:14:05.325275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:14:06.417509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:14:36.417537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:15:05.333816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:15:05.333919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:15:06.417551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:15:36.417612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:16:05.340833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:16:05.340885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:16:06.417591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:16:36.417621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:17:05.357380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:17:05.357441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:17:06.417740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:17:36.417545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:18:05.381381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:18:05.381433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:18:06.417521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:18:36.417554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:19:05.390561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:19:05.390612 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:19:06.417585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:19:36.417590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:20:05.403347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:20:05.403384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:20:06.417646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:20:36.417654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:21:05.411467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:21:05.411633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:21:06.417598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:21:36.417584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:22:05.421673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:22:05.421790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:22:06.417772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:22:36.417675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:23:05.430274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:23:05.430316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:23:06.417611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:23:36.417663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:24:05.442227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:24:05.442316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:24:06.417539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:24:36.417516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:25:05.448396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:25:05.448458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:25:06.417628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:25:36.417859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:26:05.484778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:26:05.484824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:26:06.417530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:26:36.417483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:27:05.492893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:27:05.492946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:27:06.417594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:27:36.417641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:28:05.508627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:28:05.508712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:28:06.417613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:28:36.417545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:29:05.518400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:29:05.518478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:29:06.417686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:29:36.417580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:30:05.530707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:30:05.530764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:30:06.417511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:30:36.417585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:31:05.553593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:31:05.553626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:31:06.417567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:31:36.417590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:32:05.566789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:32:05.566839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:32:06.417588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:32:36.417497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:33:05.577836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:33:05.577882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:33:06.417562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:33:36.417529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:34:05.594243 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:34:05.594299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:34:06.419311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:34:36.417657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:35:05.603724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:35:05.603771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:35:06.417611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:35:36.417678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:36:05.613346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:36:05.613526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:36:06.418339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:36:36.417637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:37:05.624077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:37:05.624110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:37:06.417539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:37:36.417760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:38:05.636669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:38:05.636707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:38:06.417495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:38:36.417609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:39:05.650190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:39:05.650245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:39:06.420035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:39:36.417595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:40:05.661628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:40:05.661837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:40:06.417533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:40:36.417721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:41:05.668767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:41:05.668816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:41:06.417589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:41:36.417734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:42:05.677546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:42:05.677598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:42:06.417611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:42:36.417566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:43:05.686549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:43:05.686593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:43:06.417590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:43:36.417855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:44:05.695917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:44:05.695976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:44:06.417518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:44:36.417587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:45:05.711673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:45:05.711735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:45:06.417589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:45:36.417571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:46:05.723416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:46:05.723456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:46:06.417547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:46:36.417678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:47:05.734880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:47:05.734961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:47:06.417566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:47:36.417569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:48:05.744015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:48:05.744092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:48:06.417523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:48:36.417804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:49:05.752214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:49:05.752266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:49:06.417604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:49:36.417499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:50:05.782772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:50:05.782812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:50:06.417665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:50:36.417511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:51:05.792930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:51:05.792966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:51:06.417545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:51:36.417534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:52:05.800596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:52:05.800646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:52:06.417567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:52:36.417672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:53:05.825807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:53:05.825850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:53:06.417589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:53:36.417842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:54:05.835103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:54:05.835196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:54:06.417599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:54:36.417634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:55:05.848679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:55:05.848950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:55:06.417505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:55:36.417563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:56:05.862524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:56:05.862567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:56:06.417678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:56:36.417582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:57:05.872045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:57:05.872109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:57:06.417550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:57:36.417493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:58:05.879497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:58:05.879537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:58:06.417606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:58:36.417593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:59:05.891891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:59:05.891951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:59:06.417561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:59:36.417615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:00:05.909365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:00:05.909493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:00:06.417856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:00:36.417729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:01:05.923263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:01:05.923325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:01:06.417700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:01:36.417596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:02:05.944529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:02:05.944738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:02:06.417787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:02:36.417580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:03:05.967199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:03:05.967272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:03:06.417555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:03:36.417628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:04:05.976992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:04:05.977040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:04:06.417654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:04:36.417531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:05:05.985666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:05:05.985716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:05:06.417508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:05:36.417880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:06:05.998251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:06:05.998297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:06:06.417536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:06:36.417598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:07:06.005698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:07:06.005745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:07:06.417658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:07:36.417574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:08:06.021467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:08:06.021515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:08:06.417555 metrics.go:34: INFO No non-zero metrics in the last 30s