Results

          2022/03/28 03:21:12.766172 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:12.766244 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/28 03:21:12.766348 metrics.go:23: INFO Metrics logging every 30s
2022/03/28 03:21:12.766389 logstash.go:90: INFO Max Retries set to: 3
2022/03/28 03:21:12.766585 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/28 03:21:12.766845 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-xctfr
2022/03/28 03:21:12.767121 async.go:63: INFO Flush Interval set to: 1s
2022/03/28 03:21:12.767153 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/28 03:21:12.767776 beat.go:221: INFO filebeat start running.
2022/03/28 03:21:12.767892 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/28 03:21:12.772646 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/28 03:21:12.772718 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/28 03:21:12.772822 registrar.go:236: INFO Starting Registrar
2022/03/28 03:21:12.772845 crawler.go:38: INFO Loading Prospectors: 1
2022/03/28 03:21:12.772912 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/28 03:21:12.772911 sync.go:41: INFO Start sending events to output
2022/03/28 03:21:12.773087 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/28 03:21:12.773181 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/28 03:21:12.773207 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/28 03:21:12.773892 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/28 03:21:42.767058 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:12.766707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:22:42.766703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:12.766756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:42.766862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:12.766896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:42.766892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:12.766820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:42.766722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:12.766766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:17.784954 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:26:42.768872 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:12.766768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:27:42.766767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:12.766695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:42.766731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:12.766736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:42.766751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:12.766627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:42.766788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:12.766721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:42.766738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:12.766651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:42.766700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:12.766858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:42.766834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:12.766786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:42.766726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:12.766802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:42.766777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:12.766678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:42.766811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:12.766786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:42.766667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:12.766733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:42.766707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:12.766687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:42.766744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:12.766685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:42.766664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:12.766696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:42.766699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:12.766700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:42.766844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:12.766636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:42.766828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:44:12.766759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:44:42.766700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:45:12.766762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:45:42.766622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:46:12.766637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:46:42.766620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:47:12.766732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:47:42.766724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:48:12.767530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:48:42.766794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:12.766718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:42.766726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:49:52.958744 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/28 03:49:57.884785 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.884830 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.888961 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.889010 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.894019 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.894050 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:04.900587 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.900635 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.766622 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:12.920004 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.920041 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.926298 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.926393 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:42.766767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:51:00.945789 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.945838 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:12.766717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:51:42.766673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:52:00.955062 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.955096 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:12.766732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:52:42.766627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:53:00.961709 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.961746 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:12.766673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:53:42.766686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:00.968982 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.969046 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:12.766773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:42.766719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:54:57.969858 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:55:00.976123 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.976173 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:12.766758 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:42.766722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:56:00.985196 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.985317 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:12.766751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:56:42.766684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:57:00.992379 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.992414 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:12.766734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:57:42.766639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:58:00.999263 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.999351 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:12.766747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:58:42.766814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:59:01.005938 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:01.005984 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:12.766698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:59:42.766712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:00:01.012254 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:01.012291 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:12.766736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:00:42.766648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:01:01.020776 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:01.020824 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:12.766707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:01:42.766670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:02:01.029001 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:01.029080 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:12.766850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:02:42.766729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:03:01.035141 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:01.035172 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:12.766696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:03:42.766668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:04:01.047567 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:01.047604 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:12.766636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:04:42.766657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:05:01.055795 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:01.055835 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:12.766756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:05:42.766636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:06:01.062312 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:01.062360 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:12.766641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:06:42.766631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:07:01.068961 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:01.069004 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:12.766616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:07:42.766622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:08:01.075752 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:01.075799 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:12.766663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:08:42.766731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:09:01.083755 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:01.083811 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:12.766930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:09:42.766704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:10:01.091721 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:01.091770 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:12.766734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:10:42.766701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:11:01.098154 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:01.098186 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:12.766661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:11:42.766667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:12:01.105366 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:01.105404 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:12.766696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:12:42.766716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:13:01.112610 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:01.112649 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:12.766706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:13:42.766677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:14:01.122546 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:01.122591 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:12.766974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:14:42.767969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:15:01.129960 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:01.130025 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:12.766680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:15:42.766719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:16:01.137302 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:01.137371 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:12.766622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:16:42.766840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:17:01.143821 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:01.143854 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:12.766733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:17:42.766782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:18:01.151903 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:01.151994 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:12.766688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:18:42.766665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:19:01.162205 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.162238 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:12.766693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:19:42.766696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:20:01.173650 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.173691 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:12.766800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:20:42.766669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:21:01.180308 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.180349 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:12.766696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:21:42.766763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:22:01.189485 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.189531 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:12.766700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:22:42.766666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:23:01.196748 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.196804 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:12.766688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:23:42.766727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:24:01.203165 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.203418 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:12.766701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:24:42.766645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:25:01.210345 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.210378 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:12.766624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:25:42.766724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:26:01.217651 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.217709 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:12.766626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:26:42.766653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:27:01.225770 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.225817 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:12.766625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:27:42.766625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:28:01.233904 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.233950 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:12.769760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:28:42.766711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:29:01.240888 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.240955 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:12.766708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:29:42.766764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:30:01.248616 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.248656 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:12.766770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:30:42.766642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:31:01.254734 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.254776 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:12.766683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:31:42.766662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:32:01.262795 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.262845 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:12.766697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:32:42.766751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:33:01.269770 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.269806 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:12.766650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:33:42.766722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:34:01.277128 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.277167 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:12.766853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:34:42.766806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:35:01.284421 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.284458 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:12.766697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:35:42.766811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:36:01.292356 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.292549 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:12.766605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:36:42.766602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:37:01.305702 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.305739 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:12.766703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:37:42.766751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:38:01.313433 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.313527 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:12.766896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:38:42.766751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:39:01.320666 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.320736 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:12.766671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:39:42.766787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:40:01.329850 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.329888 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:12.766652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:40:42.766760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:41:01.342785 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.342835 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:12.766783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:41:42.766692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:42:01.349701 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.349745 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:12.766674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:42:42.766664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:43:01.356928 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.357078 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:12.766769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:43:42.766855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:44:01.365501 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.365593 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:12.766654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:44:42.766688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:45:01.372979 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.373015 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:12.766820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:45:42.766986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:46:01.383972 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.384029 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:12.766785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:46:42.766770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 04:47:01.391705 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.391740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host