2022/03/14 03:18:55.829439 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/14 03:18:55.829504 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/14 03:18:55.829620 logstash.go:90: INFO Max Retries set to: 3
2022/03/14 03:18:55.829725 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/14 03:18:55.829852 publish.go:295: INFO Publisher name: onap-vfc-vnflcm-84bd7747bf-2r6bp
2022/03/14 03:18:55.830134 async.go:63: INFO Flush Interval set to: 1s
2022/03/14 03:18:55.830146 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/14 03:18:55.830674 metrics.go:23: INFO Metrics logging every 30s
2022/03/14 03:18:55.830790 beat.go:221: INFO filebeat start running.
2022/03/14 03:18:55.830958 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/14 03:18:55.854254 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/14 03:18:55.854449 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/14 03:18:55.854628 crawler.go:38: INFO Loading Prospectors: 1
2022/03/14 03:18:55.855102 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/14 03:18:55.855186 registrar.go:236: INFO Starting Registrar
2022/03/14 03:18:55.855292 sync.go:41: INFO Start sending events to output
2022/03/14 03:18:55.855439 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/14 03:18:55.855548 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/14 03:18:55.855626 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/14 03:18:55.856907 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/14 03:19:25.831320 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/14 03:19:55.831100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:25.831078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:55.831190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:25.831092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:55.831000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:25.831151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:55.831187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:25.831000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:55.831047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:00.899633 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/14 03:24:25.830995 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/14 03:24:55.831158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:25.831063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:55.831087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:25.831041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:55.831037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:25.831013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:55.831049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:25.831092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:55.835217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:25.831119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:55.830970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:25.830957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:55.831151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:25.831048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:55.831093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:25.830949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:55.830926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:25.831067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:55.831078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:25.830961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:55.831084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:25.830956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:55.831086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:25.831033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:55.831305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:25.831192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:55.831228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:25.831051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:55.830921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:25.831216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:55.831044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:25.831000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:55.830959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:25.830938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:55.830994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:25.830989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:55.831057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:25.831004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:55.831055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:25.830961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:55.830918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:25.831034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:55.831108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:25.831002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:55.830938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:25.831053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:55.831217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:56.037962 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/14 03:48:01.028423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:01.028828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:02.032729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:02.032902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:04.036770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:04.036811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:08.043291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:08.043331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:16.050582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:16.050719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:25.831146 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/14 03:48:32.073436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:32.073491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:55.831138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:04.090689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:04.090912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:25.831860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:55.831036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:04.108044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:04.108125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:25.830975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:55.830941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:04.124993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:04.125044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:25.830958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:55.831078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:04.143560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:04.143628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:25.830950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:55.831260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:53:01.050732 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/14 03:53:04.161916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:04.161960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:25.831000 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/14 03:53:55.831120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:04.181058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:04.181140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:25.830965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:55.830965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:04.200009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:04.200061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:25.831028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:55.831199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:04.216706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:04.216786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:25.831066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:55.831049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:04.236150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:04.236201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:25.831080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:55.830931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:04.254117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:04.254164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:25.830982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:55.830987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:04.271782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:04.271831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:25.830999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:55.830982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:04.288129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:04.288207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:25.830963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:55.830990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:04.310606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:04.310661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:25.831007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:55.831170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:04.328687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:04.328745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:25.831060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:55.831018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:04.346805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:04.346865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:25.831100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:55.831102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:04.364422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:04.364466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:25.831230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:55.831915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:04.383737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:04.383858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:25.830934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:55.830963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:04.407330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:04.407388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:25.831202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:55.831028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:04.424640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:04.424706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:25.830989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:55.831023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:04.455518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:04.455564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:25.831281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:55.830953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:04.474284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:04.474363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:25.831604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:55.831090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:04.549885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:04.549950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:25.831132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:55.831018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:04.567516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:04.567575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:25.831105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:55.831081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:04.585149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:04.585229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:25.831099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:55.838950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:04.606077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:04.606136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:25.831027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:55.830963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:04.623755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:04.623796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:25.831293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:55.830982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:04.642522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:04.642807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:25.831089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:55.830999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:04.660443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:04.660716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:25.831040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:55.831079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:04.679414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:04.679464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:25.831288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:55.833064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:04.696778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:04.696821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:25.830980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:55.830944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:04.714090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:04.714139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:25.830994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:55.831099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:04.733357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:04.733802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:25.836081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:55.831129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:04.754366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:04.754406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:25.831024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:55.831016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:04.773843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:04.773903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:25.831035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:55.839928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:04.792685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:04.792737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:25.831051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:55.830991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:04.811338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:04.811385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:25.831008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:55.830963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:04.830416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:04.830480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:25.831077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:55.831119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:04.849903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:04.849986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:25.831037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:55.830992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:04.867346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:04.867391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:25.830988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:55.831015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:04.885668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:04.885750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:25.831805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:55.831156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:04.908510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:04.908566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:25.830908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:55.831097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:04.926698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:04.926741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:25.831267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:55.831093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:04.946747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:04.946795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:25.831098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:55.830948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:04.966095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:04.966159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:25.830989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:55.830996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:04.984949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:04.985003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:25.833177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:55.831008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:05.003631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:05.003700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:25.831096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:55.831022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:05.020885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:05.020933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:25.831053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:55.831004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:36:05.036531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:05.036593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:25.831133 metrics.go:34: INFO No non-zero metrics in the last 30s