Results

          2022/03/24 03:12:52.444075 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/24 03:12:52.444130 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 03:12:52.444216 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 03:12:52.444302 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 03:12:52.444422 publish.go:295: INFO Publisher name: onap-vfc-vnflcm-84bd7747bf-vkmjq
2022/03/24 03:12:52.444665 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 03:12:52.444692 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 03:12:52.444670 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 03:12:52.445162 beat.go:221: INFO filebeat start running.
2022/03/24 03:12:52.445307 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 03:12:52.448790 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 03:12:52.449119 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 03:12:52.449247 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 03:12:52.449556 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 03:12:52.449738 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/24 03:12:52.449799 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 03:12:52.449836 registrar.go:236: INFO Starting Registrar
2022/03/24 03:12:52.449892 sync.go:41: INFO Start sending events to output
2022/03/24 03:12:52.449951 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 03:12:52.450572 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/24 03:13:22.445753 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/24 03:13:52.445332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:22.445261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:52.445278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:22.445189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:52.445246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:22.445266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:52.445232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:22.445246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:52.445281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:57.467015 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:18:22.445281 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/24 03:18:52.445242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:22.445301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:52.445252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:22.445288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:52.445432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:22.445252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:52.445231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:22.447863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:52.445214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:22.445253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:52.445295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:22.445201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:52.445210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:22.445309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:52.445255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:22.445281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:52.445266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:22.445199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:52.445191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:22.445241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:52.445370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:22.445239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:52.445260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:22.445236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:52.445136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:22.445210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:52.445203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:22.445247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:52.445170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:22.445229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:52.445202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:22.445251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:52.445213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:22.445304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:52.445252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:22.445183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:52.445258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:22.445233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:52.445218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:22.445215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:52.445259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:22.445327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:52.445399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:12.639551 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/24 03:40:17.595933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:17.595968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:18.599436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:18.599470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:20.602195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:20.602253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:22.445307 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/24 03:40:24.607552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:24.607587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:32.636693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:32.636869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:48.642248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:48.642296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:52.445453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:20.661539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:20.661723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:22.445263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:52.445213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:20.668445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:20.668508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:22.445226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:52.445290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:20.675775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:20.675823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:22.445323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:52.445283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:20.681480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:20.681521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:22.445191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:52.445222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:17.653332 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:45:20.689060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:20.689119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:22.445164 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/24 03:45:52.445227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:20.696003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:20.696046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:22.445231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:52.445259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:20.704711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:20.704756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:22.447505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:52.445386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:20.711494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:20.711538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:22.445211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:52.445151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:20.722109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:20.722144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:22.445864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:52.445183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:20.734043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:20.734092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:22.445242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:52.452356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:20.745892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:20.745946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:22.445184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:52.445205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:20.751988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:20.752022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:22.445215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:52.445750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:20.758580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:20.758613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:22.445273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:52.445158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:20.766281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:20.766324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:22.445216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:52.445170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:20.773636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:20.773686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:22.445347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:52.445231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:20.780748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:20.780817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:22.446294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:52.445282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:20.788500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:20.788538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:22.445231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:52.445303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:20.797597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:20.797645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:22.445282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:52.445189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:20.803656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:20.803690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:22.445277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:52.445263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:20.811111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:20.811157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:22.445148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:52.445449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:20.827630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:20.827686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:22.445435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:52.445228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:20.842833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:20.842879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:22.445260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:52.445165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:20.849682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:20.849723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:22.445509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:52.445236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:20.856615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:20.856650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:22.445231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:52.445321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:20.863800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:20.863850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:22.445194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:52.445172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:20.871459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:20.871525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:22.445262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:52.445199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:20.877945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:20.877976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:22.445362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:52.445440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:20.893305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:20.893346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:22.445271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:52.445385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:20.899452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:20.899485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:22.445188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:52.445227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:20.905661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:20.905710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:22.445245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:52.445301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:20.913655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:20.913700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:22.445162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:52.445248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:20.927834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:20.928010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:22.445208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:52.445291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:20.939315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:20.939353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:22.445165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:52.445200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:20.945804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:20.945862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:22.445247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:52.445386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:20.952765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:20.952804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:22.445249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:52.445292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:20.960050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:20.960104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:22.445131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:52.445184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:20.966588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:20.966634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:22.445184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:52.445311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:20.975835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:20.975870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:22.445177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:52.445207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:20.984433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:20.984484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:22.445242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:52.445188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:20.991553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:20.991596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:22.445219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:52.445227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:20.998408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:20.998443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:22.445293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:52.445407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:21.005580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:21.005672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:22.445240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:52.445284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:21.016887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:21.016920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:22.445295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:52.445224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:21.027449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:21.027559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:22.445206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:52.445378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:21.037335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:21.037424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:22.445198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:52.445251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:21.044913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:21.044958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:22.445430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:52.445287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:21.052775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:21.052809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:22.445187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:52.445179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:21.060057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:21.060095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:22.445239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:52.445233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:21.068245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:21.068315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:22.445550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:52.445215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:21.080778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:21.080816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:22.445300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:52.445264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:21.088200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:21.088249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:22.445230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:52.445232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:21.096619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:21.096667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:22.445209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:52.445257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:21.102765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:21.102803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:22.445217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:52.445228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:21.110073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:21.110108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:22.445220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:52.445267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:21.116423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:21.116615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:22.445222 metrics.go:34: INFO No non-zero metrics in the last 30s