By type
2022/03/11 03:18:35.223911 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/11 03:18:35.223961 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/11 03:18:35.224026 logstash.go:90: INFO Max Retries set to: 3
2022/03/11 03:18:35.224104 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/11 03:18:35.224336 publish.go:295: INFO Publisher name: onap-vfc-vnfmgr-8594ffd488-bnhbz
2022/03/11 03:18:35.224370 metrics.go:23: INFO Metrics logging every 30s
2022/03/11 03:18:35.224613 async.go:63: INFO Flush Interval set to: 1s
2022/03/11 03:18:35.224643 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/11 03:18:35.225202 beat.go:221: INFO filebeat start running.
2022/03/11 03:18:35.225352 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/11 03:18:35.230203 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/11 03:18:35.230279 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/11 03:18:35.230504 registrar.go:236: INFO Starting Registrar
2022/03/11 03:18:35.230552 crawler.go:38: INFO Loading Prospectors: 1
2022/03/11 03:18:35.230577 sync.go:41: INFO Start sending events to output
2022/03/11 03:18:35.230700 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/11 03:18:35.230731 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/11 03:18:35.230857 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/11 03:18:35.230915 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/11 03:18:35.231605 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/11 03:19:05.225023 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/11 03:19:35.224888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:05.224780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:35.224948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:05.224924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:35.224950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:05.224813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:35.225019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:05.224944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:35.224842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:40.242405 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/11 03:24:05.224945 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/11 03:24:35.224811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:05.224880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:35.225206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:05.224815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:35.224862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:05.224826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:35.224804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:05.224758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:35.224957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:05.224905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:35.224804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:05.224980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:35.224909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:05.224873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:35.224864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:05.224878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:35.224939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:05.224768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:35.224775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:05.224793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:35.226033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:05.224920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:35.224946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:05.224826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:35.224787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:05.224918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:35.224814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:05.224711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:35.224729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:05.224936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:35.224902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:05.224824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:35.224835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:05.224803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:35.224770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:05.224764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:35.224781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:05.224973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:35.224781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:05.224802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:35.224788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:05.224870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:35.224807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:05.224808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:35.224855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:05.224903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:35.224897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:55.446079 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/11 03:48:00.344925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:00.344965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:01.349458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:01.349501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:03.353861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:03.353898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:05.224898 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/11 03:48:07.361398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:07.361498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:15.367379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:15.367546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:31.388827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:31.388904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:35.224851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:03.405295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:03.405336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:05.224839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:35.224856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:03.431690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:03.431730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:05.224821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:35.224853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:03.450159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:03.450219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:05.224829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:35.224796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:03.468543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:03.468582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:05.224711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:35.224857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:00.456638 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/11 03:53:03.488868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:03.488926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:05.224929 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/11 03:53:35.224980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:03.506932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:03.507016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:05.224771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:35.224820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:03.526519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:03.526566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:05.224883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:35.224796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:03.545511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:03.545564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:05.224807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:35.224793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:03.563088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:03.563136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:05.224935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:35.224863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:03.582472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:03.582656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:05.224937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:35.225367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:03.600660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:03.600712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:05.224733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:35.224719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:03.619219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:03.619266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:05.224792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:35.224833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:03.637574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:03.637619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:05.224932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:35.224763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:03.656925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:03.656982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:05.224780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:35.224812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:03.673504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:03.673639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:05.224804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:35.224799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:03.695400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:03.695454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:05.224857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:35.224806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:03.714778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:03.714832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:05.224968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:35.225196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:03.734197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:03.734242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:05.224822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:35.224958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:03.754786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:03.754829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:05.224853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:35.224821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:03.771131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:03.771170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:05.224972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:35.224732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:03.801227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:03.801315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:05.224800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:35.224838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:03.821683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:03.821727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:05.224825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:35.224863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:03.848872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:03.848943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:05.224867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:35.224786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:03.866787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:03.866952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:05.224911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:35.224787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:03.886086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:03.886227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:05.224798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:35.224814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:03.905011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:03.905059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:05.224902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:35.225142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:03.923177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:03.923246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:05.224819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:35.224798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:03.942954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:03.943237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:05.224870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:35.224788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:03.963115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:03.963177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:05.224801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:35.224819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:03.982974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:03.983015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:05.224902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:35.224832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:04.003517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:04.003561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:05.224767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:35.224844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:04.021001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:04.021050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:05.225002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:35.224754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:04.038486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:04.038699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:05.224786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:35.224828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:04.057575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:04.057616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:05.224727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:35.224843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:04.076185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:04.076390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:05.224909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:35.224909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:04.096908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:04.097215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:05.224801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:35.224816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:04.119098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:04.119140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:05.225056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:35.225043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:04.135499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:04.135549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:05.224916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:35.224817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:04.155081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:04.155165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:05.224894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:35.224804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:04.175670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:04.175820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:05.224790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:35.224862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:04.195287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:04.195330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:05.224841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:35.224773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:04.215191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:04.215243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:05.224867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:35.224809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:04.238882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:04.238940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:05.224953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:35.225061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:04.263422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:04.263495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:05.224893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:35.224972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:33:04.286493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:33:04.286552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:33:05.224775 metrics.go:34: INFO No non-zero metrics in the last 30s