Results

          2022/04/13 03:31:54.051216 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/04/13 03:31:54.051352 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/13 03:31:54.051378 metrics.go:23: INFO Metrics logging every 30s
2022/04/13 03:31:54.051719 logstash.go:90: INFO Max Retries set to: 3
2022/04/13 03:31:54.051862 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/13 03:31:54.052111 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-nn24n
2022/04/13 03:31:54.052481 async.go:63: INFO Flush Interval set to: 1s
2022/04/13 03:31:54.052510 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/13 03:31:54.053419 beat.go:221: INFO filebeat start running.
2022/04/13 03:31:54.053576 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/13 03:31:54.069774 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/13 03:31:54.069944 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/13 03:31:54.070017 crawler.go:38: INFO Loading Prospectors: 1
2022/04/13 03:31:54.070113 registrar.go:236: INFO Starting Registrar
2022/04/13 03:31:54.070146 sync.go:41: INFO Start sending events to output
2022/04/13 03:31:54.070348 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/13 03:31:54.070379 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/13 03:31:54.070543 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/13 03:31:54.070604 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/13 03:31:54.072553 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/13 03:31:54.072748 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/13 03:31:54.072874 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/13 03:31:54.073000 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/13 03:31:54.073201 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/13 03:31:59.145926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:31:59.146051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:00.175410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:00.175452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:02.190815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:02.190875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:06.252303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:06.252397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:14.272300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:14.272385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:24.052033 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=64 registrar.writes=1
2022/04/13 03:32:30.301850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:30.301956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:54.055811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:33:02.344988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:33:02.345059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:33:24.052050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:33:54.052095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:34:02.380747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:34:02.381127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:34:24.051817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:34:54.052170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:35:02.404388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:35:02.404461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:35:24.051807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:35:54.052141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:36:02.432698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:36:02.432772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:36:24.051921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:36:54.051911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:36:59.120076 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:36:59.120116 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:36:59.120267 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:36:59.120089 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:37:02.487669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:37:02.487759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:37:19.121491 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:37:24.051930 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/04/13 03:37:54.051760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:38:02.510778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:38:02.510846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:38:24.051868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:38:54.051847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:39:02.539651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:39:02.539722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:39:24.052260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:39:54.051854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:40:02.561249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:40:02.561335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:40:24.051979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:40:54.051846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:41:02.623457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:41:02.624449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:41:24.051896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:41:54.051760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:42:02.679932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:42:02.679996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:42:24.051816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:42:54.051913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:43:02.720157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:43:02.720214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:43:24.052009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:43:54.052158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:44:02.775109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:44:02.775176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:44:24.052444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:44:54.051947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:45:02.806029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:45:02.806091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:45:24.051865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:45:54.051878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:46:02.856738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:46:02.856804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:46:24.051852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:46:54.052041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:47:02.888560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:47:02.888639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:47:24.051971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:47:54.052004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:48:02.912585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:48:02.912645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:48:24.052147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:48:54.051923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:49:02.990087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:49:02.990150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:49:24.051847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:49:54.051984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:50:03.051084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:50:03.051153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:50:24.051933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:50:54.051789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:51:03.079277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:51:03.079344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:51:24.051866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:51:54.052879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:52:03.108397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:52:03.108458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:52:24.051767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:52:54.051821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:53:03.151806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:53:03.151867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:53:24.052025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:53:54.051776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:54:03.185448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:54:03.185510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:54:24.051813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:54:54.051741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:55:03.212111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:55:03.213099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:55:24.051932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:55:54.051894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:56:03.268952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:56:03.269027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:56:24.051745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:56:54.051861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:57:03.293667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:57:03.293730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:57:24.051924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:57:54.051924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:58:03.329720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:58:03.329780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:58:24.055930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:58:54.051798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:59:03.367310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:59:03.367390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:59:24.051867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:59:54.051854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:00:03.401397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:00:03.401456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:00:24.051901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:00:54.051919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:01:03.424218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:01:03.424286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:01:24.051780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:01:54.051780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:02:03.484056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:02:03.484110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:02:24.051967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:02:54.052130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:03:03.509284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:03:03.509483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:03:24.051856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:03:54.051862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:04:03.545889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:04:03.545944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:04:24.051953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:04:54.052240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:05:03.580516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:05:03.580878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:05:24.052150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:05:54.052685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:06:03.605681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:06:03.605741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:06:24.055326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:06:54.053403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:07:03.644777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:07:03.644843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:07:24.051915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:07:54.051830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:08:03.684732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:08:03.684793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:08:24.052132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:08:54.051762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:09:03.707564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:09:03.707625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:09:24.051807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:09:54.051812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:10:03.753032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:10:03.753078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:10:24.051946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:10:54.053506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:11:03.786245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:11:03.786326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:11:24.051953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:11:54.051839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:12:03.816364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:12:03.816425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:12:24.052071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:12:54.052083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:13:03.861965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:13:03.862121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:13:24.051871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:13:54.052116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:14:03.890556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:14:03.890625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:14:24.052031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:14:54.051799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:15:03.916130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:15:03.916196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:15:24.052379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:15:54.051928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:16:03.959894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:16:03.959958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:16:24.052042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:16:54.051845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:17:03.989439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:17:03.989969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:17:24.051849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:17:54.052560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:18:04.012497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:18:04.012573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:18:24.051943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:18:54.052301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:19:04.060793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:19:04.060846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:19:24.051831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:19:54.052067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:20:04.093934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:20:04.094007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:20:24.051791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:20:54.051781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:21:04.116955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:21:04.117012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:21:24.051791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:21:54.051896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:22:04.158291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:22:04.158495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:22:24.052034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:22:54.051926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:23:04.195645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:23:04.195711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host