By type
2022/03/11 03:18:39.445779 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/11 03:18:39.445841 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/11 03:18:39.446021 logstash.go:90: INFO Max Retries set to: 3
2022/03/11 03:18:39.446230 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/11 03:18:39.446434 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-qsx9m
2022/03/11 03:18:39.446665 async.go:63: INFO Flush Interval set to: 1s
2022/03/11 03:18:39.446682 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/11 03:18:39.447196 beat.go:221: INFO filebeat start running.
2022/03/11 03:18:39.447291 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/11 03:18:39.447852 metrics.go:23: INFO Metrics logging every 30s
2022/03/11 03:18:39.450970 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/11 03:18:39.451025 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/11 03:18:39.451234 crawler.go:38: INFO Loading Prospectors: 1
2022/03/11 03:18:39.451497 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/11 03:18:39.451606 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/11 03:18:39.451619 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/11 03:18:39.451629 registrar.go:236: INFO Starting Registrar
2022/03/11 03:18:39.451647 sync.go:41: INFO Start sending events to output
2022/03/11 03:18:39.451674 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/11 03:18:39.452214 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/11 03:19:09.452242 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/11 03:19:39.462062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:09.453578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:39.451239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:09.459913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:39.455021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:09.448313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:39.451290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:09.448251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:39.448627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:44.481416 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:24:09.452298 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/11 03:24:39.451573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:09.449437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:39.448357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:09.453447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:39.448362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:09.448236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:39.449826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:09.451449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:39.450455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:09.448176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:39.453416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:09.448265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:39.459511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:09.448447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:39.448350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:09.457404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:39.451359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:09.449220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:39.448237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:09.451436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:39.448165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:09.450523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:39.456480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:09.453964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:39.448346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:09.448158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:39.448313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:09.448328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:39.448536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:09.455281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:39.448620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:09.448140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:39.451043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:09.448562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:39.448149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:09.452342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:39.448865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:09.449659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:39.448923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:09.451642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:39.448220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:09.451616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:39.451395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:09.448247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:39.454116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:09.448179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:39.448174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:49.684356 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/11 03:47:49.691731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:49.691786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:50.696505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:50.696556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:52.701489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:52.701516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:56.707837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:56.707928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:04.725852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:04.725898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:09.448334 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/11 03:48:20.733831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:20.734644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:39.448129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:48:52.754514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:52.754602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:09.448641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:39.448215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:52.762047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:52.762093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:09.449286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:39.453925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:52.770543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:52.770586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:09.453947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:39.448141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:52.777108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:52.777241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:09.448307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:39.450914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:52.784624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:52.784672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:54.701336 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:53:09.451423 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/11 03:53:39.448175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:52.793043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:52.793108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:09.448193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:39.455408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:52.800016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:52.800063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:09.454019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:39.448167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:52.807315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:52.807357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:09.448147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:39.448223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:52.814891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:52.814959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:09.448167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:39.448213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:52.820923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:52.820967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:09.448118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:39.448867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:52.827222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:52.827272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:09.453989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:39.448204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:52.834348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:52.834396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:09.455449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:39.448335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:52.841257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:52.841299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:09.448488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:39.456891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:52.848204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:52.848268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:09.448242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:39.448230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:52.855609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:52.855659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:09.448324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:39.451484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:52.862825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:52.862872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:09.455459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:39.448222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:52.868838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:52.868891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:09.452029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:39.448162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:52.877204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:52.877239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:09.448158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:39.448239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:52.895611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:52.895795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:09.460608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:39.448215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:52.902597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:52.902647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:09.449684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:39.449569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:52.910241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:52.910286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:09.448168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:39.448418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:52.917334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:52.917373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:09.448267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:39.449958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:52.925533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:52.925694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:09.448669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:39.454227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:52.932408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:52.932452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:09.448116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:39.448186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:52.939379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:52.939438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:09.455554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:39.455368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:52.960551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:52.960605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:09.448200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:39.448254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:52.967180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:52.967250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:09.456250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:39.455320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:52.973265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:52.973308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:09.455285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:39.451317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:52.984221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:52.984288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:09.459515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:39.463286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:52.990257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:52.990317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:09.459396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:39.448530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:52.996772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:52.996815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:09.453371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:39.459464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:53.004180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:53.004235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:09.451310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:39.450357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:53.011595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:53.011639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:09.449212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:39.450145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:53.017836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:53.017875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:09.451529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:39.448182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:53.023921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:53.023963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:09.450414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:39.451269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:53.029827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:53.029867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:09.448400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:39.454721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:53.036328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:53.036372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:09.448357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:39.459524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:53.043806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:53.043846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:09.450475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:39.454718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:53.049871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:53.049934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:09.451772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:39.455842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:53.057212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:53.057256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:09.448162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:39.448173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:53.065120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:53.065160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:09.451912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:39.448143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:53.072509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:53.072561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:09.448182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:39.448176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:53.083281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:53.083318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:09.455343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:39.449709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:53.090172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:53.090211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:09.464063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:39.449586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:53.096848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:53.096890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:33:09.455578 metrics.go:34: INFO No non-zero metrics in the last 30s