By type
2022/03/05 03:28:59.772704 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/05 03:28:59.772804 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:28:59.772973 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:28:59.773123 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:28:59.773348 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-grkzt
2022/03/05 03:28:59.773760 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:28:59.773798 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:28:59.774499 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:28:59.774575 beat.go:221: INFO filebeat start running.
2022/03/05 03:28:59.774645 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:28:59.780296 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:28:59.780592 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:28:59.780797 registrar.go:236: INFO Starting Registrar
2022/03/05 03:28:59.780891 sync.go:41: INFO Start sending events to output
2022/03/05 03:28:59.780752 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:28:59.781071 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:28:59.781724 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:28:59.782057 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/05 03:28:59.782144 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:28:59.784108 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/05 03:29:29.774943 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/05 03:29:59.775007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:29.774974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:59.774968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:29.777221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:59.775153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:29.775702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:59.774882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:29.774972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:59.775303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:04.807427 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:34:29.777615 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/05 03:34:59.775320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:29.774995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:59.775350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:29.775089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:59.775648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:29.774799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:59.775127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:29.775344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:59.775060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:29.775744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:59.775477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:29.774942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:59.775130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:29.775572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:59.775132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:29.774875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:59.774951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:29.774898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:59.774882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:29.775174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:59.775112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:29.774880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:59.774949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:29.775033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:59.775062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:29.774941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:59.775390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:29.775546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:59.776269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:29.775028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:59.775388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:29.775799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:59.775110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:29.774865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:59.775110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:29.775017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:59.775068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:29.775013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:59.775502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:29.774977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:59.775189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:29.775200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:59.775384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:29.775301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:59.774793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:29.774903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:59.775397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:29.775167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:30.051238 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/05 03:58:35.010044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:35.010094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:36.015674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:36.015736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:38.020174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:38.020215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:42.041002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:42.041297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:50.085425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:50.085474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:59.774901 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/05 03:59:06.107462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:06.107634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:29.775592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:38.131057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:38.131109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:59.776033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:29.774897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:38.156705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:38.156767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:59.775079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:29.775158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:38.182710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:38.182762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:59.775311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:29.774965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:38.202950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:38.203065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:59.775931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:29.775225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:35.065598 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/05 04:03:38.228632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:38.228694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:59.775244 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/05 04:04:29.775315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:38.261299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:38.261360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:59.774916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:29.776197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:38.294807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:38.294876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:59.775043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:29.774819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:38.316719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:38.316780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:59.774893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:29.775287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:38.338344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:38.338415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:59.775140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:29.774945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:38.366731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:38.366817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:59.775305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:29.775328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:38.395764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:38.395873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:59.774863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:29.774894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:38.420294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:38.420360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:59.775088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:29.774959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:38.442735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:38.442797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:59.774915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:29.774922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:38.467436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:38.467490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:59.775015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:29.775776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:38.485658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:38.485714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:59.788662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:29.774953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:38.507911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:38.507981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:59.776709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:29.776166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:38.539408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:38.539479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:59.775070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:29.774844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:38.574780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:38.574840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:59.775835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:29.775536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:38.601647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:38.601791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:59.775848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:29.774988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:38.650719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:38.650825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:59.775496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:29.775239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:38.671154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:38.671216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:59.774894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:29.775893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:38.694402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:38.694459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:59.775162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:29.775114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:38.715977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:38.716051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:59.775160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:29.775167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:38.741192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:38.741248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:59.778325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:29.774933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:38.762647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:38.762724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:59.775054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:29.774804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:38.796746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:38.797044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:59.774964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:29.776385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:38.816778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:38.816854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:59.775073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:29.775286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:38.860735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:38.860791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:59.775330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:29.775143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:38.882489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:38.882543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:59.774941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:29.775491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:38.902599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:38.902663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:59.774991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:29.775545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:38.926335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:38.926389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:59.775064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:29.774826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:38.958954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:38.959002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:59.775240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:29.775455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:38.978144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:38.978201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:59.775081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:29.774905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:39.002217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:39.002292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:59.775115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:29.775018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:39.034390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:39.034457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:59.774990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:29.774824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:39.061532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:39.061589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:59.774898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:29.774870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:39.084079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:39.084306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:59.774970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:29.775064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:39.106802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:39.106868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:59.775041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:29.774913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:39.127517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:39.127582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:59.775399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:29.775520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:39.154213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:39.154290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:59.775067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:29.775279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:39.176474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:39.176536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:59.775026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:29.776137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:39.197013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:39.197054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:59.776180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:29.775732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:39.227544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:39.227606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:59.775021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:29.775138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:39.250481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:39.250552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:59.775230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:29.775993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:39.275183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:39.275247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:59.775209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:29.775272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:39.293732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:39.293799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:59.775551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:29.774842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:39.311348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:39.311389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:59.775194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:29.776078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:39.347177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:39.347223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:59.775622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:29.775354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:39.371187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:39.371261 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:59.778896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:29.774983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:39.395210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:39.395263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:59.775797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:29.775010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:39.420773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:39.420822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:59.774890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:29.775493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:39.459903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:39.460156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:59.775572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:29.774875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:39.481684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:39.481758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:59.776344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:29.775132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:39.512634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:39.512716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:59.775302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:29.774881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:39.561406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:39.561459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:59.777172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:29.778495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:39.639055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:39.639125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:59.775178 metrics.go:34: INFO No non-zero metrics in the last 30s