By type
2022/03/13 03:18:36.648393 metrics.go:23: INFO Metrics logging every 30s 2022/03/13 03:18:36.648587 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/13 03:18:36.648634 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0 2022/03/13 03:18:36.648765 logstash.go:90: INFO Max Retries set to: 3 2022/03/13 03:18:36.648869 outputs.go:108: INFO Activated logstash as output plugin. 2022/03/13 03:18:36.649000 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-rrmp6 2022/03/13 03:18:36.649471 async.go:63: INFO Flush Interval set to: 1s 2022/03/13 03:18:36.649491 async.go:64: INFO Max Bulk Size set to: 2048 2022/03/13 03:18:36.650389 beat.go:221: INFO filebeat start running. 2022/03/13 03:18:36.650515 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file. 2022/03/13 03:18:36.661251 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry 2022/03/13 03:18:36.661638 registrar.go:123: INFO States Loaded from registrar: 0 2022/03/13 03:18:36.661823 crawler.go:38: INFO Loading Prospectors: 1 2022/03/13 03:18:36.662022 registrar.go:236: INFO Starting Registrar 2022/03/13 03:18:36.662130 sync.go:41: INFO Start sending events to output 2022/03/13 03:18:36.662337 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s 2022/03/13 03:18:36.662627 prospector_log.go:65: INFO Prospector with previous states loaded: 0 2022/03/13 03:18:36.662939 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 2022/03/13 03:18:36.663080 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1 2022/03/13 03:18:36.663977 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log 2022/03/13 03:19:06.649034 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/13 03:19:36.655808 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:20:06.657577 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:20:36.664583 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:21:06.649688 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:21:36.652667 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:22:06.648820 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:22:36.649528 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:23:06.651229 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:23:36.650376 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:23:41.712340 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached. 2022/03/13 03:24:06.650457 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/13 03:24:36.648731 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:25:06.648862 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:25:36.648848 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:26:06.649225 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:26:36.648861 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:27:06.653171 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:27:36.652517 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:28:06.650745 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:28:36.652222 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:29:06.648885 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:29:36.648791 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:30:06.648789 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:30:36.650649 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:31:06.649345 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:31:36.648807 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:32:06.651725 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:32:36.668190 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:33:06.649576 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:33:36.650575 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:34:06.651086 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:34:36.650020 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:35:06.648823 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:35:36.649003 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:36:06.649201 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:36:36.650356 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:37:06.668170 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:37:36.649963 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:38:06.660526 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:38:36.648888 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:39:06.649620 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:39:36.648749 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:40:06.649524 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:40:36.650114 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:41:06.648840 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:41:36.649246 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:42:06.648803 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:42:36.652669 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:43:06.664241 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:43:36.649242 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:44:06.648748 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:44:36.652369 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:45:06.648756 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:45:36.648712 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:46:06.649889 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:46:36.648953 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:47:06.648749 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:47:36.656446 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:48:06.649949 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:48:06.889095 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log 2022/03/13 03:48:06.911349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:06.911403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:07.918200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:07.918244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:09.926532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:09.926627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:13.933199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:13.933257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:21.944712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:21.944757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:36.662627 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/13 03:48:37.978635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:48:37.978689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:49:06.664396 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:49:09.998642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:49:09.998691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:49:36.649836 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:50:06.648739 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:50:10.015572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:50:10.015612 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:50:36.664424 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:51:06.654418 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:51:10.033062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:51:10.033104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:51:36.649179 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:52:06.651610 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:52:10.051250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:52:10.051286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:52:36.684282 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:53:06.650135 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:53:10.072482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:53:10.072524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:53:11.908972 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached. 2022/03/13 03:53:36.660248 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/13 03:54:06.660332 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:54:10.093726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:54:10.093777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:54:36.654561 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:55:06.660255 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:55:10.113217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:55:10.113255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:55:36.648778 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:56:06.650581 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:56:10.141331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:56:10.141379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:56:36.649026 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:57:06.648746 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:57:10.165199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:57:10.165248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:57:36.650042 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:58:06.649946 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:58:10.190086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:58:10.190607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:58:36.649891 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:59:06.663402 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 03:59:10.211537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:59:10.211591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 03:59:36.651722 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:00:06.648838 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:00:10.247262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:00:10.247325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:00:36.648797 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:01:06.650784 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:01:10.295928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:01:10.296339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:01:36.648761 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:02:06.650023 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:02:10.323150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:02:10.323219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:02:36.650944 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:03:06.652326 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:03:10.341159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:03:10.341215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:03:36.649512 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:04:06.649461 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:04:10.364398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:04:10.364442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:04:36.648745 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:05:06.650220 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:05:10.391075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:05:10.391133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:05:36.658286 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:06:06.648807 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:06:10.413552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:06:10.413739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:06:36.650104 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:07:06.648789 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:07:10.430599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:07:10.430649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:07:36.649919 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:08:06.649658 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:08:10.459710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:08:10.459762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:08:36.648800 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:09:06.648682 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:09:10.494613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:09:10.494734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:09:36.648860 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:10:06.649703 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:10:10.514646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:10:10.514694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:10:36.649223 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:11:06.648937 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:11:10.531991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:11:10.532046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:11:36.648778 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:12:06.648830 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:12:10.554676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:12:10.554842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:12:36.652620 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:13:06.648704 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:13:10.576674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:13:10.576827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:13:36.648794 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:14:06.652274 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:14:10.602246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:14:10.602283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:14:36.649173 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:15:06.664037 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:15:10.621407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:15:10.622419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:15:36.654869 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:16:06.650219 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:16:10.638670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:16:10.638721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:16:36.649847 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:17:06.660272 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:17:10.674523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:17:10.674582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:17:36.653144 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:18:06.654426 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:18:10.695537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:18:10.695589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:18:36.665942 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:19:06.648713 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:19:10.719163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:19:10.719207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:19:36.648785 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:20:06.651578 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:20:10.737446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:20:10.737666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:20:36.649965 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:21:06.650715 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:21:10.771009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:21:10.771059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:21:36.651278 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:22:06.650370 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:22:10.793043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:22:10.793105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:22:36.648904 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:23:06.648730 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:23:10.815023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:23:10.815061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:23:36.657654 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:24:06.648674 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:24:10.834871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:24:10.834913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:24:36.649122 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:25:06.658140 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:25:10.864301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:25:10.864947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:25:36.669977 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:26:06.658599 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:26:10.885589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:26:10.885629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:26:36.648741 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:27:06.664251 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:27:10.906109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:27:10.906160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:27:36.648777 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:28:06.652264 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:28:10.943327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:28:10.943360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:28:36.648739 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:29:06.661166 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:29:10.969872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:29:10.969928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:29:36.652683 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:30:06.652597 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:30:10.991145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:30:10.991191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:30:36.655026 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:31:06.649986 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:31:11.013019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:31:11.013073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:31:36.649329 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:32:06.654090 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:32:11.059151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:32:11.059203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:32:36.648855 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:33:06.649835 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:33:11.081977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:33:11.082032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:33:36.651113 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:34:06.654751 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:34:11.099493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:34:11.099547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:34:36.648708 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:35:06.649498 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:35:11.117703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:35:11.117746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:35:36.648839 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:36:06.648832 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:36:11.136395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:36:11.136531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:36:36.664370 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:37:06.648748 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/13 04:37:11.183742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/13 04:37:11.183793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host