By type
2022/03/10 03:15:35.817264 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:35.817334 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 03:15:35.817434 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 03:15:35.817478 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 03:15:35.817526 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 03:15:35.817691 publish.go:295: INFO Publisher name: onap-vfc-vnfmgr-8594ffd488-4mqnd
2022/03/10 03:15:35.817937 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 03:15:35.817956 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 03:15:35.818488 beat.go:221: INFO filebeat start running.
2022/03/10 03:15:35.818583 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 03:15:35.823927 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 03:15:35.824005 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 03:15:35.824042 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 03:15:35.824265 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 03:15:35.824354 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/10 03:15:35.824367 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 03:15:35.824386 registrar.go:236: INFO Starting Registrar
2022/03/10 03:15:35.824432 sync.go:41: INFO Start sending events to output
2022/03/10 03:15:35.824464 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 03:15:35.825004 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/10 03:16:05.818034 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:35.818491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:05.818013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:35.818638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:05.817814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:35.817914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:05.817936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:35.817964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:05.817971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:35.817790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:40.841733 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:21:05.818017 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:35.818119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:05.820976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:35.817938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:05.818048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:35.817883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:05.817783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:35.817970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:05.817819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:35.818019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:05.818135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:35.817905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:05.817888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:35.817939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:05.817973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:35.817807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:05.817908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:35.818155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:05.818010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:35.817983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:05.817844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:35.817925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:05.818520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:35.819219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:05.817745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:35.818319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:05.817807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:35.817860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:05.818216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:35.817900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:05.817779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:35.817881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:05.818198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:35.817921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:05.817840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:35.817924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:05.817848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:35.817823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:05.817959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:35.817848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:05.817955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:35.818579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:05.819303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:35.817977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:05.818140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:35.817907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:05.817899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:35.817899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:45.973358 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/10 03:44:50.946915 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.946951 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.950308 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.950345 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.954752 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.954798 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:57.961964 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.962026 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.818524 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:45:05.969390 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.969429 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.987086 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.987134 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:35.817776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:45:54.008485 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:54.008557 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:05.817882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:35.817855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:54.032882 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:54.032966 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:05.817824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:35.818490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:54.051942 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:54.051992 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:05.817876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:35.817832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:54.070278 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:54.070318 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:05.817872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:35.817926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:50.986144 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:49:54.090565 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:54.090616 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:05.817809 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:35.817815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:50:54.111155 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:54.111192 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:05.817883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:35.817906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:54.130737 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:54.130779 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:05.817758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:35.819709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:54.150703 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:54.150739 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:05.817854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:35.817872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:54.168743 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:54.169132 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:05.817763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:35.817844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:54.187518 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:54.187557 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:05.817787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:35.817837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:54.208261 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.208308 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:05.817781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:35.818045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:54.226486 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.226519 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:05.820011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:35.817891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:54.246507 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.246557 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:05.817890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:35.817919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:54.264738 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.264778 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:05.817886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:35.817886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:54.284411 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.284760 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:05.817890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:35.817899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:54.306116 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.306172 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:05.817990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:35.817981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:54.324802 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.324851 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:05.817834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:35.817812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:54.344649 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.344690 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:05.817774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:35.817954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:54.369570 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.369662 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:05.817889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:35.817853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:54.388947 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.389007 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:05.817855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:35.817850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:54.406969 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.407013 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:05.817797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:35.817945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:54.427684 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.427730 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:05.820419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:35.820536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:54.447117 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.447316 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:05.818721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:35.817852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:54.466721 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.466771 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:05.817800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:35.817860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:54.486897 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.487303 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:05.817887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:35.818106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:54.505926 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.505968 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:05.820824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:35.819070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:54.524639 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.524694 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:05.818097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:35.817790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:54.543486 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.543564 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:05.818984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:35.817931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:54.564515 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.564585 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:05.818789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:35.818033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:54.583090 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.583156 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:05.817821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:35.817899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:54.603661 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.603707 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:05.817749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:35.818172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:54.629929 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.629994 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:05.817948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:35.817780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:54.650425 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.650462 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:05.818025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:35.817863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:54.670755 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.670799 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:05.817827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:35.817948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:54.691473 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.691552 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:05.817857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:35.817994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:54.711340 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.711687 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:05.817808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:35.819161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:54.734300 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.734347 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:05.817929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:35.817866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:54.753014 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.753056 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:05.818184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:35.817977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:54.773180 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.773215 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:05.817979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:35.817784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:54.790984 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.791028 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:05.817840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:35.817829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:54.809985 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.810027 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:05.817905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:35.817794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:54.828096 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.828130 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:05.818010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:35.817783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:54.846546 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.846594 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:05.818037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:35.818949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:54.866913 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.866976 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:05.817916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:35.817866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:54.886738 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.886783 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:05.817824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:35.817950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:54.905987 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.906085 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:05.817933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:35.817944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:54.926629 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.926667 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:05.817784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:35.818070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:54.950631 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.950688 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:05.817763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:35.820549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:54.969029 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.969081 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:05.817805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:35.817860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:54.989005 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.989218 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:05.817808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:35.818073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:55.008684 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:55.008758 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:05.817889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:35.817906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:55.029428 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:55.029469 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:05.817886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:35.817858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:55.047781 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:55.047822 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:05.817882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:35.817773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:55.066839 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:55.066877 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:39:05.819208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:39:35.817854 metrics.go:34: INFO No non-zero metrics in the last 30s