By type
2022/04/25 03:09:09.312677 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/25 03:09:09.312733 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/25 03:09:09.312799 metrics.go:23: INFO Metrics logging every 30s
2022/04/25 03:09:09.312912 logstash.go:90: INFO Max Retries set to: 3
2022/04/25 03:09:09.313035 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/25 03:09:09.313335 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-6gg6t
2022/04/25 03:09:09.313612 async.go:63: INFO Flush Interval set to: 1s
2022/04/25 03:09:09.313629 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/25 03:09:09.314127 beat.go:221: INFO filebeat start running.
2022/04/25 03:09:09.314271 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/25 03:09:09.327603 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/25 03:09:09.327708 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/25 03:09:09.327767 crawler.go:38: INFO Loading Prospectors: 1
2022/04/25 03:09:09.328125 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/25 03:09:09.328305 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/25 03:09:09.328375 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/25 03:09:09.328403 registrar.go:236: INFO Starting Registrar
2022/04/25 03:09:09.328512 sync.go:41: INFO Start sending events to output
2022/04/25 03:09:09.328580 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/25 03:09:29.330832 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/25 03:09:29.332247 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/25 03:09:29.332751 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/25 03:09:29.333086 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/25 03:09:29.333433 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/25 03:09:34.350169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:34.350269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:35.354921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:35.354956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:37.359761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:37.359822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:39.313303 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/04/25 03:09:41.366273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:41.366306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:49.373058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:09:49.373098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:10:05.390834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:10:05.390881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:10:09.313141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:10:37.409951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:10:37.410001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:10:39.313225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:11:09.313233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:11:37.431399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:11:37.431437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:11:39.313171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:12:09.313167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:12:37.449332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:12:37.449375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:12:39.313160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:13:09.313170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:13:37.470371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:13:37.470419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:13:39.313158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:14:09.313038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:14:34.358843 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/25 03:14:34.359004 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/25 03:14:34.359041 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/25 03:14:34.359073 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/25 03:14:37.488886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:14:37.488927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:14:39.313143 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/04/25 03:14:40.367523 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/25 03:15:09.313230 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/04/25 03:15:37.507853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:15:37.507909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:15:39.313206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:16:09.313179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:16:37.528219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:16:37.528269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:16:39.313325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:17:09.313129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:17:37.546843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:17:37.546888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:17:39.313154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:18:09.313228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:18:37.567900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:18:37.567942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:18:39.313165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:19:09.313065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:19:37.588238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:19:37.588276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:19:39.313127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:20:09.313165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:20:37.609875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:20:37.609913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:20:39.313086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:21:09.313333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:21:37.627929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:21:37.627988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:21:39.313108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:22:09.313121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:22:37.668300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:22:37.668376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:22:39.314540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:23:09.317637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:23:37.687203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:23:37.687238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:23:39.313083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:24:09.313115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:24:37.705563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:24:37.705627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:24:39.313107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:25:09.313366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:25:37.729068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:25:37.729115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:25:39.313477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:26:09.313099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:26:37.747424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:26:37.747482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:26:39.313085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:27:09.313987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:27:37.766513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:27:37.766564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:27:39.313159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:28:09.313157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:28:37.784647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:28:37.784797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:28:39.313154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:29:09.313197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:29:37.803533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:29:37.803584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:29:39.313100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:30:09.313125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:30:37.821021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:30:37.821056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:30:39.313127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:31:09.313207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:31:37.840213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:31:37.840254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:31:39.313144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:32:09.313160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:32:37.859959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:32:37.860015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:32:39.313135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:33:09.313126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:33:37.877965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:33:37.878023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:33:39.313114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:34:09.313210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:34:37.896445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:34:37.896491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:34:39.313129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:35:09.313086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:35:37.920812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:35:37.920867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:35:39.313070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:36:09.313065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:36:37.939046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:36:37.939087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:36:39.313131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:37:09.313080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:37:37.958332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:37:37.958475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:37:39.313166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:38:09.313112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:38:37.978688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:38:37.978740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:38:39.313136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:39:09.313192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:39:37.997137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:39:37.997200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:39:39.313178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:40:09.313160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:40:38.015176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:40:38.015230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:40:39.313098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:41:09.313171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:41:38.032827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:41:38.032897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:41:39.313275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:42:09.313173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:42:38.050777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:42:38.050834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:42:39.313106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:43:09.313079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:43:38.069747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:43:38.069813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:43:39.313164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:44:09.313321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:44:38.092261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:44:38.092339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:44:39.313117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:45:09.313082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:45:38.111565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:45:38.111622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:45:39.313094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:46:09.313064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:46:38.129877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:46:38.129921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:46:39.313135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:47:09.313100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:47:38.147905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:47:38.147944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:47:39.313106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:48:09.313072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:48:38.166085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:48:38.166129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:48:39.313231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:49:09.313128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:49:38.188422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:49:38.188554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:49:39.313154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:50:09.313256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:50:38.205797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:50:38.205862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:50:39.313130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:51:09.313072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:51:38.226919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:51:38.226974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:51:39.313158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:52:09.313870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:52:38.245178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:52:38.245243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:52:39.313150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:53:09.313146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:53:38.264841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:53:38.264893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:53:39.313212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:54:09.313139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:54:38.284052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:54:38.284090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/25 03:54:39.313108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/25 03:55:09.313190 metrics.go:34: INFO No non-zero metrics in the last 30s