By type
2022/03/07 03:28:22.477552 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/07 03:28:22.477597 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/07 03:28:22.477657 logstash.go:90: INFO Max Retries set to: 3
2022/03/07 03:28:22.477714 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/07 03:28:22.477768 metrics.go:23: INFO Metrics logging every 30s
2022/03/07 03:28:22.477877 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-k4m5t
2022/03/07 03:28:22.478061 async.go:63: INFO Flush Interval set to: 1s
2022/03/07 03:28:22.478097 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/07 03:28:22.478566 beat.go:221: INFO filebeat start running.
2022/03/07 03:28:22.478644 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/07 03:28:22.484004 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/07 03:28:22.484054 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/07 03:28:22.484097 crawler.go:38: INFO Loading Prospectors: 1
2022/03/07 03:28:22.484267 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/07 03:28:22.484349 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/07 03:28:22.484369 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/07 03:28:22.484406 registrar.go:236: INFO Starting Registrar
2022/03/07 03:28:22.484454 sync.go:41: INFO Start sending events to output
2022/03/07 03:28:22.484483 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/07 03:28:22.485010 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/07 03:28:52.478218 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/03/07 03:29:22.478297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:29:52.478226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:30:22.478173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:30:52.478069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:31:22.478212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:31:52.478327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:32:22.478264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:32:52.478159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:33:22.478115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:33:27.500631 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/07 03:33:52.478178 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/07 03:34:22.478154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:34:52.478099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:35:22.478188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:35:52.478062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:36:22.478132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:36:52.478176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:37:22.478295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:37:52.478148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:38:22.478182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:38:52.478066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:39:22.478162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:39:52.478115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:40:22.478136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:40:52.478130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:41:22.478091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:41:52.478157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:42:22.478060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:42:52.478088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:43:22.478053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:43:52.478456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:44:22.478212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:44:52.478237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:45:22.478191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:45:52.478380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:46:22.478162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:46:52.478185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:47:22.478171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:47:52.478100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:48:22.478089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:48:52.479392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:49:22.478060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:49:52.478181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:50:22.478104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:50:52.478141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:51:22.478259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:51:52.478225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:52:22.478192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:52:52.478128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:53:22.478206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:53:52.478334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:54:22.478245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:54:52.478199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:55:22.478095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:55:52.478049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:56:22.478225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:56:52.478144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:57:22.478370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:57:52.478088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:58:22.478080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:58:42.642580 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/07 03:58:47.649480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:47.649521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:48.652916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:48.652972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:50.657596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:50.657644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:52.478328 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/03/07 03:58:54.667529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:58:54.667571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:02.671369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:02.671455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:18.691168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:18.691222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:22.478100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 03:59:50.710672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:50.710718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 03:59:52.478107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:00:22.478164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:00:50.728870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:00:50.728908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:00:52.478123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:01:22.478172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:01:50.748238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:01:50.748367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:01:52.478078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:02:22.478084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:02:50.767088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:02:50.767417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:02:52.478286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:03:22.478145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:03:47.658251 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/07 04:03:50.785997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:03:50.786039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:03:52.478322 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/07 04:04:22.478197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:04:50.804209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:04:50.804258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:04:52.478098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:05:22.478154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:05:50.822949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:05:50.823028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:05:52.478127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:06:22.478055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:06:50.840607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:06:50.840644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:06:52.478128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:07:22.478064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:07:50.859796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:07:50.859897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:07:52.478081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:08:22.478098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:08:50.877615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:08:50.877655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:08:52.478129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:09:22.478255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:09:50.896101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:09:50.896155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:09:52.478092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:10:22.478066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:10:50.914338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:10:50.914377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:10:52.478288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:11:22.478127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:11:50.933120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:11:50.933164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:11:52.478088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:12:22.478096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:12:50.953604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:12:50.953643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:12:52.478128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:13:22.478089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:13:50.972309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:13:50.972471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:13:52.478132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:14:22.478086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:14:50.993405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:14:50.993457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:14:52.478113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:15:22.478107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:15:51.013090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:15:51.013139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:15:52.478064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:16:22.478049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:16:51.031665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:16:51.031716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:16:52.478131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:17:22.478126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:17:51.050296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:17:51.050372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:17:52.478199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:18:22.478716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:18:51.068238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:18:51.068310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:18:52.478196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:19:22.478114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:19:51.087919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:19:51.087961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:19:52.478104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:20:22.478074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:20:51.109223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:20:51.109262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:20:52.478269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:21:22.478137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:21:51.127792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:21:51.127855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:21:52.478112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:22:22.478078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:22:51.145695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:22:51.145743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:22:52.478124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:23:22.478122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:23:51.164043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:23:51.164082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:23:52.478075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:24:22.478060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:24:51.182196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:24:51.182253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:24:52.478100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:25:22.478115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:25:51.200729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:25:51.201065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:25:52.478195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:26:22.478131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:26:51.219149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:26:51.219207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:26:52.478094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:27:22.478134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:27:51.240931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:27:51.240973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:27:52.478156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:28:22.478139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:28:51.261346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:28:51.261389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:28:52.478192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:29:22.478151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:29:51.281594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:29:51.281641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:29:52.478100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:30:22.478110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:30:51.302082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:30:51.302373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:30:52.478161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:31:22.478134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:31:51.321855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:31:51.321913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:31:52.478098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:32:22.478057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:32:51.342119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:32:51.342173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:32:52.478075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:33:22.478198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:33:51.360708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:33:51.360752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:33:52.480640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:34:22.478111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:34:51.380005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:34:51.380062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:34:52.478197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:35:22.478270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:35:51.401900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:35:51.401958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:35:52.478164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:36:22.478138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:36:51.420245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:36:51.420297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:36:52.478758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:37:22.478106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:37:51.443893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:37:51.443934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:37:52.478169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:38:22.478067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:38:51.462824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:38:51.463059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:38:52.478091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:39:22.478071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:39:51.482208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:39:51.482249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:39:52.478190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:40:22.478161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:40:51.500063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:40:51.500106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:40:52.478117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:41:22.478091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:41:51.518955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:41:51.518997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:41:52.478096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:42:22.478152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:42:51.537731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:42:51.537787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:42:52.478109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:43:22.478081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:43:51.559132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:43:51.559199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:43:52.478260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:44:22.478340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:44:51.580296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:44:51.580426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:44:52.478136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:45:22.478149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:45:51.598643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:45:51.598684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:45:52.478052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:46:22.478296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:46:51.621788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:46:51.621830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:46:52.478123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:47:22.478164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:47:51.639257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:47:51.639312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:47:52.478116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:48:22.478154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:48:51.660350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:48:51.660414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:48:52.478080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:49:22.478053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:49:51.678142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:49:51.678208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:49:52.478141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:50:22.478058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:50:51.701170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:50:51.701214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:50:52.478175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:51:22.478108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:51:51.719442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:51:51.719489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:51:52.478090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:52:22.478125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:52:51.742216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:52:51.742254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:52:52.478352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:53:22.478065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:53:51.764457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:53:51.764529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:53:52.478172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:54:22.478119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:54:51.781501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:54:51.781562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:54:52.478084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:55:22.478249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:55:51.807902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:55:51.807942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:55:52.478124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:56:22.478091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:56:51.826464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:56:51.826507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:56:52.478112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:57:22.478138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:57:51.846824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:57:51.846870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:57:52.478139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:58:22.478060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:58:51.864131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:58:51.864182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:58:52.478077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:59:22.478111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/07 04:59:51.881322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:59:51.881377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/07 04:59:52.478100 metrics.go:34: INFO No non-zero metrics in the last 30s