By type
2022/03/08 02:34:37.392017 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/08 02:34:37.392046 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/08 02:34:37.392095 logstash.go:90: INFO Max Retries set to: 3
2022/03/08 02:34:37.392135 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/08 02:34:37.392313 metrics.go:23: INFO Metrics logging every 30s
2022/03/08 02:34:37.392358 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-qfrm5
2022/03/08 02:34:37.392500 async.go:63: INFO Flush Interval set to: 1s
2022/03/08 02:34:37.392510 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/08 02:34:37.392859 beat.go:221: INFO filebeat start running.
2022/03/08 02:34:37.392929 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/08 02:34:37.759325 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/08 02:34:37.759426 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/08 02:34:37.759490 crawler.go:38: INFO Loading Prospectors: 1
2022/03/08 02:34:37.759699 registrar.go:236: INFO Starting Registrar
2022/03/08 02:34:37.759872 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/08 02:34:37.759791 sync.go:41: INFO Start sending events to output
2022/03/08 02:34:37.760080 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/08 02:34:37.760238 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/08 02:34:37.760387 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/08 02:34:47.762357 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/08 02:34:47.762455 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/08 02:34:47.762577 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/08 02:34:47.762674 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/08 02:34:47.762785 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/08 02:34:52.771242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:52.771287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:53.776616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:53.776672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:55.782684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:55.782731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:59.792190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:34:59.792228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:35:07.392852 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=72 registrar.writes=1
2022/03/08 02:35:07.800498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:35:07.800562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:35:23.807643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:35:23.807692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:35:37.392743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:35:55.815962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:35:55.816009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:36:07.392675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:36:37.392801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:36:55.823107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:36:55.823148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:37:07.392833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:37:37.392684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:37:55.832482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:37:55.832519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:38:07.392802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:38:37.392795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:38:55.868677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:38:55.868765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:39:07.392784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:39:37.392713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:39:52.775092 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/08 02:39:55.879967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:39:55.880090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:40:07.392790 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/08 02:40:37.392789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:40:55.890414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:40:55.890455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:41:07.392820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:41:37.393023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:41:55.915708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:41:55.915784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:42:07.392781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:42:37.392874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:42:55.928511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:42:55.928556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:43:07.392752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:43:37.392675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:43:55.938340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:43:55.938379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:44:07.392730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:44:37.392723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:44:55.949972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:44:55.950011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:45:07.392875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:45:37.392678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:45:55.961592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:45:55.961647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:46:07.392691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:46:37.392771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:46:55.970642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:46:55.970673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:47:07.392747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:47:37.392697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:47:55.981032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:47:55.981080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:48:07.392705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:48:37.392701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:48:55.990388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:48:55.990439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:49:07.392806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:49:37.392781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:49:56.000809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:49:56.000849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:50:07.392818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:50:37.392946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:50:56.011400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:50:56.011447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:51:07.392763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:51:37.392598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:51:56.022490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:51:56.022553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:52:07.392749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:52:37.392769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:52:56.032754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:52:56.032817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:53:07.394600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:53:37.392876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:53:56.044154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:53:56.044206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:54:07.392797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:54:37.392761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:54:56.054949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:54:56.055015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:55:07.392766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:55:37.392790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:55:56.064840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:55:56.064886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:56:07.392790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:56:37.392734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:56:56.075746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:56:56.075793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:57:07.392753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:57:37.392934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:57:56.084312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:57:56.084360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:58:07.392750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:58:37.392844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:58:56.094860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:58:56.094905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:59:07.392610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:59:37.392789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 02:59:56.106878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 02:59:56.106927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:00:07.392606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:00:37.392886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:00:56.120316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:00:56.120363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:01:07.392639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:01:37.392807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:01:56.131597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:01:56.131686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:02:07.392851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:02:37.392766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:02:56.140993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:02:56.141036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:03:07.392814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:03:37.392809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:03:56.156961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:03:56.156989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:04:07.392703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:04:37.392831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:04:56.166085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:04:56.166113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:05:07.392636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:05:37.392842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:05:56.176560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:05:56.176607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:06:07.392659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:06:37.392699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:06:56.185885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:06:56.185927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:07:07.392798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:07:37.392769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:07:56.202269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:07:56.202340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:08:07.392766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:08:37.392845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:08:56.213871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:08:56.213943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:09:07.392754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:09:37.392725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:09:56.226865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:09:56.227058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:10:07.392740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:10:37.392693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:10:56.236925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:10:56.236974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:11:07.392802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:11:37.392691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:11:56.247120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:11:56.247167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:12:07.392764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:12:37.392716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:12:56.258731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:12:56.258773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:13:07.392991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:13:37.392930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:13:56.266475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:13:56.266495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:14:07.392795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:14:37.392728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:14:56.274605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:14:56.274634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:15:07.392802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:15:37.392780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:15:56.285848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:15:56.285886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:16:07.392553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:16:37.392810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:16:56.294424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:16:56.294459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:17:07.392716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:17:37.393055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:17:56.303863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:17:56.303921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:18:07.392740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:18:37.392835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:18:56.312900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:18:56.312923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:19:07.392800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:19:37.392835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:19:56.326124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:19:56.326174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:20:07.392736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:20:37.392955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:20:56.336699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:20:56.336726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:21:07.392815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:21:37.392716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:21:56.345122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:21:56.345173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:22:07.392805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:22:37.392656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:22:56.356553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:22:56.356617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:23:07.392816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:23:37.392734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:23:56.367733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:23:56.367785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:24:07.392747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:24:37.392804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:24:56.378341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:24:56.378386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:25:07.392883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:25:37.392770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:25:56.388523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:25:56.388631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:26:07.392807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:26:37.392649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:26:56.399939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:26:56.399987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:27:07.392692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:27:37.392753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:27:56.445973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:27:56.446018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:28:07.392887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:28:37.392726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:28:56.458664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:28:56.458713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:29:07.392715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:29:37.392965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:29:56.468127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:29:56.468150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:30:07.392623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:30:37.392568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:30:56.476411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:30:56.476442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:31:07.392945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:31:37.392655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:31:56.487199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:31:56.487245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:32:07.392872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:32:37.392831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:32:56.496289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:32:56.496331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:33:07.392804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:33:37.392777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:33:56.506945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:33:56.507006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:34:07.392834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:34:37.392749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:34:56.517394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:34:56.517459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:35:07.392886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:35:37.392799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:35:56.527087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:35:56.527192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:36:07.392701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:36:37.392902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:36:56.538475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:36:56.538528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:37:07.392722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:37:37.392880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:37:56.549659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:37:56.549736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:38:07.392780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:38:37.392797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:38:56.561287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:38:56.561311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:39:07.392700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:39:37.392715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:39:56.571225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:39:56.571255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:40:07.392886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:40:37.392751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:40:56.581391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:40:56.581420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:41:07.392880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:41:37.392824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:41:56.590904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:41:56.590946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:42:07.392711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:42:37.392654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:42:56.602361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:42:56.602416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:43:07.392805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:43:37.392755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:43:56.611991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:43:56.612043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:44:07.392728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:44:37.392630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:44:56.625666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:44:56.625704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:45:07.392785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:45:37.392681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:45:56.635693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:45:56.635730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:46:07.392657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:46:37.392905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:46:56.645474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:46:56.645521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:47:07.392773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:47:37.392802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:47:56.656089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:47:56.656135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:48:07.392617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:48:37.392679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:48:56.666501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:48:56.666529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:49:07.392663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:49:37.392685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:49:56.678424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:49:56.678452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:50:07.392629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:50:37.392797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:50:56.687600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:50:56.687648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:51:07.392657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:51:37.392736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:51:56.696285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:51:56.696308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:52:07.392634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:52:37.392739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:52:56.706144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:52:56.706204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:53:07.392648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:53:37.392771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:53:56.716788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:53:56.716856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:54:07.392755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:54:37.392765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:54:56.727580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:54:56.727608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:55:07.392658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:55:37.392670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:55:56.739460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:55:56.739560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:56:07.392630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:56:37.392662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:56:56.750919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:56:56.750972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:57:07.392745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:57:37.392801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:57:56.762485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:57:56.762511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:58:07.392665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:58:37.392689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:58:56.772985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:58:56.773036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:59:07.392689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:59:37.392836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 03:59:56.780959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 03:59:56.781006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:00:07.392648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:00:37.392572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:00:56.789214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:00:56.789263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:01:07.392753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:01:37.392761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:01:56.800317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:01:56.800395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:02:07.394847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:02:37.392864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:02:56.813011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:02:56.813070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:03:07.392861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:03:37.392851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:03:56.824671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:03:56.824707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:04:07.392920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:04:37.392688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:04:56.834535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:04:56.834588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:05:07.392537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:05:37.392814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:05:56.844219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:05:56.844262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:06:07.392832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:06:37.392775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:06:56.855206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:06:56.855280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:07:07.392659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:07:37.392785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:07:56.866277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:07:56.866325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:08:07.392752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:08:37.392620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:08:56.877905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:08:56.877959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:09:07.392793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:09:37.392724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:09:56.889206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:09:56.889255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:10:07.392809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:10:37.392691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:10:56.899441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:10:56.899483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:11:07.392701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:11:37.392694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:11:56.909187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:11:56.909236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:12:07.392655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:12:37.392736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:12:56.918015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:12:56.918045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:13:07.392829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:13:37.392806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:13:56.929376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:13:56.929414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:14:07.392662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:14:37.392781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:14:56.939436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:14:56.939488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:15:07.392696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:15:37.392881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:15:56.949270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:15:56.949326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:16:07.392614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:16:37.393160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:16:56.959072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:16:56.959099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:17:07.392843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:17:37.392693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:17:56.968192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:17:56.968223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:18:07.392709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:18:37.392845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:18:56.977994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:18:56.978045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:19:07.392736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:19:37.394124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:19:56.989471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:19:56.989535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:20:07.392776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:20:37.392772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:20:56.999708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:20:56.999775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:21:07.392752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:21:37.392810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:21:57.008997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:21:57.009034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:22:07.392785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:22:37.392639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:22:57.019945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:22:57.020014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:23:07.392734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:23:37.392726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:23:57.030503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:23:57.030549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:24:07.392830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:24:37.392734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:24:57.040939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:24:57.041035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:25:07.392667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:25:37.392647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:25:57.053282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:25:57.053327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:26:07.392692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:26:37.392769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:26:57.063842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:26:57.063870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:27:07.392819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:27:37.392760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:27:57.071338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:27:57.071388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:28:07.392926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:28:37.392800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:28:57.079417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:28:57.079468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:29:07.392747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:29:37.392943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:29:57.089793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:29:57.089855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:30:07.392647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:30:37.392780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:30:57.098749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:30:57.098777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:31:07.392707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:31:37.392749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:31:57.109685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:31:57.109735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:32:07.392673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:32:37.392666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:32:57.119432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:32:57.119459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:33:07.392776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:33:37.392792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:33:57.129537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:33:57.129589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:34:07.392844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:34:37.392704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:34:57.140069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:34:57.140125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:35:07.392678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:35:37.392755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 04:35:57.151330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:35:57.151382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 04:36:07.392814 metrics.go:34: INFO No non-zero metrics in the last 30s