By type
2022/03/09 16:21:30.777178 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/09 16:21:30.777263 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 16:21:30.777346 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 16:21:30.777467 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 16:21:30.777597 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 16:21:30.780069 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-n89rh
2022/03/09 16:21:30.780392 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 16:21:30.780419 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 16:21:30.781040 beat.go:221: INFO filebeat start running.
2022/03/09 16:21:30.781108 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 16:21:30.785339 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 16:21:30.785392 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 16:21:30.785432 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 16:21:30.785621 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 16:21:30.785716 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/09 16:21:30.785739 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 16:21:30.785752 registrar.go:236: INFO Starting Registrar
2022/03/09 16:21:30.785783 sync.go:41: INFO Start sending events to output
2022/03/09 16:21:30.785815 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 16:21:50.791402 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/09 16:21:50.792385 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/09 16:21:50.800113 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/09 16:21:50.800764 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/09 16:21:50.800874 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/09 16:21:55.806073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:55.806119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:56.810510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:56.810542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:58.816838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:58.816898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:00.780113 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=64 registrar.writes=1
2022/03/09 16:22:02.824420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:02.824456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:10.830434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:10.830484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:26.842633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:26.842854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:30.777962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:22:58.850886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:58.850928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:23:00.777975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:23:30.777964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:23:58.854113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:23:58.854148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:24:00.778266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:24:30.777963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:24:58.857195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:24:58.857246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:25:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:25:30.777860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:25:58.860265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:25:58.860302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:26:00.777931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:26:30.777951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:26:55.806791 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:55.815445 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:55.815457 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:55.815449 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:58.863388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:26:58.863447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:27:00.777957 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/09 16:27:10.808654 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:27:30.777958 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/09 16:27:58.867329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:27:58.867385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:28:00.778048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:28:30.778001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:28:58.870395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:28:58.870444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:29:00.777955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:29:30.778081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:29:58.874827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:29:58.874862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:30:00.777930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:30:30.778019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:30:58.879088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:30:58.879131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:31:00.777917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:31:30.777918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:31:58.882618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:31:58.882654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:32:00.777882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:32:30.780983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:32:58.886357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:32:58.886694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:33:00.778240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:33:30.777955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:33:58.890745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:33:58.890776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:34:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:34:30.777887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:34:58.895645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:34:58.895691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:35:00.780055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:35:30.777901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:35:58.899779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:35:58.899820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:36:00.778011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:36:30.777979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:36:58.903433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:36:58.903490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:37:00.777916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:37:30.777916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:37:58.907325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:37:58.907357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:38:00.777878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:30.777897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:58.910648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:38:58.910682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:39:00.777929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:30.778005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:58.913439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:39:58.913480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:40:00.778010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:30.777997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:58.917390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:40:58.917434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:41:00.777940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:30.777987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:58.920564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:41:58.920662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:42:00.777968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:42:30.777928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:42:58.924068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:42:58.924105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:43:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:30.777969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:58.940091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:43:58.940136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:44:00.777967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:30.777865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:58.954482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:44:58.954521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:45:00.777969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:30.777949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:58.960681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:45:58.960732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:46:00.777968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:30.777850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:58.968453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:46:58.968501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:47:00.777953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:30.777897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:58.974460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:47:58.974497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:48:00.777931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:30.777940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:58.981343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:48:58.981393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:49:00.777985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:30.777931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:58.988145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:49:58.988189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:50:00.777977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:30.778120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:58.995648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:50:58.995701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:51:00.778090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:30.777915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:59.002098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:51:59.002150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:52:00.777994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:30.777905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:59.007758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:52:59.007796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:53:00.778009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:30.777888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:59.014168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:53:59.014219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:54:00.777943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:30.777898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:59.022597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:54:59.022643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:55:00.778096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:30.777940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:59.029077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:55:59.029119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:56:00.777989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:30.778060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:59.035856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:56:59.035929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:57:00.777908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:30.778000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:59.045152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:57:59.045366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:58:00.777935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:30.777918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:59.056621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:58:59.056840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:59:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:30.777934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:59.063388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:59:59.063437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:00:00.777989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:30.778018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:59.070427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:00:59.070462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:01:00.778068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:01:30.777960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:01:59.076901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:01:59.076934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:02:00.783420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:02:30.777936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:02:59.084456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:02:59.084843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:03:00.777999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:03:30.777918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:03:59.091450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:03:59.091497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:04:00.777935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:04:30.777891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:04:59.099136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:04:59.099177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:05:00.777939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:05:30.777945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:05:59.105768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:05:59.105801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:06:00.777927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:06:30.777948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:06:59.113525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:06:59.113574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:07:00.777955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:07:30.777907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:07:59.120299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:07:59.120339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:08:00.777954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:08:30.777939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:08:59.126855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:08:59.126896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:09:00.777933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:09:30.777977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:09:59.132947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:09:59.132996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:10:00.777890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:10:30.778323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:10:59.142568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:10:59.142635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:11:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:11:30.778023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:11:59.152521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:11:59.152566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:12:00.778037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:12:30.777996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:12:59.160140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:12:59.160289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:13:00.777959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:13:30.777883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:13:59.168086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:13:59.168133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:14:00.777942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:14:30.777942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:14:59.174364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:14:59.174424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:15:00.777968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:15:30.777916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:15:59.180800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:15:59.180856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:16:00.777921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:16:30.777992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:16:59.187777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:16:59.187825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:17:00.777946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:17:30.777909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:17:59.194724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:17:59.194773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:18:00.777916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:18:30.777922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:18:59.201522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:18:59.201561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:19:00.777883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:19:30.777995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:19:59.207298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:19:59.207343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:20:00.777929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:20:30.779098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:20:59.214061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:20:59.214128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:21:00.777986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:21:30.778032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:21:59.220833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:21:59.221229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:22:00.778060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:22:30.778120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:22:59.228932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:22:59.228997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:23:00.777938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:23:30.778588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:23:59.242990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:23:59.243027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:24:00.778068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:24:30.777999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:24:59.256432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:24:59.256514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:25:00.777963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:25:30.777959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:25:59.263742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:25:59.263795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:26:00.777957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:26:30.778028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:26:59.270376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:26:59.270411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:27:00.777951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:27:30.777957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:27:59.278143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:27:59.278193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:28:00.777838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:28:30.778006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:28:59.285027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:28:59.285064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:29:00.777955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:29:30.777952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:29:59.291722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:29:59.291762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:30:00.778047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:30:30.777946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:30:59.298495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:30:59.298532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:31:00.777965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:31:30.777907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:31:59.306451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:31:59.306495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:32:00.777917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:32:30.778046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:32:59.314950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:32:59.314985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:33:00.777977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:33:30.778009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:33:59.323551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:33:59.323611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:34:00.778009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:34:30.778134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:34:59.333204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:34:59.333238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:35:00.777912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:35:30.777916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:35:59.345396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:35:59.345429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:36:00.778134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:36:30.777911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:36:59.354269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:36:59.354344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:37:00.777904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:37:30.777904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:37:59.362012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:37:59.362092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:38:00.777931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:38:30.778007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:38:59.371366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:38:59.371415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:39:00.777947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:39:30.777926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:39:59.378145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:39:59.378206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:40:00.778435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:40:30.777943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:40:59.385404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:40:59.385491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:41:00.777918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:41:30.777919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:41:59.392154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:41:59.392213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:42:00.778068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:42:30.778127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:42:59.398264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:42:59.398302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:43:00.777982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:43:30.777925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:43:59.404933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:43:59.404994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:44:00.777910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:44:30.777880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:44:59.411720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:44:59.411754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:45:00.777933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:45:30.777923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:45:59.418188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:45:59.418240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:46:00.777960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:46:30.777899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:46:59.424390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:46:59.424424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:47:00.777892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:47:30.777957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:47:59.431677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:47:59.431753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:48:00.777944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:48:30.777902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:48:59.441173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:48:59.441223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:49:00.777810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:49:30.777862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:49:59.452848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:49:59.453084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:50:00.778142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:50:30.777928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:50:59.459788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:50:59.459831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:51:00.778978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:51:30.777965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:51:59.466184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:51:59.466229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:52:00.777984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:52:30.777957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:52:59.473215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:52:59.473252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:53:00.777967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:53:30.778130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:53:59.481385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:53:59.481421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:54:00.778318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:54:30.778005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:54:59.487985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:54:59.488024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:55:00.777897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:55:30.777965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:55:59.494431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:55:59.494479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:56:00.778002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:56:30.778419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:56:59.501406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:56:59.501458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:57:00.777922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:57:30.777997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:57:59.508450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:57:59.508490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:58:00.778040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:58:30.777973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:58:59.516617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:58:59.516654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:59:00.778176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:59:30.777924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:59:59.523100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:59:59.523138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:00:00.777904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:00:30.777903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:00:59.530066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:00:59.530098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:01:00.777917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:01:30.777909 metrics.go:34: INFO No non-zero metrics in the last 30s