By type
2022/04/23 03:11:00.448589 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/23 03:11:00.448766 metrics.go:23: INFO Metrics logging every 30s
2022/04/23 03:11:00.448772 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/23 03:11:00.449883 logstash.go:90: INFO Max Retries set to: 3
2022/04/23 03:11:00.450058 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/23 03:11:00.452631 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-s92jg
2022/04/23 03:11:00.453168 async.go:63: INFO Flush Interval set to: 1s
2022/04/23 03:11:00.453234 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/23 03:11:00.454209 beat.go:221: INFO filebeat start running.
2022/04/23 03:11:00.454273 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/23 03:11:00.459146 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/23 03:11:00.459210 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/23 03:11:00.459263 crawler.go:38: INFO Loading Prospectors: 1
2022/04/23 03:11:00.459490 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/23 03:11:00.459638 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/23 03:11:00.459655 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/23 03:11:00.459683 registrar.go:236: INFO Starting Registrar
2022/04/23 03:11:00.459734 sync.go:41: INFO Start sending events to output
2022/04/23 03:11:00.459768 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/23 03:11:20.465188 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/23 03:11:20.465349 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/23 03:11:20.465537 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/23 03:11:20.465598 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/23 03:11:20.465668 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/23 03:11:25.471634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:25.471698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:26.475594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:26.475660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:28.479329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:28.479363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:30.449262 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/23 03:11:32.499023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:32.499057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:40.503482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:40.503535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:56.508727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:11:56.508768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:12:00.449225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:12:28.512297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:12:28.512351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:12:30.449075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:13:00.449096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:13:28.515676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:13:28.515712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:13:30.454018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:14:00.449054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:14:28.522570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:14:28.522627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:14:30.449369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:15:00.449039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:15:28.527017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:15:28.527130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:15:30.449556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:16:00.449052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:16:25.485150 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/23 03:16:25.485296 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/23 03:16:25.485332 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/23 03:16:25.495496 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/23 03:16:28.531253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:16:28.531419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:16:30.449279 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/23 03:16:33.495884 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/23 03:17:00.449143 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/23 03:17:28.545702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:17:28.545736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:17:30.450095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:18:00.449199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:18:28.558134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:18:28.558190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:18:30.452583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:19:00.449490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:19:28.563984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:19:28.564188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:19:30.449159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:20:00.449111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:20:28.568652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:20:28.568687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:20:30.450410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:21:00.449202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:21:28.572402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:21:28.572443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:21:30.449047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:22:00.449102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:22:28.575950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:22:28.575985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:22:30.449050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:23:00.449138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:23:28.579753 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:23:28.579796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:23:30.449319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:24:00.449073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:24:28.583286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:24:28.583352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:24:30.449095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:25:00.449206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:25:28.586486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:25:28.586533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:25:30.449063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:26:00.449130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:26:28.594185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:26:28.594257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:26:30.452622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:27:00.450028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:27:28.598335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:27:28.598403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:27:30.449066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:28:00.449090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:28:28.601625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:28:28.601659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:28:30.449235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:29:00.450199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:29:28.605059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:29:28.605092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:29:30.449118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:30:00.449068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:30:28.608447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:30:28.608481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:30:30.449149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:31:00.449042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:31:28.612553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:31:28.612646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:31:30.449036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:32:00.449137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:32:28.617081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:32:28.617130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:32:30.449098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:33:00.449270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:33:28.623965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:33:28.624001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:33:30.449164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:34:00.449217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:34:28.627802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:34:28.627837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:34:30.449432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:35:00.449092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:35:28.635733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:35:28.635768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:35:30.449107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:36:00.452390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:36:28.648773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:36:28.648816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:36:30.449337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:37:00.449079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:37:28.655032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:37:28.655068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:37:30.449043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:38:00.449128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:38:28.658239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:38:28.658288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:38:30.449105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:39:00.449122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:39:28.662229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:39:28.662264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:39:30.449186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:40:00.449154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:40:28.666300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:40:28.666336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:40:30.449304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:41:00.449106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:41:28.670972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:41:28.671031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:41:30.449117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:42:00.449090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:42:28.675115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:42:28.675147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:42:30.449113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:43:00.449034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:43:28.679124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:43:28.679180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:43:30.449144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:44:00.449146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:44:28.683523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:44:28.683568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:44:30.449104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:45:00.449484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:45:28.687462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:45:28.687511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:45:30.449127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:46:00.450077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:46:28.690984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:46:28.691027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:46:30.449082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:47:00.449014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:47:28.694075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:47:28.694111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:47:30.449074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:48:00.449050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:48:28.698385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:48:28.698421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:48:30.449097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:49:00.449892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:49:28.702471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:49:28.702508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:49:30.449107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:50:00.449087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:50:28.707979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:50:28.708038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:50:30.449148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:51:00.449084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:51:28.712554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:51:28.712603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:51:30.449084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:52:00.449012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:52:28.718012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:52:28.718042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:52:30.449066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:53:00.449157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:53:28.722401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:53:28.722450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:53:30.449324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:54:00.449040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:54:28.728107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:54:28.728160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:54:30.449037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:55:00.449115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:55:28.732679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:55:28.732716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:55:30.449092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:56:00.449147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:56:28.739928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:56:28.739981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:56:30.449077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:57:00.452724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:57:28.747516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:57:28.747554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:57:30.449067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:58:00.449070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:58:28.754165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:58:28.754208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:58:30.449069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:59:00.449233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 03:59:28.760662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:59:28.760696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 03:59:30.449158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:00:00.449135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:00:28.763879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:00:28.763917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:00:30.449634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:01:00.449055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:01:28.768796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:01:28.768832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:01:30.449138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:02:00.449115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:02:28.772126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:02:28.772174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:02:30.449177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:03:00.449094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:03:28.775773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:03:28.775914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:03:30.449094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:04:00.449072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:04:28.779994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:04:28.780027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:04:30.449095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:05:00.449052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:05:28.784578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:05:28.784616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:05:30.449123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:06:00.449131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:06:28.791800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:06:28.791849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:06:30.449142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:07:00.449027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:07:28.795887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:07:28.795921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:07:30.449126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:08:00.449069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:08:28.799141 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:08:28.799174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:08:30.449044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:09:00.449080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:09:28.802126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:09:28.802160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:09:30.449084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:10:00.449125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:10:28.805605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:10:28.805661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:10:30.449008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:11:00.449088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:11:28.811205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:11:28.811240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:11:30.449047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:12:00.449028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:12:28.816900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:12:28.816934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:12:30.450286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:13:00.449108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:13:28.823897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:13:28.823951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:13:30.449267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:14:00.449115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:14:28.828408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:14:28.828443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:14:30.449074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:15:00.449050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:15:28.833668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:15:28.833705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:15:30.449073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:16:00.449160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:16:28.845764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:16:28.845816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:16:30.449247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:17:00.449046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:17:28.852662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:17:28.852697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:17:30.449100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:18:00.449043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:18:28.856443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:18:28.856480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:18:30.452600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:19:00.449034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:19:28.866657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:19:28.866713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:19:30.449099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:20:00.449080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:20:28.870393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:20:28.870430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:20:30.449172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:21:00.449205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:21:28.873940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:21:28.873993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:21:30.451065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:22:00.449010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:22:28.877161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:22:28.877207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:22:30.449074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:23:00.449073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:23:28.880839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:23:28.880889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:23:30.449964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:24:00.449048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:24:28.884133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:24:28.884171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:24:30.449048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:25:00.449141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:25:28.887615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:25:28.887652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:25:30.452692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:26:00.449118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:26:28.892242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:26:28.892282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:26:30.449038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:27:00.449144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:27:28.895503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:27:28.895542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:27:30.449548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:28:00.449085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:28:28.899038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:28:28.899077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:28:30.449139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:29:00.449039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:29:28.902390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:29:28.902450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:29:30.449040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:30:00.451815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:30:28.908533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:30:28.908566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:30:30.449097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:31:00.451079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:31:28.912173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:31:28.912206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:31:30.450327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:32:00.449057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:32:28.916080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:32:28.916126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:32:30.449116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:33:00.449136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:33:28.919736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:33:28.919776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:33:30.449058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:34:00.449076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:34:28.923616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:34:28.923654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:34:30.449105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:35:00.449100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:35:28.926736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:35:28.926851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:35:30.449394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:36:00.449015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:36:28.931257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:36:28.931291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:36:30.449091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:37:00.449069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:37:28.935827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:37:28.935865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:37:30.449094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:38:00.449130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:38:28.946041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:38:28.946103 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:38:30.449053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:39:00.449979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:39:28.956539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:39:28.956575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:39:30.449888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:40:00.449510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:40:28.963042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:40:28.963093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:40:30.449469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:41:00.449657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:41:28.966733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:41:28.966769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:41:30.449071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:42:00.450415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:42:28.970606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:42:28.970640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:42:30.449072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:43:00.449057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:43:28.974095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:43:28.974128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:43:30.449162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:44:00.449154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:44:28.977500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:44:28.977634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:44:30.449103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:45:00.449035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:45:28.980849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:45:28.980884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:45:30.449136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:46:00.449025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:46:28.984566 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:46:28.984599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:46:30.449054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:47:00.449046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:47:28.987925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:47:28.987958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:47:30.449035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:48:00.449096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:48:28.991217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:48:28.991255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:48:30.449064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:49:00.449034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:49:28.994678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:49:28.994721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:49:30.449039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:50:00.449101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:50:28.998797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:50:28.998835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:50:30.449121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:51:00.449120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:51:29.002718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:51:29.002752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:51:30.449146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:52:00.449051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:52:29.006029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:52:29.006072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:52:30.449093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:53:00.449187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:53:29.010422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:53:29.010567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:53:30.449121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:54:00.449811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:54:29.016160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:54:29.016194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:54:30.449071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:55:00.449070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:55:29.019522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:55:29.019561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:55:30.449138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:56:00.450528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:56:29.022597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:56:29.022636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:56:30.449132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:57:00.449100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:57:29.031068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:57:29.031121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:57:30.449080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:58:00.451123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:58:29.036038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:58:29.036099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:58:30.449122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:59:00.449106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 04:59:29.041755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:59:29.041806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 04:59:30.449102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 05:00:00.449080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/23 05:00:29.053413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 05:00:29.053453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/23 05:00:30.449097 metrics.go:34: INFO No non-zero metrics in the last 30s