By type
2022/03/09 03:19:40.861502 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/09 03:19:40.861588 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 03:19:40.861848 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 03:19:40.862049 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 03:19:40.862256 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-hwh7m
2022/03/09 03:19:40.862574 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 03:19:40.862603 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 03:19:40.863458 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 03:19:40.863826 beat.go:221: INFO filebeat start running.
2022/03/09 03:19:40.863958 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 03:19:40.867707 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 03:19:40.867786 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 03:19:40.867831 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 03:19:40.868006 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 03:19:40.868102 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/09 03:19:40.868116 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 03:19:40.868126 registrar.go:236: INFO Starting Registrar
2022/03/09 03:19:40.868174 sync.go:41: INFO Start sending events to output
2022/03/09 03:19:40.868205 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 03:19:40.868938 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/09 03:20:10.864023 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/09 03:20:40.863870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:21:10.863830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:21:40.871928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:22:10.863951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:22:40.863981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:23:10.865348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:23:40.863815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:10.863839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:40.863838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:45.880663 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:25:10.863914 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/09 03:25:40.863780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:26:10.863797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:26:40.863809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:27:10.864055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:27:40.863782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:28:10.863775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:28:40.863810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:29:10.863853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:29:40.863810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:30:10.863791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:30:40.863921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:31:10.863819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:31:40.863925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:32:10.863965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:32:40.863820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:33:10.863808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:33:40.863862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:34:10.863762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:34:40.863780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:35:10.863965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:35:40.863888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:36:10.863911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:36:40.863840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:37:10.863779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:37:40.863742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:38:10.863774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:38:40.863759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:39:10.863738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:39:40.863806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:40:10.863875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:40:40.863770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:41:10.863715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:41:40.863878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:42:10.863928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:42:40.863759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:43:10.863771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:43:40.863795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:44:10.863812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:44:40.863830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:45:10.863987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:45:40.863877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:46:10.863752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:46:40.863738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:47:10.863704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:47:40.863767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:48:10.863802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:48:40.863775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:49:10.863920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:49:40.863816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:50:10.863805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:50:31.060364 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/09 03:50:35.995811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:35.995953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:37.002607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:37.002683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:39.006977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:39.007109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:40.863842 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/09 03:50:43.016158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:43.016194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:51.024148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:51.024180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:51:07.041985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:51:07.042150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:51:10.863782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:51:39.060329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:51:39.060366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:51:40.863765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:52:10.863761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:52:39.079386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:52:39.079425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:52:40.863814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:53:10.863797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:53:39.097396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:53:39.097435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:53:40.863754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:54:10.863902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:54:39.115119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:54:39.115157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:54:40.863885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:55:10.863782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:55:36.076213 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:55:39.135225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:55:39.135279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:55:40.863841 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/09 03:56:10.863814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:56:39.154949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:56:39.154989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:56:40.863766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:57:10.863739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:57:39.172623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:57:39.172771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:57:40.863811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:58:10.863969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:58:39.192221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:58:39.192269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:58:40.863780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:59:10.863822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:59:39.209781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:59:39.209819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:59:40.863803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:00:10.863789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:00:39.226393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:00:39.226433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:00:40.863810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:01:10.863744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:01:39.244369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:01:39.244427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:01:40.863758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:02:10.863843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:02:39.262942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:02:39.262991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:02:40.863973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:03:10.863830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:03:39.279637 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:03:39.279821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:03:40.863778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:04:10.863762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:04:39.297553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:04:39.297608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:04:40.863785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:05:10.863765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:05:39.315172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:05:39.315213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:05:40.864097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:06:10.864661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:06:39.336316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:06:39.336537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:06:40.863963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:07:10.863817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:07:39.355142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:07:39.355197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:07:40.863817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:08:10.863848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:08:39.372831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:08:39.372914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:08:40.863812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:09:10.863792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:09:39.389055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:09:39.389092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:09:40.863734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:10:10.863771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:10:39.407326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:10:39.407388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:10:40.863868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:11:10.863794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:11:39.427389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:11:39.427450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:11:40.864026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:12:10.863875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:12:39.445101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:12:39.445141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:12:40.863728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:13:10.863794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:13:39.462384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:13:39.462427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:13:40.863884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:14:10.863933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:14:39.481194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:14:39.481272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:14:40.863820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:15:10.863877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:15:39.499154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:15:39.499363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:15:40.863948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:16:10.864461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:16:39.516984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:16:39.517041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:16:40.864302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:17:10.864107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:17:39.534322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:17:39.534358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:17:40.863852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:18:10.863844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:18:39.551965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:18:39.552002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:18:40.863871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:19:10.863802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:19:39.572227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:19:39.572261 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:19:40.864022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:20:10.863819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:20:39.589660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:20:39.589698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:20:40.864401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:21:10.863749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:21:39.607577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:21:39.607619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:21:40.863843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:22:10.863834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:22:39.625288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:22:39.625365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:22:40.863822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:23:10.863809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:23:39.642171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:23:39.642209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:23:40.863767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:24:10.863802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:24:39.660506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:24:39.660560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:24:40.863805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:25:10.863757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:25:39.678645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:25:39.678707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:25:40.863819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:26:10.863806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:26:39.694614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:26:39.694683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:26:40.863778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:27:10.863949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:27:39.713155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:27:39.713203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:27:40.863878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:28:10.863927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:28:39.730553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:28:39.730756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:28:40.863732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:29:10.863757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:29:39.746974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:29:39.747024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:29:40.863745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:30:10.863785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:30:39.763557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:30:39.763620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:30:40.863741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:31:10.863811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:31:39.781404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:31:39.781459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:31:40.863807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:32:10.863776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:32:39.798774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:32:39.798869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:32:40.863749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:33:10.863789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:33:39.816281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:33:39.816352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:33:40.863764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:34:10.863835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:34:39.833036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:34:39.833068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:34:40.863898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:35:10.863777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:35:39.848772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:35:39.848810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:35:40.863791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:36:10.863788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:36:39.864116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:36:39.864165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:36:40.863711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:37:10.863775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:37:39.880281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:37:39.880468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:37:40.863971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:38:10.863848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:38:39.897760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:38:39.897798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:38:40.863734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:39:10.863785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:39:39.914176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:39:39.914238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:39:40.863799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:40:10.863827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:40:39.931426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:40:39.931465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:40:40.863838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:41:10.863836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:41:39.950183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:41:39.950221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:41:40.863815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:42:10.863765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:42:39.967329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:42:39.967383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:42:40.863940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:43:10.863776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:43:39.986486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:43:39.986532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:43:40.867062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:44:10.863808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:44:40.004048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:44:40.004080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:44:40.863768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:45:10.863762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:45:40.021874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:45:40.021919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:45:40.863775 metrics.go:34: INFO No non-zero metrics in the last 30s