Results

          2022/03/26 03:14:31.670398 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/26 03:14:31.670483 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/26 03:14:31.670518 metrics.go:23: INFO Metrics logging every 30s
2022/03/26 03:14:31.670585 logstash.go:90: INFO Max Retries set to: 3
2022/03/26 03:14:31.670690 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/26 03:14:31.670827 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-sd56z
2022/03/26 03:14:31.671069 async.go:63: INFO Flush Interval set to: 1s
2022/03/26 03:14:31.671093 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/26 03:14:31.671549 beat.go:221: INFO filebeat start running.
2022/03/26 03:14:31.671644 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/26 03:14:31.680963 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/26 03:14:31.681048 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/26 03:14:31.681095 crawler.go:38: INFO Loading Prospectors: 1
2022/03/26 03:14:31.681134 registrar.go:236: INFO Starting Registrar
2022/03/26 03:14:31.681242 sync.go:41: INFO Start sending events to output
2022/03/26 03:14:31.681292 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/26 03:14:31.681313 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/26 03:14:31.681385 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/26 03:14:31.681423 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/26 03:14:31.682271 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/26 03:15:01.670904 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/26 03:15:31.670982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:01.670954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:31.670897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:01.670801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:31.670870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:01.670916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:31.670800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:01.670874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:31.670850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:36.691908 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:20:01.670931 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/26 03:20:31.670938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:01.671106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:31.670841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:01.671121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:31.670845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:01.670889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:31.670889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:01.670803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:31.670961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:01.670884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:31.670930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:01.670824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:31.670936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:01.670898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:31.670920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:01.671005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:31.670836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:01.670795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:31.670838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:01.670942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:31.670856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:01.670883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:31.670832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:01.670822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:31.670853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:01.670913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:31.670905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:01.670855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:31.670867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:01.670861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:31.670848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:01.670976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:31.670847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:01.670935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:31.670894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:01.671027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:38:31.670882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:01.670901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:39:31.670900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:01.670923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:40:31.670878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:01.671051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:41:31.670871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:01.670857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:31.670802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:42:51.812220 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/26 03:42:56.801426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:56.801465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:57.805043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:57.805081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:59.811246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:42:59.811282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:01.670884 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/26 03:43:03.817163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:03.817198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:11.825760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:11.825910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:27.843867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:27.844129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:31.670868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:43:59.859802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:43:59.859983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:44:01.670904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:31.670884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:44:59.875732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:44:59.875772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:45:01.670912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:31.670849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:45:59.890945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:45:59.890988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:46:01.670800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:31.670847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:46:59.907188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:46:59.907222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:47:01.670884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:31.670830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:47:59.924028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:47:59.924437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:48:01.670892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:31.670868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:48:59.942267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:48:59.942321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:49:01.670912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:31.670910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:49:59.962280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:49:59.962326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:50:01.670818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:31.670947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:50:59.981783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:50:59.981838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:51:01.670861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:51:26.832263 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:51:31.670961 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/26 03:51:59.998436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:51:59.998471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:52:01.670890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:52:31.670936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:00.013899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:53:00.013939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:53:01.670848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:53:31.670896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:00.029915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:54:00.029960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:54:01.670897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:54:31.670903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:00.046206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:55:00.046244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:55:01.670860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:55:31.670862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:00.061528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:56:00.061611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:56:01.670835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:56:31.670917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:00.077943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:57:00.077993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:57:01.671075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:57:31.670911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:00.093941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:58:00.093982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:58:01.670947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:58:31.670815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:00.115351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:59:00.115425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:59:01.670878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:59:31.670924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:00.132873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:00:00.132915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:00:01.670861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:00:31.670866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:00.150623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:01:00.150670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:01:01.670854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:01:31.671252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:00.166880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:02:00.166931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:02:01.670879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:02:31.670857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:00.184596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:03:00.184650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:03:01.671059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:03:31.670845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:00.202730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:04:00.202791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:04:01.670885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:04:31.670862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:00.220957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:05:00.221169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:05:01.670885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:05:31.670827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:00.240237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:06:00.240276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:06:01.671010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:06:31.670871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:00.257113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:07:00.257155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:07:01.670799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:07:31.670864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:00.274200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:08:00.274246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:08:01.670877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:08:31.670908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:00.291139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:09:00.291183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:09:01.670827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:09:31.670863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:00.308829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:10:00.308866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:10:01.670815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:10:31.670893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:00.327369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:11:00.327408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:11:01.670851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:11:31.670911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:00.344441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:12:00.344486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:12:01.670905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:12:31.670837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:00.361726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:13:00.361766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:13:01.670911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:13:31.670817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:00.378731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:14:00.378796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:14:01.670842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:14:31.670983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:00.405906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:15:00.405963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:15:01.670832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:15:31.670827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:00.423190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:16:00.423231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:16:01.670881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:16:31.670973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:00.440163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:17:00.440228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:17:01.670893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:17:31.671168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:00.457150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:18:00.457192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:18:01.670890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:18:31.670942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:00.473772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:19:00.473819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:19:01.670939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:19:31.671035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:00.490651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:20:00.490784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:20:01.670856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:20:31.671024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:00.506992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:21:00.507044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:21:01.670898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:21:31.670853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:00.523906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:22:00.523959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:22:01.670977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:22:31.671626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:00.541841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:23:00.541878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:23:01.670797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:23:31.670834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:00.558108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:24:00.558147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:24:01.670837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:24:31.670886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:00.574666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:25:00.574711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:25:01.670911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:25:31.670828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:00.591825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:26:00.591870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:26:01.670896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:26:31.671180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:00.608626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:27:00.608774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:27:01.670832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:27:31.670872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:00.626057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:28:00.626385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:28:01.670899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:28:31.670952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:00.644050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:29:00.644096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:29:01.670931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:29:31.670875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:00.660224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:30:00.660282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:30:01.670882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:30:31.670849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:00.677249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:31:00.677471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:31:01.670910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:31:31.670902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:00.693883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:32:00.693930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:32:01.670816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:32:31.670854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:00.711730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:33:00.711790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:33:01.670845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:33:31.670909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:00.733335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:34:00.733389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:34:01.670872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:34:31.670835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:00.751604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:35:00.751650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:35:01.670914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:35:31.670994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:00.769567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:36:00.769706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:36:01.670857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:36:31.670805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:00.785751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:37:00.785795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:37:01.670946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:37:31.670926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:00.814389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:38:00.814567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:38:01.670870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:38:31.670994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:00.833767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:39:00.833972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:39:01.670874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:39:31.670802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:00.853907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:40:00.853982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:40:01.670854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:40:31.670817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:00.871334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:41:00.871404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:41:01.670871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:41:31.671038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 04:42:00.891012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:42:00.891079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 04:42:01.670895 metrics.go:34: INFO No non-zero metrics in the last 30s