By type
2022/03/25 03:03:03.827378 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/25 03:03:03.827432 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/25 03:03:03.827504 metrics.go:23: INFO Metrics logging every 30s
2022/03/25 03:03:03.827508 logstash.go:90: INFO Max Retries set to: 3
2022/03/25 03:03:03.827617 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/25 03:03:03.827751 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-9fmw5
2022/03/25 03:03:03.827968 async.go:63: INFO Flush Interval set to: 1s
2022/03/25 03:03:03.827995 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/25 03:03:03.828421 beat.go:221: INFO filebeat start running.
2022/03/25 03:03:03.828519 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/25 03:03:03.832788 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/25 03:03:03.832876 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/25 03:03:03.832914 crawler.go:38: INFO Loading Prospectors: 1
2022/03/25 03:03:03.832943 registrar.go:236: INFO Starting Registrar
2022/03/25 03:03:03.833188 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/25 03:03:03.833218 sync.go:41: INFO Start sending events to output
2022/03/25 03:03:03.833351 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/25 03:03:03.833358 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/25 03:03:03.833561 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/25 03:03:23.835774 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/25 03:03:23.836020 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/25 03:03:23.836229 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/25 03:03:23.836298 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/25 03:03:23.836394 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/25 03:03:28.852616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:28.852659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:29.856421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:29.856452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:31.862123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:31.862153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:33.827867 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/25 03:03:35.866872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:35.866900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:43.873994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:43.874246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:59.898156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:59.898229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:03.827910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:04:31.915143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:31.915184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:33.827827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:03.827787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:31.930982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:31.931018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:33.827807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:03.827832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:31.948022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:31.948066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:33.827881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:03.829392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:31.965735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:31.965772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:33.827821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:03.827892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:28.845571 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:08:28.845587 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:08:28.845632 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:08:28.845671 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:08:31.984338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:31.984369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:33.827867 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/25 03:08:35.851915 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:09:03.827847 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/25 03:09:32.001850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:09:32.002038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:09:33.827757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:03.827968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:32.017700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:32.017734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:33.827809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:03.827761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:32.036466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:32.036498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:33.827755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:03.827817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:32.053276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:32.053314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:33.827837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:03.828170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:32.072613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:32.072643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:33.827849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:03.827775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:32.091648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:32.091696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:33.827942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:03.827824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:32.109752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:32.109798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:33.827732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:03.828268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:32.127398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:32.127432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:33.827784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:03.830511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:32.144434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:32.144494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:33.827762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:03.827786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:32.162915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:32.162970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:33.827877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:03.827804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:32.179947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:32.179983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:33.827868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:03.827836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:32.200401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:32.200559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:33.827803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:03.827925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:32.221030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:32.221079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:33.827819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:03.827872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:32.238526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:32.238565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:33.827778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:03.827985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:32.256742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:32.256786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:33.827899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:03.827778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:32.278384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:32.278439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:33.827791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:03.827825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:32.296524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:32.296553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:33.827726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:03.827802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:32.314224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:32.314291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:33.827756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:03.827857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:32.333203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:32.333240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:33.827849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:03.827843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:32.352739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:32.352878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:33.827987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:03.827757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:32.371171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:32.371213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:33.827753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:03.827848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:32.390270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:32.390308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:33.827863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:03.827889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:32.412085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:32.412135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:33.827886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:03.828122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:32.429915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:32.430090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:33.827809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:03.827761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:32.450460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:32.450507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:33.827782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:03.827813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:32.468518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:32.468560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:33.829133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:03.827828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:32.485181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:32.485219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:33.827789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:03.827778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:32.503630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:36:32.503673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:36:33.827872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:37:03.827817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:37:32.520572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:37:32.520636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:37:33.827841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:38:03.828056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:38:32.538411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:38:32.538457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:38:33.827875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:39:03.827973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:39:32.559570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:39:32.559605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:39:33.827818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:40:03.827805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:40:32.579072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:40:32.579238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:40:33.827963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:41:03.827750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:41:32.595940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:41:32.595975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:41:33.827838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:42:03.827834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:42:32.613673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:42:32.613705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:42:33.827823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:43:03.827868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:43:32.629370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:43:32.629403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:43:33.827800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:44:03.827796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:44:32.647640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:44:32.647680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:44:33.827866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:45:03.827825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:45:32.669644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:45:32.669676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:45:33.827787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:46:03.827806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:46:32.687306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:46:32.687346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:46:33.827829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:47:03.827793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:47:32.708163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:47:32.708203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:47:33.827959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:48:03.827782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:48:32.726679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:48:32.726714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:48:33.827844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:49:03.827807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:49:32.744947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:49:32.744996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:49:33.827815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:50:03.827791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:50:32.765247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:50:32.765278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:50:33.827837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:51:03.827833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:51:32.781715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:51:32.781889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:51:33.827807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:52:03.827937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:52:32.800452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:52:32.800600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:52:33.827797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:53:03.827847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:53:32.817859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:53:32.817908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:53:33.828123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:54:03.827813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:54:32.836712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:54:32.836906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:54:33.827838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:55:03.827779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:55:32.854832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:55:32.854873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:55:33.827888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:56:03.827914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:56:32.872799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:56:32.872833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:56:33.827860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:57:03.827998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:57:32.891480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:57:32.891548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:57:33.827812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:58:03.827887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:58:32.909453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:58:32.909498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:58:33.827861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:59:03.827910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:59:32.925601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:59:32.925901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:59:33.827769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:00:03.827814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:00:32.942529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:00:32.942568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:00:33.827905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:01:03.827814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:01:32.959295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:01:32.959338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:01:33.827796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:02:03.827869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:02:32.976458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:02:32.976490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:02:33.827858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:03:03.827839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:03:32.993057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:03:32.993088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:03:33.827856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:04:03.827791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:04:33.010290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:04:33.010325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:04:33.827853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:05:03.827821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:05:33.032257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:05:33.032297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:05:33.827862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:06:03.827932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:06:33.048407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:06:33.048445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:06:33.827866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:07:03.827900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:07:33.064581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:07:33.064618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:07:33.827724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:08:03.827838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:08:33.083681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:08:33.083724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:08:33.827870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:09:03.827767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:09:33.101076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:09:33.101112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:09:33.827784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:10:03.827893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:10:33.119042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:10:33.119080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:10:33.827936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:11:03.827840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:11:33.136035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:11:33.136082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:11:33.827854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:12:03.827844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:12:33.153565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:12:33.153591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:12:33.827812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:13:03.827877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:13:33.171954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:13:33.172023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:13:33.827865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:14:03.827834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:14:33.190469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:14:33.190668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:14:33.827863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:15:03.827816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:15:33.208581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:15:33.208630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:15:33.827803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:16:03.827750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:16:33.225798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:16:33.225836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:16:33.827880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:17:03.827857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:17:33.243978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:17:33.244013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:17:33.827777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:18:03.827764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:18:33.271400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:18:33.271469 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:18:33.827760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:19:03.827827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:19:33.288928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:19:33.288970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:19:33.827795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:20:03.828043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:20:33.306319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:20:33.306357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:20:33.827840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:21:03.827844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:21:33.325124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:21:33.325162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:21:33.827850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:22:03.827937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:22:33.341912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:22:33.341944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:22:33.827788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:23:03.827982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:23:33.364462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:23:33.364503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:23:33.827779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:24:03.827796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:24:33.383709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:24:33.384053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:24:33.827863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:25:03.827833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:25:33.403255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:25:33.403288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:25:33.827817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:26:03.827820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:26:33.420879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:26:33.421004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:26:33.827840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:27:03.827760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:27:33.440393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:27:33.440469 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:27:33.827856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:28:03.827795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:28:33.458650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:28:33.458697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:28:33.827813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:29:03.827817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:29:33.477087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:29:33.477126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:29:33.827902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:30:03.827803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:30:33.827914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:30:35.494325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:30:35.494374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:31:03.827916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:31:33.827857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:31:35.515437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:31:35.515468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:32:03.827959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:32:33.827997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:32:35.534492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:32:35.534563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:33:03.827783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:33:33.827847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:33:35.551012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:33:35.551055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:34:03.827811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:34:33.827829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:34:35.569482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:34:35.569520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:35:03.827799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:35:33.827867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:35:35.593091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:35:35.593124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:36:03.827871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:36:33.827900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:36:35.612461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:36:35.612497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:37:03.828120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:37:33.827781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:37:35.630240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:37:35.630298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:38:03.827842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:38:33.827890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:38:35.650600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:38:35.650635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:39:03.827849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:39:33.827934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:39:35.668147 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:39:35.668182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:40:03.827803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:40:33.827931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:40:35.687317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:40:35.687362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:41:03.827836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:41:33.827801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:41:35.706489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:41:35.706533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:42:03.827845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:42:33.827838 metrics.go:34: INFO No non-zero metrics in the last 30s