Results

          2022/03/23 03:13:32.053054 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/23 03:13:32.053128 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/23 03:13:32.053235 logstash.go:90: INFO Max Retries set to: 3
2022/03/23 03:13:32.053355 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/23 03:13:32.053780 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-qqfxq
2022/03/23 03:13:32.054041 async.go:63: INFO Flush Interval set to: 1s
2022/03/23 03:13:32.054070 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/23 03:13:32.055585 metrics.go:23: INFO Metrics logging every 30s
2022/03/23 03:13:32.055719 beat.go:221: INFO filebeat start running.
2022/03/23 03:13:32.055814 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/23 03:13:32.060897 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/23 03:13:32.061017 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/23 03:13:32.061361 crawler.go:38: INFO Loading Prospectors: 1
2022/03/23 03:13:32.061703 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/23 03:13:32.061877 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/23 03:13:32.061909 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/23 03:13:32.062000 registrar.go:236: INFO Starting Registrar
2022/03/23 03:13:32.062060 sync.go:41: INFO Start sending events to output
2022/03/23 03:13:32.062172 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/23 03:13:32.062918 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/23 03:14:02.055997 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/23 03:14:32.055961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:02.056030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:32.055940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:02.059527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:32.055920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:17:02.055973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:17:32.056016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:02.055935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:32.056029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:37.085357 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/23 03:19:02.056040 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/23 03:19:32.055981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:20:02.056010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:20:32.056027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:21:02.055876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:21:32.056021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:22:02.055950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:22:32.056030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:23:02.055955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:23:32.055891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:24:02.055899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:24:32.056045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:25:02.056062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:25:32.055932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:26:02.056035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:26:32.055961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:27:02.055919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:27:32.055906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:28:02.055985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:28:32.055883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:29:02.056066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:29:32.055907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:30:02.055900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:30:32.055911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:31:02.055939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:31:32.055932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:32:02.056121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:32:32.055859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:33:02.055925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:33:32.055945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:34:02.055959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:34:32.055898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:35:02.055948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:35:32.055882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:36:02.055962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:36:32.056055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:37:02.056113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:37:32.055929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:38:02.056052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:38:32.055947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:39:02.055881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:39:32.056559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:40:02.056446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:40:32.055852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:41:02.055945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:41:32.056017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:42:02.055863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:42:22.225171 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/23 03:42:27.194079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:27.194171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:28.198330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:28.198400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:30.202058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:30.202104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:32.056012 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/23 03:42:34.209287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:34.209332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:42.232422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:42.232478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:58.249771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:58.249814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:43:02.055973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:43:30.268543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:43:30.268600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:43:32.055856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:44:02.055945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:44:30.288337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:44:30.288420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:44:32.056004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:45:02.055866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:45:30.305445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:45:30.305495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:45:32.055926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:46:02.055930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:46:30.325879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:46:30.325924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:46:32.056022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:47:02.055886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:47:27.244191 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/23 03:47:30.349003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:47:30.349041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:47:32.055935 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/23 03:48:02.055855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:48:30.368467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:48:30.368512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:48:32.055956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:49:02.055960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:49:30.386113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:49:30.386440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:49:32.056035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:50:02.055928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:50:30.405451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:50:30.405495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:50:32.055950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:51:02.055950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:51:30.425449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:51:30.425504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:51:32.055974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:52:02.055925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:52:30.443805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:52:30.443869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:52:32.055975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:53:02.055906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:53:30.462681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:53:30.462720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:53:32.055969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:54:02.055918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:54:30.480297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:54:30.480349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:54:32.055969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:55:02.055927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:55:30.501018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:55:30.501069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:55:32.055907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:56:02.055954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:56:30.518918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:56:30.518977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:56:32.055909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:57:02.056005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:57:30.539524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:57:30.539904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:57:32.055940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:58:02.055926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:58:30.559131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:58:30.559481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:58:32.056090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:59:02.055939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:59:30.578144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:59:30.578179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:59:32.055949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:00:02.055910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:00:30.597714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:00:30.597768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:00:32.055916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:01:02.055859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:01:30.616123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:01:30.616227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:01:32.055886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:02:02.055987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:02:30.635836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:02:30.636182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:02:32.055862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:03:02.056050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:03:30.655115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:03:30.655167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:03:32.055993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:04:02.055890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:04:30.671282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:04:30.671463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:04:32.055880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:05:02.055891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:05:30.690537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:05:30.690624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:05:32.056184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:06:02.055964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:06:30.710973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:06:30.711027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:06:32.055866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:07:02.055926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:07:30.734235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:07:30.734318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:07:32.055879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:08:02.055923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:08:30.753631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:08:30.753730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:08:32.056016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:09:02.056187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:09:30.784452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:09:30.784514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:09:32.056156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:10:02.055932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:10:30.804024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:10:30.804065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:10:32.056023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:11:02.055917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:11:30.821521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:11:30.821598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:11:32.055941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:12:02.056049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:12:30.839252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:12:30.839297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:12:32.055908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:13:02.055985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:13:30.856889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:13:30.856986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:13:32.055930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:14:02.055897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:14:30.875743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:14:30.875901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:14:32.055912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:15:02.056262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:15:30.894158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:15:30.894218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:15:32.056127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:16:02.055948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:16:30.915643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:16:30.915689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:16:32.055895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:17:02.055977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:17:30.934324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:17:30.934475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:17:32.056153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:18:02.055972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:18:30.953662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:18:30.953711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:18:32.056011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:19:02.055962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:19:30.973901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:19:30.973941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:19:32.055889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:20:02.056028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:20:30.992483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:20:30.992548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:20:32.055957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:21:02.055955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:21:31.010602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:21:31.010655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:21:32.055923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:22:02.055929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:22:31.031252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:22:31.031289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:22:32.055818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:23:02.056140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:23:31.056175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:23:31.056222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:23:32.055901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:24:02.055997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:24:31.073876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:24:31.073924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:24:32.055826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:25:02.055867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:25:31.097806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:25:31.097860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:25:32.055963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:26:02.055864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:26:31.117607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:26:31.117678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:26:32.056020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:27:02.055901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:27:31.135435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:27:31.135479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:27:32.055891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:28:02.055886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:28:31.153896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:28:31.153944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:28:32.056291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:29:02.055969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:29:31.173956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:29:31.173998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:29:32.055975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:30:02.056031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:30:31.190783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:30:31.190819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:30:32.055916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:31:02.055951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:31:31.208877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:31:31.208928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:31:32.055898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:32:02.056024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:32:31.226458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:32:31.226499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:32:32.055861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:33:02.056192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:33:31.244695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:33:31.244744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:33:32.055952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:34:02.055975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:34:31.263185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:34:31.263222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:34:32.055904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:35:02.055994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:35:31.283084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:35:31.283120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:35:32.055937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:36:02.055901 metrics.go:34: INFO No non-zero metrics in the last 30s