By type
2022/03/10 03:15:55.577355 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/10 03:15:55.577412 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 03:15:55.577491 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 03:15:55.577554 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 03:15:55.577660 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-ccvdf
2022/03/10 03:15:55.577872 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 03:15:55.577890 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 03:15:55.578561 beat.go:221: INFO filebeat start running.
2022/03/10 03:15:55.578656 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 03:15:55.580474 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 03:15:55.584737 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 03:15:55.584810 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 03:15:55.584868 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 03:15:55.585081 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 03:15:55.585199 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/10 03:15:55.585237 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 03:15:55.585309 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 03:15:55.585257 registrar.go:236: INFO Starting Registrar
2022/03/10 03:15:55.585426 sync.go:41: INFO Start sending events to output
2022/03/10 03:15:55.589266 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/10 03:16:25.580974 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/10 03:16:55.581305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:25.580981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:55.580992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:25.580932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:55.581189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:25.580842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:55.581202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:25.580836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:55.581010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:21:00.601836 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:21:25.580873 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/10 03:21:55.580944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:25.580851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:55.580862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:25.580941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:55.580862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:25.580861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:55.580834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:25.580832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:55.580877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:25.580877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:55.580927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:25.580888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:55.580965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:25.580824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:55.580791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:25.581299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:55.580855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:25.580891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:55.580851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:25.580922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:55.580842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:25.580936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:55.580870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:25.580888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:55.580864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:25.580786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:55.580849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:25.580975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:55.580871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:25.580932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:55.580981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:25.581178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:55.580897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:25.580843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:55.580852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:25.580923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:55.580941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:25.580894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:55.580843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:25.580815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:55.580833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:25.580922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:55.581059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:25.580869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:55.580922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:25.580972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:45.776338 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/10 03:44:50.723383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:50.723637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:51.733888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:51.733972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:53.739167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:53.739236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:55.581051 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/10 03:44:57.746462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:57.746502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:05.755153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:05.755191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:21.776873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:21.776933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:25.580954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:45:53.794902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:53.794975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:55.580913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:25.580885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:53.813208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:46:53.813272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:46:55.581573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:25.580842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:53.833317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:47:53.833379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:47:55.581394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:25.580879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:53.851852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:48:53.851925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:48:55.580876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:25.580867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:50.796226 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:49:53.871852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:49:53.871924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:49:55.580916 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/10 03:50:25.580868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:50:53.908138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:50:53.908200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:50:55.580885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:25.580987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:53.926088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:51:53.926263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:51:55.580855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:25.581119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:53.945864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:52:53.945922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:52:55.580909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:25.580860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:53.963309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:53:53.963384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:53:55.580812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:25.580847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:53.981849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:54:53.981889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:54:55.580870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:25.580891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:54.003348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:55:54.003644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:55:55.580902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:25.582334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:54.023117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:56:54.023175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:56:55.580914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:25.580952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:54.041974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:57:54.042035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:57:55.580804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:25.580912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:54.059528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:58:54.059982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:58:55.580923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:25.580863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:54.077485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:59:54.077524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:59:55.580899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:25.580857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:54.093597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:00:54.093646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:00:55.580906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:25.580861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:54.110115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:01:54.110270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:01:55.581039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:25.580943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:54.128177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:02:54.128233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:02:55.583719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:25.580955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:54.146306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:03:54.146361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:03:55.580883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:25.580868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:54.165685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:04:54.165732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:04:55.581320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:25.580899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:54.183998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:05:54.184057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:05:55.580875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:25.581519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:54.202424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:06:54.202497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:06:55.580850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:25.580864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:54.223758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:07:54.224225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:07:55.580897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:25.580884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:54.241785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:08:54.241847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:08:55.580901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:25.580873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:54.259053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:09:54.259109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:09:55.580902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:25.580890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:54.275094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:10:54.275142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:10:55.580878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:25.580842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:54.293354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:11:54.293393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:11:55.580864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:25.580987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:54.310857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:12:54.310899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:12:55.581064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:25.580801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:54.327739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:13:54.327799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:13:55.581038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:25.580888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:54.346244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:14:54.346295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:14:55.580853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:25.581004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:54.364836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:15:54.364905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:15:55.580890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:25.580904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:54.384204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:16:54.384254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:16:55.580951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:25.580860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:54.402588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:17:54.402652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:17:55.580942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:25.580843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:54.420819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:18:54.420868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:18:55.580851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:25.580939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:54.439533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:19:54.439596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:19:55.580938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:25.581179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:54.458496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:20:54.458548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:20:55.580910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:25.580869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:54.475684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:21:54.475724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:21:55.580810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:25.580883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:54.495533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:22:54.495739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:22:55.580969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:25.580910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:54.514416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:23:54.514466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:23:55.580844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:25.580913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:54.532232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:24:54.532272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:24:55.580903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:25.580860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:54.551291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:25:54.551370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:25:55.580841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:25.580842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:54.569350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:26:54.569397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:26:55.580874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:25.580873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:54.586576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:27:54.586648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:27:55.580930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:25.580872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:54.606454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:28:54.606512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:28:55.580915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:25.580964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:54.626617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:29:54.626665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:29:55.580967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:25.580988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:54.643914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:30:54.643994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:30:55.580888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:25.580876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:54.662852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:31:54.662923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:31:55.580830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:25.581240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:54.680840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:32:54.680895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:32:55.580871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:25.580934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:54.701846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:33:54.701906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:33:55.580904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:25.580884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:54.719042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:34:54.719082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:34:55.580822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:25.580867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:54.736911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:35:54.736962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:35:55.580909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:25.581000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:54.754995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:36:54.755081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:36:55.580920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:25.580976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:54.774440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:37:54.774527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:37:55.581035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:25.580886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:54.793039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:38:54.793105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:38:55.581125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:39:25.580986 metrics.go:34: INFO No non-zero metrics in the last 30s