Results

          2022/03/28 03:21:02.155154 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:02.155660 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/28 03:21:02.156087 logstash.go:90: INFO Max Retries set to: 3
2022/03/28 03:21:02.156379 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/28 03:21:02.156665 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-fpnnv
2022/03/28 03:21:02.157094 async.go:63: INFO Flush Interval set to: 1s
2022/03/28 03:21:02.157370 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/28 03:21:02.158104 beat.go:221: INFO filebeat start running.
2022/03/28 03:21:02.158179 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/28 03:21:02.158551 metrics.go:23: INFO Metrics logging every 30s
2022/03/28 03:21:02.162744 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/28 03:21:02.162817 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/28 03:21:02.162904 crawler.go:38: INFO Loading Prospectors: 1
2022/03/28 03:21:02.163094 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/28 03:21:02.163127 registrar.go:236: INFO Starting Registrar
2022/03/28 03:21:02.163192 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/28 03:21:02.163205 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/28 03:21:02.163240 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/28 03:21:02.163350 sync.go:41: INFO Start sending events to output
2022/03/28 03:21:02.163825 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/28 03:21:32.159163 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:02.159042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:22:32.158888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:02.159010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:32.159078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:02.158878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:32.158925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:02.158830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:32.158851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:02.158910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:07.183846 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:26:32.159009 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:02.158868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:27:32.158960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:02.158982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:32.158947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:02.158865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:32.158815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:02.158988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:32.158901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:02.159007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:32.158871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:02.158807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:32.158844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:02.158872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:32.158852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:02.158991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:32.158921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:02.161108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:32.158800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:02.158820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:32.158914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:02.158914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:32.158879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:02.158863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:32.158941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:02.158798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:32.159063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:02.158844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:32.158972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:02.158866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:32.158815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:02.158849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:32.158803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:02.158843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:32.158852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:44:02.158832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:44:32.158827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:45:02.158868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:45:32.158892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:46:02.158883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:46:32.158928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:47:02.158828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:47:32.158849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:48:02.158931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:48:32.158903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:02.158840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:32.159588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:52.366205 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/28 03:49:57.364603 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.364756 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:58.368388 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:58.368436 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:00.373690 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:00.373760 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:02.158967 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:04.384017 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:04.384071 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:12.392994 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:12.393051 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:28.413859 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:28.413906 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:32.158836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:51:00.436056 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:00.436101 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:02.158893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:51:32.158833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:52:00.455069 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:00.455118 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:02.158871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:52:32.158880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:53:00.471483 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:00.471520 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:02.158900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:53:32.158912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:00.487589 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:00.487633 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:02.158818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:32.158919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:57.383378 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:55:00.505461 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:00.505511 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:02.158914 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:32.158819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:56:00.535060 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:00.535239 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:02.158864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:56:32.158844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:57:00.558071 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:00.558130 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:02.159216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:57:32.158997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:58:00.578550 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:00.578616 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:02.158961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:58:32.158823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:59:00.596223 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:00.596288 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:02.158839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:59:32.158823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:00:00.612990 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:00.613050 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:02.158829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:00:32.158830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:01:00.642088 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:00.642140 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:02.158854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:01:32.158839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:02:00.658062 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:00.658109 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:02.158918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:02:32.159082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:03:00.676535 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:00.676688 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:02.158897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:03:32.158986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:04:00.697291 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:00.697354 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:02.158845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:04:32.158876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:05:00.737508 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:00.737613 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:02.158831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:05:32.158909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:06:00.761590 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:06:00.761635 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:02.158799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:06:32.158928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:07:00.779609 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.779675 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:02.158894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:07:32.158903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:08:00.795893 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.795961 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:02.158875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:08:32.158889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:09:00.814372 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.814442 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:02.158823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:09:32.160309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:10:00.841486 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.841545 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:02.158828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:10:32.158836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:11:00.858258 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.858301 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:02.158949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:11:32.158814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:12:00.876697 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.876755 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:02.158878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:12:32.158918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:13:00.892888 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.892944 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:02.158861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:13:32.158935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:14:00.915523 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.915599 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:02.158880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:14:32.158835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:15:00.938505 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.938560 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:02.158944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:15:32.158873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:16:00.955558 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.955709 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:02.158881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:16:32.158925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:17:00.973630 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.973689 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:02.158877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:17:32.158838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:18:00.990379 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.990426 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:02.158971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:18:32.158953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:19:01.008767 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:01.008818 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:02.158825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:19:32.158869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:20:01.028942 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:01.028995 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:02.158825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:20:32.158823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:21:01.046647 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:01.046692 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:02.158820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:21:32.158827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:22:01.065896 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:01.065983 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:02.158970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:22:32.159016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:23:01.090507 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:01.090555 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:02.158845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:23:32.158841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:24:01.110394 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:01.110500 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:02.158854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:24:32.158925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:25:01.145435 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:01.145501 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:02.158935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:25:32.158886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:26:01.165251 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:01.165306 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:02.159298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:26:32.159581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:27:01.183530 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:01.183587 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:02.158949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:27:32.158901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:28:01.198932 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:01.198992 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:02.158981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:28:32.158817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:29:01.220778 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:01.220868 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:02.158926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:29:32.158780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:30:01.241414 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:01.241769 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:02.158883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:30:32.158994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:31:01.259382 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:01.259450 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:02.158940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:31:32.158914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:32:01.277376 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:01.277426 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:02.162265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:32:32.158892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:33:01.294875 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:01.294925 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:02.158859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:33:32.158835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:34:01.314906 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:01.314942 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:02.158864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:34:32.165499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:35:01.332802 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:01.332845 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:02.158873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:35:32.158898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:36:01.348611 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:01.348654 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:02.159175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:36:32.158941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:37:01.365294 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:01.365695 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:02.158861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:37:32.159007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:38:01.383644 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:01.383743 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:02.158902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:38:32.158867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:39:01.403283 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:01.403363 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:02.158843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:39:32.158826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:40:01.442164 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:01.442244 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:02.158868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:40:32.159189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:41:01.459673 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:01.459749 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:02.160042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:41:32.158848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:42:01.478338 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:01.478415 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:02.158938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:42:32.158977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:43:01.495365 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:01.495427 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:02.158950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:43:32.159045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:44:01.535959 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:01.536033 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:02.158940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:44:32.158912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:45:01.561491 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:01.561548 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:02.158896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:45:32.158993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:46:01.579503 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:01.579556 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:02.158866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:46:32.158888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:47:01.601150 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:01.601220 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:02.158960 metrics.go:34: INFO No non-zero metrics in the last 30s