Results

          2022/03/31 03:06:34.310470 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/31 03:06:34.310538 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/31 03:06:34.310677 metrics.go:23: INFO Metrics logging every 30s
2022/03/31 03:06:34.310755 logstash.go:90: INFO Max Retries set to: 3
2022/03/31 03:06:34.310878 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/31 03:06:34.311038 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-s9nmd
2022/03/31 03:06:34.311324 async.go:63: INFO Flush Interval set to: 1s
2022/03/31 03:06:34.311353 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/31 03:06:34.311819 beat.go:221: INFO filebeat start running.
2022/03/31 03:06:34.311903 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/31 03:06:34.318172 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/31 03:06:34.318260 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/31 03:06:34.318302 crawler.go:38: INFO Loading Prospectors: 1
2022/03/31 03:06:34.318479 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/31 03:06:34.318570 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/31 03:06:34.318604 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/31 03:06:34.318617 registrar.go:236: INFO Starting Registrar
2022/03/31 03:06:34.318693 sync.go:41: INFO Start sending events to output
2022/03/31 03:06:34.318736 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/31 03:06:54.321263 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/31 03:06:54.321746 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/31 03:06:54.322024 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/31 03:06:54.322186 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/31 03:06:54.322478 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/31 03:06:59.342989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:06:59.343032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:00.354280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:00.354354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:02.361990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:02.362034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:04.311109 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=200 registrar.writes=1
2022/03/31 03:07:06.369312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:06.369344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:14.375946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:14.375979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:30.399630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:30.399667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:07:34.311069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:08:02.416522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:08:02.416558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:08:04.311028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:08:34.311060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:09:02.434157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:09:02.434214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:09:04.311273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:09:34.311198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:10:02.451394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:10:02.451662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:10:04.311152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:10:34.310991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:11:02.476191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:11:02.476243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:11:04.311075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:11:34.310993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:11:59.330631 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/31 03:11:59.330658 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/31 03:11:59.330807 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/31 03:11:59.330897 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/31 03:12:02.495241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:12:02.495277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:12:04.311066 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/31 03:12:05.349952 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/31 03:12:34.311045 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/31 03:13:02.513899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:13:02.513952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:13:04.310970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:13:34.310992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:14:02.535659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:14:02.535703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:14:04.311132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:14:34.310979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:15:02.553856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:15:02.553906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:15:04.311091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:15:34.311057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:16:02.577172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:16:02.577315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:16:04.310984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:16:34.310949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:17:02.596444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:17:02.596481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:17:04.310972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:17:34.310986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:18:02.622529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:18:02.622607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:18:04.311188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:18:34.310974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:19:02.639804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:19:02.639841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:19:04.311009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:19:34.311062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:20:02.661458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:20:02.661520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:20:04.311003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:20:34.311007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:21:02.681016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:21:02.681072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:21:04.311053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:21:34.311013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:22:02.698885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:22:02.698930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:22:04.311010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:22:34.312991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:23:02.718019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:23:02.718066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:23:04.311070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:23:34.311063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:24:02.738119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:24:02.738158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:24:04.310976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:24:34.310993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:25:02.756151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:25:02.756197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:25:04.311030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:25:34.310963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:26:02.784008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:26:02.784050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:26:04.311102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:26:34.311225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:27:02.803094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:27:02.803144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:27:04.311038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:27:34.311013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:28:02.821815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:28:02.821850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:28:04.310977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:28:34.311059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:29:02.840020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:29:02.840051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:29:04.310964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:29:34.311005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:30:02.857035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:30:02.857082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:30:04.311033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:30:34.310957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:31:02.881715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:31:02.881752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:31:04.311026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:31:34.311001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:32:02.899746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:32:02.899783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:32:04.311050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:32:34.310994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:33:02.916537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:33:02.916600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:33:04.310968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:33:34.311105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:34:02.935023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:34:02.935090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:34:04.311087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:34:34.310992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:35:02.952354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:35:02.952388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:35:04.311030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:35:34.310974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:36:02.973175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:36:02.973328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:36:04.310990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:36:34.311049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:37:02.991706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:37:02.991751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:37:04.311038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:37:34.310951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:38:03.009597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:38:03.009641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:38:04.310973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:38:34.310948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:39:03.029053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:39:03.029087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:39:04.311117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:39:34.311192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:40:03.047113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:40:03.047148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:40:04.312928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:40:34.312366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:41:03.065448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:41:03.065488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:41:04.310972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:41:34.311056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:42:03.082378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:42:03.082405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:42:04.311055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:42:34.310973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:43:03.103155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:43:03.103193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:43:04.311024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:43:34.313218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:44:03.122006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:44:03.122049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:44:04.311035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:44:34.310984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:45:03.145062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:45:03.145092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:45:04.310946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:45:34.310971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/31 03:46:03.165166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:46:03.165214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/31 03:46:04.310986 metrics.go:34: INFO No non-zero metrics in the last 30s