Results

          2022/03/30 03:04:09.816757 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/30 03:04:09.816809 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/30 03:04:09.816927 logstash.go:90: INFO Max Retries set to: 3
2022/03/30 03:04:09.816999 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/30 03:04:09.817121 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-l2sqs
2022/03/30 03:04:09.817354 async.go:63: INFO Flush Interval set to: 1s
2022/03/30 03:04:09.817378 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/30 03:04:09.819267 beat.go:221: INFO filebeat start running.
2022/03/30 03:04:09.819351 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/30 03:04:09.822758 metrics.go:23: INFO Metrics logging every 30s
2022/03/30 03:04:09.826051 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/30 03:04:09.826124 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/30 03:04:09.826175 crawler.go:38: INFO Loading Prospectors: 1
2022/03/30 03:04:09.826226 registrar.go:236: INFO Starting Registrar
2022/03/30 03:04:09.826325 sync.go:41: INFO Start sending events to output
2022/03/30 03:04:09.826384 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/30 03:04:09.826457 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/30 03:04:09.826583 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/30 03:04:09.826615 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/30 03:04:29.831708 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/30 03:04:29.831773 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/30 03:04:29.831721 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/30 03:04:29.831710 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/30 03:04:29.831778 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/30 03:04:34.853451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:34.853508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:35.864974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:35.865034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:37.878187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:37.878239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:39.823412 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/30 03:04:41.888946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:41.889008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:49.897460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:04:49.897529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:05.920431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:05.920482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:09.823177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:05:37.938754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:37.938975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:05:39.823176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:06:09.823226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:06:37.987992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:06:37.988040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:06:39.823315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:07:09.823203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:07:38.010899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:07:38.010961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:07:39.823170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:08:09.823126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:08:38.036214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:08:38.036263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:08:39.823241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:09:09.823047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:09:34.859665 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/30 03:09:34.859764 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/30 03:09:34.859823 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/30 03:09:34.860000 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/30 03:09:38.061173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:09:38.061245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:09:39.823263 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/30 03:09:49.862734 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/30 03:10:09.823059 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/30 03:10:38.103066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:10:38.103119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:10:39.823122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:11:09.823106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:11:38.124287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:11:38.124344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:11:39.823176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:12:09.823092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:12:38.151526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:12:38.151638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:12:39.823175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:13:09.823134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:13:38.171395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:13:38.171429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:13:39.823099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:14:09.823139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:14:38.191420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:14:38.191456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:14:39.823181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:15:09.823413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:15:38.210791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:15:38.210869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:15:39.823185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:16:09.823162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:16:38.240896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:16:38.240945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:16:39.823164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:17:09.823865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:17:38.266316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:17:38.266377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:17:39.823410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:18:09.823138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:18:38.284912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:18:38.284954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:18:39.823146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:19:09.823329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:19:38.303984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:19:38.304030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:19:39.823115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:20:09.823169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:20:38.332086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:20:38.332123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:20:39.823201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:21:09.823141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:21:38.352686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:21:38.352729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:21:39.823087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:22:09.823131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:22:38.376814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:22:38.376857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:22:39.823244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:23:09.823304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:23:38.418409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:23:38.418459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:23:39.823184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:24:09.823071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:24:38.438075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:24:38.438113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:24:39.823181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:25:09.823656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:25:38.460236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:25:38.460289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:25:39.823418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:26:09.823188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:26:38.485450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:26:38.485492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:26:39.823111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:27:09.823099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:27:38.504717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:27:38.504789 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:27:39.823234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:28:09.823104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:28:38.531971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:28:38.532028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:28:39.823148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:29:09.823062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:29:38.555062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:29:38.555104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:29:39.823260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:30:09.823122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:30:38.575062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:30:38.575115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:30:39.823126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:31:09.823066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:31:38.597927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:31:38.597996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:31:39.823171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:32:09.823131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:32:38.618157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:32:38.618199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:32:39.823275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:33:09.823155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:33:38.636408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:33:38.636458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:33:39.823122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:34:09.823150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:34:38.658086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:34:38.658128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:34:39.823222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:35:09.823133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:35:38.683056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:35:38.683107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:35:39.823142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:36:09.823149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:36:38.705999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:36:38.706046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:36:39.823784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:37:09.823063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:37:38.730954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:37:38.731011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:37:39.823141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:38:09.823082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:38:38.756915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:38:38.756971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:38:39.823166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:39:09.823119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:39:38.785699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:39:38.785972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:39:39.823200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:40:09.823120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:40:38.810226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:40:38.810306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:40:39.823106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:41:09.823173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:41:38.833224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:41:38.833289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:41:39.823156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:42:09.823116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:42:38.856631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:42:38.856711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:42:39.823141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:43:09.823103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:43:38.879413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:43:38.879467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:43:39.823157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:44:09.823097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:44:38.910180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:44:38.910225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:44:39.823233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:45:09.823188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:45:38.931523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:45:38.931565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:45:39.823182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:46:09.823083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:46:38.966220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:46:38.966266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:46:39.823054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:47:09.823286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:47:38.970317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:38.970364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:47:39.823186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:48:09.823289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:48:38.979941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:48:38.979986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:48:39.823163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:49:09.823091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:49:38.989182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:49:38.989220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:49:39.823658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:50:09.823048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:50:38.996053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:50:38.996089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:50:39.823142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:51:09.823095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:51:39.003384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:51:39.003429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:51:39.823091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:52:09.823204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:52:39.011562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:52:39.011646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:52:39.823165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:53:09.823170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:53:39.015857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:53:39.015907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:53:39.823139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:54:09.823112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:54:39.020024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:54:39.020065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:54:39.823063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:55:09.823154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:55:39.024095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:55:39.024151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:55:39.823120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:56:09.823087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:56:39.027698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:56:39.027729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:56:39.823207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:57:09.823122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:57:39.036139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:57:39.036206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:57:39.823146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:58:09.823138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:58:39.041522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:58:39.041564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:58:39.823164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:59:09.823059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 03:59:39.045132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:59:39.045167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 03:59:39.823302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:00:09.823146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:00:39.049836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:00:39.049882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:00:39.823293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:01:09.823185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:01:39.053351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:01:39.053390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:01:39.823233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:02:09.823248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:02:39.057616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:02:39.057668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:02:39.823161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:03:09.823103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:03:39.061863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:03:39.061921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:03:39.823137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:04:09.823325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:04:39.064924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:04:39.064967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:04:39.823140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:05:09.823195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:05:39.069509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:05:39.069555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:05:39.823174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:06:09.823094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:06:39.072907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:06:39.073122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:06:39.823060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:07:09.823275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:07:39.076615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:07:39.076772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:07:39.823145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:08:09.823122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:08:39.080730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:08:39.080773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:08:39.823335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:09:09.823146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:09:39.086749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:09:39.086821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:09:39.823176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:10:09.823067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:10:39.092613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:10:39.092664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:10:39.823168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:11:09.823089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:11:39.098380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:11:39.098416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:11:39.823171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:12:09.823224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:12:39.104009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:12:39.104067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:12:39.823109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:13:09.823168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:13:39.108708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:13:39.108745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:13:39.823254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:14:09.823169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:14:39.113870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:14:39.113921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:14:39.823241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:15:09.823270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:15:39.117558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:15:39.117594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:15:39.823025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:16:09.823224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:16:39.121757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:16:39.121803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:16:39.823278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:17:09.823078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:17:39.128305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:17:39.128357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:17:39.823086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:18:09.823132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:18:39.134636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:18:39.134681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:18:39.823180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:19:09.823133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:19:39.138668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:19:39.138718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:19:39.823153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:20:09.823155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:20:39.142757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:20:39.142792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:20:39.823227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:21:09.823143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:21:39.146476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:21:39.146509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:21:39.823147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:22:09.823137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:22:39.151075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:22:39.151133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:22:39.823200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:23:09.823118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:23:39.154025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:23:39.154069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:23:39.823673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:24:09.823126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:24:39.157899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:24:39.157948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:24:39.823121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:25:09.823189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:25:39.162875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:25:39.162939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/30 04:25:39.823187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/30 04:26:09.823122 metrics.go:34: INFO No non-zero metrics in the last 30s