By type
2022/03/26 03:02:18.761535 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/26 03:02:18.761592 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/26 03:02:18.761680 logstash.go:90: INFO Max Retries set to: 3
2022/03/26 03:02:18.761734 metrics.go:23: INFO Metrics logging every 30s
2022/03/26 03:02:18.761807 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/26 03:02:18.761939 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-46r9w
2022/03/26 03:02:18.762202 async.go:63: INFO Flush Interval set to: 1s
2022/03/26 03:02:18.762221 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/26 03:02:18.762975 beat.go:221: INFO filebeat start running.
2022/03/26 03:02:18.763186 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/26 03:02:18.769041 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/26 03:02:18.769126 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/26 03:02:18.769163 crawler.go:38: INFO Loading Prospectors: 1
2022/03/26 03:02:18.769246 registrar.go:236: INFO Starting Registrar
2022/03/26 03:02:18.769325 sync.go:41: INFO Start sending events to output
2022/03/26 03:02:18.769491 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/26 03:02:18.769533 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/26 03:02:18.769698 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/26 03:02:18.769757 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/26 03:02:38.776358 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/26 03:02:38.776519 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/26 03:02:38.776730 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/26 03:02:38.777085 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/26 03:02:38.779391 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/26 03:02:43.797464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:43.797809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:44.850947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:44.850995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:46.857413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:46.857457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:48.762606 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=70 registrar.writes=1
2022/03/26 03:02:50.864661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:50.864715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:58.871533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:58.871880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:03:14.895704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:03:14.895757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:03:18.762474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:03:46.919163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:03:46.919535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:03:48.762212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:04:18.762330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:04:46.941713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:04:46.941792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:04:48.762245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:05:18.762140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:05:46.961123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:05:46.961182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:05:48.762135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:06:18.762213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:06:46.983700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:06:46.983770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:06:48.762117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:07:18.762116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:07:43.793413 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:07:47.002838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:07:47.002890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:07:48.762162 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/26 03:08:18.762159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:08:47.022205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:08:47.022252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:08:48.762074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:09:18.762065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:09:47.047770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:09:47.047819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:09:48.762463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:10:18.762100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:10:47.067089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:10:47.067156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:10:48.762037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:11:18.762076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:11:47.088115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:11:47.088151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:11:48.762128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:12:18.762114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:12:47.109428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:12:47.109462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:12:48.762093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:13:18.762122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:13:47.142195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:13:47.142265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:13:48.762076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:14:18.762705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:14:47.163186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:14:47.163258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:14:48.762033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:15:18.762250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:15:47.222417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:15:47.222486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:15:48.770593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:18.762142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:47.248602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:16:47.248661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:16:48.766244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:18.762184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:47.302567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:17:47.302629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:17:48.762652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:18.762058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:47.331074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:18:47.331169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:18:48.762418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:18.762722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:47.351368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:19:47.351469 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:19:48.762211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:20:18.762114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:20:47.370619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:20:47.370676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:20:48.762213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:18.762048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:47.389614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:21:47.389654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:21:48.762059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:18.762059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:47.409972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:22:47.410010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:22:48.762132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:18.762264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:47.430048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:23:47.430090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:23:48.762115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:18.762045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:47.454008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:24:47.454050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:24:48.762073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:18.762367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:47.471955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:25:47.472004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:25:48.762032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:18.762089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:47.490477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:26:47.490548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:26:48.762109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:18.762077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:47.511286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:27:47.511353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:27:48.762047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:18.762093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:47.530255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:28:47.530312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:28:48.762500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:18.762790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:47.550652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:29:47.551252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:29:48.762191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:18.762122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:47.570993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:30:47.571077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:30:48.762134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:18.762086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:47.591588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:31:47.591688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:31:48.762143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:18.762112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:47.618962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:32:47.619191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:32:48.762129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:18.762059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:47.638091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:33:47.638142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:33:48.762063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:18.762019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:47.677959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:34:47.678002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:34:48.762029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:18.762196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:47.695324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:35:47.695381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:35:48.762062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:18.762523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:47.719368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:36:47.719429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:36:48.762080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:18.762017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:47.740378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:37:47.740456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:37:48.762182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:18.762069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:47.763348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:38:47.763404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:38:48.762030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:18.762144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:47.782705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:39:47.782792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:39:48.762099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:18.762121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:47.803629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:40:47.803680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:40:48.762200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:18.762091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:47.822613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:41:47.822697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:41:48.762124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:18.762077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:47.845191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:47.845247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:48.762045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:43:18.762057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:43:47.869021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:47.869080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:48.762164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:18.762150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:47.889045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:44:47.889100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:44:48.762086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:18.762156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:47.908241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:45:47.908414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:45:48.762061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:18.762102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:47.929198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:46:47.929253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:46:48.762099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:18.762269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:47.953601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:47:47.953653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:47:48.763379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:18.762098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:47.979988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:48:47.980046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:48:48.762124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:18.762235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:48.002199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:49:48.002241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:49:48.762366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:18.762237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:48.021799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:50:48.021868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:50:48.762080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:18.762113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:48.040565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:51:48.040680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:51:48.762122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:18.762183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:48.060809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:52:48.060883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:52:48.762148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:18.762119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:48.083491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:53:48.083536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:53:48.762018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:18.762076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:48.104612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:54:48.104680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:54:48.762069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:18.762135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:48.124462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:55:48.124523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:55:48.762183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:18.762122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:48.143540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:56:48.143601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:56:48.762010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:18.762120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:48.166465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:57:48.166524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:57:48.762093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:18.762136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:48.186769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:58:48.186891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:58:48.762023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:18.762051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:48.209725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:59:48.209775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:59:48.762056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:18.762732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:48.231794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:00:48.231846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:00:48.762233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:18.762137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:48.264350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:01:48.264427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:01:48.762031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:18.762093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:48.283478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:02:48.283540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:02:48.762147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:18.762196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:48.301564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:03:48.301613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:03:48.762152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:18.762192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:48.319233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:04:48.319289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:04:48.762107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:18.762083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:48.342026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:05:48.342086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:05:48.762112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:18.762039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:48.362979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:06:48.363069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:06:48.762083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:18.762180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:48.383198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:07:48.383256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:07:48.762187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:18.762152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:48.403868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:08:48.403928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:08:48.762113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:18.764378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:48.422664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:09:48.422710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:09:48.762104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:18.762041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:48.443438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:10:48.443505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:10:48.762036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:18.762082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:48.465272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:11:48.465320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:11:48.766925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:18.762358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:48.486858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:12:48.486897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:12:48.762152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:18.762151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:48.508138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:13:48.508196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:13:48.762100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:18.762229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:48.527389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:14:48.527433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:14:48.762091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:18.762096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:48.557350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:15:48.557412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:15:48.762141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:18.762199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:48.579664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:16:48.579720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:16:48.762102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:18.762015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:48.598357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:17:48.598401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:17:48.762532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:18.762110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:48.620247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:18:48.620613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:18:48.762191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:18.762177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:48.640421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:19:48.640483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:19:48.762122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:18.762020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:48.661819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:20:48.662247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:20:48.762178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:18.762090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:48.683244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:21:48.683442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:21:48.762138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:18.762057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:48.703887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:22:48.703942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:22:48.762306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:18.762058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:48.725484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:23:48.725526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:23:48.762138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:18.762116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:48.744198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:24:48.744248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:24:48.762111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:18.762045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:48.762133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:48.765248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:25:48.765322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:26:18.762170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:48.762130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:48.784850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:26:48.784910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:27:18.762178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:48.762113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:48.804114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:27:48.804152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:28:18.762123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:48.762117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:48.824933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:28:48.824997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:29:18.762048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:48.762067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:48.845709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:29:48.845763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:30:18.762157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:48.762031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:48.865039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:30:48.865094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:31:18.762333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:48.762069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:48.883181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:31:48.883585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:32:18.762117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:48.762116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:48.902420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:32:48.902475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:33:18.762082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:48.762349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:48.924181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:33:48.924238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:34:18.762140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:48.762114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:48.944449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:34:48.944515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:35:18.762091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:48.762123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:48.966767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:35:48.966814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:36:18.762089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:48.762180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:48.988709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:36:48.988751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:37:18.762073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:48.762065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:49.013580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:37:49.013638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:38:18.762073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:48.762101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:49.032475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:38:49.032572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:39:18.762010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:48.762070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:49.064510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:39:49.064565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:40:18.762096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:48.762149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:49.091249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:40:49.091309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:41:18.762112 metrics.go:34: INFO No non-zero metrics in the last 30s