By type
2022/03/28 03:21:01.503098 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/28 03:21:01.503190 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/28 03:21:01.503336 metrics.go:23: INFO Metrics logging every 30s
2022/03/28 03:21:01.503347 logstash.go:90: INFO Max Retries set to: 3
2022/03/28 03:21:01.503539 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/28 03:21:01.503683 publish.go:295: INFO Publisher name: onap-vfc-vnflcm-84bd7747bf-fwxpq
2022/03/28 03:21:01.503934 async.go:63: INFO Flush Interval set to: 1s
2022/03/28 03:21:01.503954 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/28 03:21:01.504480 beat.go:221: INFO filebeat start running.
2022/03/28 03:21:01.504664 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/28 03:21:01.508091 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/28 03:21:01.508202 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/28 03:21:01.508292 crawler.go:38: INFO Loading Prospectors: 1
2022/03/28 03:21:01.508405 registrar.go:236: INFO Starting Registrar
2022/03/28 03:21:01.508509 sync.go:41: INFO Start sending events to output
2022/03/28 03:21:01.508598 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/28 03:21:01.508837 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/28 03:21:01.508966 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/28 03:21:01.509045 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/28 03:21:01.509691 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/28 03:21:31.503803 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/28 03:22:01.503769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:22:31.503838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:01.503740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:31.503841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:01.503834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:31.503801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:01.503745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:31.503820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:01.503760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:06.521759 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:26:31.503907 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/28 03:27:01.503744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:27:31.503818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:01.503764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:31.503976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:01.503968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:31.503708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:01.503748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:31.503744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:01.503765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:31.503855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:01.503814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:31.503734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:01.503691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:31.503753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:01.503736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:31.503849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:01.503838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:31.503802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:01.503880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:31.503927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:01.504124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:31.503911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:01.503715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:31.503859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:01.503743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:31.503827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:01.503762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:31.503798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:01.503677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:31.503758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:01.503819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:31.503756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:01.503699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:31.503913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:44:01.503663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:44:31.503786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:45:01.503678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:45:31.503893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:46:01.503814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:46:31.503786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:47:01.503994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:47:31.503709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:48:01.503692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:48:31.503713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:01.503707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:31.503766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:51.698916 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/28 03:49:56.647076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:49:56.647126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:49:57.651125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:49:57.651171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:49:59.655000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:49:59.655059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:01.504833 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/28 03:50:03.663225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:03.663368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:11.672411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:11.672520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:27.691214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:27.691267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:31.503739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:50:59.709158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:50:59.709202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:51:01.503708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:51:31.503733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:51:59.726022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:51:59.726066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:52:01.503759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:52:31.503994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:52:59.742796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:52:59.742931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:53:01.503683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:53:31.503664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:53:59.760407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:53:59.760500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:54:01.503679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:31.503639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:56.711177 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:54:59.777934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:54:59.777988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:55:01.503796 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/28 03:55:31.506923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:55:59.796655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:55:59.796708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:56:01.503698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:56:31.503753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:56:59.818336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:56:59.818435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:57:01.503750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:57:31.503806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:57:59.837126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:57:59.837169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:58:01.503758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:58:31.503801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:58:59.854551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:58:59.854595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:59:01.503760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:59:31.503738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:59:59.875016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:59:59.875065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:00:01.503712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:00:31.503729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:00:59.893680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:00:59.893741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:01:01.503703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:01:31.503858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:01:59.911522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:01:59.911576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:02:01.503773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:02:31.503730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:02:59.928705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:02:59.928745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:03:01.503763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:03:31.503758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:03:59.945829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:03:59.945878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:04:01.503651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:04:31.503690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:04:59.966410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:04:59.966468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:05:01.503855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:05:31.503770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:05:59.984554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:05:59.984599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:06:01.503709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:06:31.503793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:07:00.003871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:07:00.003917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:07:01.503740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:07:31.503769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:08:00.022071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:08:00.022110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:08:01.503672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:08:31.503621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:09:00.039769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:09:00.039814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:09:01.503666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:09:31.503673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:10:00.057283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:10:00.057476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:10:01.503724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:10:31.503714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:11:00.076687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:11:00.076725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:11:01.503623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:11:31.503769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:12:00.094836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:12:00.094885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:12:01.503706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:12:31.503737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:13:00.117815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:13:00.117855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:13:01.503802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:13:31.503725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:14:00.137865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:14:00.137911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:14:01.503777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:14:31.503644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:15:00.155978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:15:00.156039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:15:01.503673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:15:31.503743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:16:00.175874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:16:00.175923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:16:01.503733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:16:31.503775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:17:00.195763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:17:00.195806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:17:01.503927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:17:31.503721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:18:00.214740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:18:00.214785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:18:01.503655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:18:31.503695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:19:00.232816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:19:00.232855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:19:01.503732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:19:31.503850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:20:00.249501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:20:00.249560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:20:01.503742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:20:31.503649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:21:00.266261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:21:00.266306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:21:01.503689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:21:31.503691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:22:00.284572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:22:00.284636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:22:01.503661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:22:31.503811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:23:00.302686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:23:00.302736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:23:01.503787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:23:31.503747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:24:00.320394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:24:00.320474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:24:01.503670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:24:31.503657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:25:00.337325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:25:00.337383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:25:01.503887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:25:31.504021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:26:00.355379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:26:00.355443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:26:01.503783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:26:31.503837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:27:00.372406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:27:00.372483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:27:01.503830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:27:31.503778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:28:00.390244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:28:00.390282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:28:01.503739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:28:31.503761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:29:00.407530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:29:00.407566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:29:01.503743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:29:31.503792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:30:00.425271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:30:00.425315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:30:01.503706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:30:31.503780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:31:00.443814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:31:00.443865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:31:01.503703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:31:31.503728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:32:00.462662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:32:00.462708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:32:01.503738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:32:31.503733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:33:00.479526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:33:00.479660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:33:01.503722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:33:31.503783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:34:00.497122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:34:00.497187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:34:01.503747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:34:31.503682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:35:00.515867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:35:00.515925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:35:01.503733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:35:31.503716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:36:00.536092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:36:00.536229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:36:01.503671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:36:31.503883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:37:00.554088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:37:00.554192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:37:01.503771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:37:31.503807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:38:00.581478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:38:00.581532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:38:01.503684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:38:31.503694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:39:00.600245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:39:00.600298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:39:01.503734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:39:31.503670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:40:00.620768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:40:00.620819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:40:01.503658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:40:31.503748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:41:00.647428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:41:00.647477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:41:01.503671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:41:31.503619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:42:00.666216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:42:00.666284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:42:01.503709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:42:31.503725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:43:00.683079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:43:00.683136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:43:01.503695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:43:31.503738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:44:00.700845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:44:00.700891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:44:01.503733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:44:31.503718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:45:00.717506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:45:00.717702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:45:01.503635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:45:31.503729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:46:00.737784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:46:00.737848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:46:01.503704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:46:31.503769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:47:00.754299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:47:00.754350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 04:47:01.503967 metrics.go:34: INFO No non-zero metrics in the last 30s