Results

          2022/01/05 02:56:27.087843 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/01/05 02:56:27.087879 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/05 02:56:27.087964 logstash.go:90: INFO Max Retries set to: 3
2022/01/05 02:56:27.088018 metrics.go:23: INFO Metrics logging every 30s
2022/01/05 02:56:27.088061 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/05 02:56:27.088161 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-chx5f
2022/01/05 02:56:27.088320 async.go:63: INFO Flush Interval set to: 1s
2022/01/05 02:56:27.088341 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/05 02:56:27.088778 beat.go:221: INFO filebeat start running.
2022/01/05 02:56:27.088836 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/05 02:56:27.234813 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/05 02:56:27.234880 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/05 02:56:27.234933 crawler.go:38: INFO Loading Prospectors: 1
2022/01/05 02:56:27.235077 registrar.go:236: INFO Starting Registrar
2022/01/05 02:56:27.235129 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/05 02:56:27.235157 sync.go:41: INFO Start sending events to output
2022/01/05 02:56:27.235210 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/05 02:56:27.235234 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/05 02:56:27.235259 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/05 02:56:27.235735 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/05 02:56:27.235884 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/05 02:56:27.235910 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/05 02:56:27.236193 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/05 02:56:27.236242 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/05 02:56:32.246848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:32.246878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:33.253608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:33.253633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:35.256787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:35.256815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:39.262954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:39.262981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:47.269841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:47.269865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:57.088284 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=356 registrar.writes=1
2022/01/05 02:57:03.276885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:57:03.276913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:57:27.088344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:57:35.285204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:57:35.285265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:57:57.088390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:58:27.088434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:58:35.293160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:58:35.293206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:58:57.088303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:59:27.088397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:59:35.299792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:59:35.299825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:59:57.088365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:00:27.088354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:00:35.308573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:00:35.308606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:00:57.088270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:01:27.088276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:01:32.244693 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/05 03:01:32.244749 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/05 03:01:32.244774 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/05 03:01:32.244748 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/05 03:01:32.244802 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/01/05 03:01:35.315597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:01:35.315628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:01:57.088285 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/01/05 03:02:27.088357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:02:35.323172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:02:35.323207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:02:57.088318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:03:27.088264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:03:35.335600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:03:35.335635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:03:57.088401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:04:27.088375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:04:35.343888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:04:35.343939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:04:57.088270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:05:27.088304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:05:35.350984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:05:35.351012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:05:57.088312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:06:27.088263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:06:35.358672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:06:35.358716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:06:57.088267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:07:27.088289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:07:35.364706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:07:35.364733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:07:57.088344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:08:27.088313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:08:35.371834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:08:35.371879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:08:57.089524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:09:27.088284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:09:35.378614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:09:35.378662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:09:57.088307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:10:27.088470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:10:35.386749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:10:35.386782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:10:57.088254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:11:27.088267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:11:35.392937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:11:35.392972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:11:57.088443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:12:27.088273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:12:35.400665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:12:35.400697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:12:57.088314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:13:27.088360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:13:35.406844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:13:35.406883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:13:57.088348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:14:27.088330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:14:35.414272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:14:35.414299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:14:57.088280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:15:27.088249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:15:35.421808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:15:35.421847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:15:57.088289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:16:27.088267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:16:35.428628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:16:35.428658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:16:57.088275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:17:27.088263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:17:35.435756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:17:35.435803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:17:57.088311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:18:27.088326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:18:35.443432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:18:35.443464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:18:57.088227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:19:27.088271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:19:35.449253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:19:35.449292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:19:57.088267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:20:27.088230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:20:35.457525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:20:35.457559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:20:57.088273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:21:27.088392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:21:35.463959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:21:35.463985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:21:57.088261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:22:27.088357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:22:35.471745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:22:35.471780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:22:57.088243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:23:27.088251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:23:35.478275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:23:35.478307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:23:57.088268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:24:27.088267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:24:35.486687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:24:35.486729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:24:57.088267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:25:27.088350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:25:35.492878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:25:35.492907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:25:57.088292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:26:27.088231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:26:35.500023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:26:35.500056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:26:57.088398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:27:27.088299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:27:35.507170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:27:35.507213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:27:57.088278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:28:27.088280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:28:35.514224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:28:35.514254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:28:57.088259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:29:27.088346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:29:35.521131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:29:35.521166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:29:57.088313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:30:27.088284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:30:35.529461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:30:35.529498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:30:57.088308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:31:27.088306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:31:35.536170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:31:35.536204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:31:57.088336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:32:27.088284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:32:35.545428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:32:35.545462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:32:57.088300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:33:27.088273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:33:35.552332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:33:35.552363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:33:57.088367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:34:27.088278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:34:35.559805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:34:35.559839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:34:57.088282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:35:27.088306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:35:35.566116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:35:35.566154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:35:57.088294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:36:27.088465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:36:35.573523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:36:35.573558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:36:57.088380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:37:27.088289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:37:35.580307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:37:35.580340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:37:57.088329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:38:27.088237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:38:35.588194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:38:35.588231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:38:57.088299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:39:27.088304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:39:35.595232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:39:35.595261 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:39:57.088315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:40:27.088242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:40:35.603322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:40:35.603353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:40:57.088309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:41:27.088234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:41:35.610884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:41:35.610913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:41:57.088258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:42:27.088273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:42:35.619238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:42:35.619273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:42:57.088262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:43:27.088252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:43:35.627405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:43:35.627433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:43:57.088239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:44:27.088305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:44:35.635702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:44:35.635732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:44:57.088269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:45:27.088269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:45:35.642633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:45:35.642683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:45:57.088288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:46:27.088309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:46:35.649933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:46:35.649965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:46:57.088256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:47:27.088313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:47:35.657135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:47:35.657167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:47:57.088250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:48:27.088293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:48:35.665982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:48:35.666018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:48:57.088250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:49:27.088293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:49:35.673119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:49:35.673167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:49:57.088261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:50:27.088345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:50:35.681853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:50:35.681892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:50:57.088281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:51:27.088261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:51:35.689788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:51:35.689817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:51:57.088301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:52:27.088294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:52:35.697507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:52:35.697541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:52:57.088252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:53:27.088302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:53:35.704918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:53:35.704950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:53:57.088307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:54:27.088277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:54:35.714114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:54:35.714143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:54:57.088253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:55:27.088240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:55:35.721639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:55:35.721672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:55:57.088298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:56:27.088262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:56:35.728957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:56:35.728992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:56:57.088299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:57:27.088300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:57:35.735980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:57:35.736011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:57:57.088250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:58:27.088338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:58:35.743604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:58:35.743634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:58:57.088297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:59:27.088353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:59:35.751425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:59:35.751456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:59:57.088299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:00:27.088248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:00:35.759678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:00:35.759714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:00:57.088320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:01:27.088281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:01:35.766508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:01:35.766537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:01:57.089406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:02:27.088285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:02:35.773620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:02:35.773645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:02:57.088285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:03:27.088218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:03:35.780450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:03:35.780483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:03:57.088247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:04:27.088329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:04:35.788257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:04:35.788291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:04:57.089660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:05:27.088329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:05:35.794608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:05:35.794640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:05:57.088233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:06:27.088268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:06:35.803369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:06:35.803515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:06:57.088313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:07:27.088324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:07:35.810483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:07:35.810602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:07:57.088279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:08:27.088317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:08:35.817828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:08:35.817859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:08:57.088251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:09:27.088342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:09:35.826476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:09:35.826505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:09:57.088251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:10:27.088374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:10:35.835435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:10:35.835466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:10:57.088300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:11:27.088313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:11:35.842144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:11:35.842172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:11:57.088278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:12:27.088285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:12:35.853628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:12:35.853660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:12:57.088298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:13:27.088290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:13:35.860790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:13:35.860842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host