By type
2022/03/02 03:13:19.815263 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/02 03:13:19.815308 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/02 03:13:19.815365 logstash.go:90: INFO Max Retries set to: 3
2022/03/02 03:13:19.815408 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/02 03:13:19.815488 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-bmfm6
2022/03/02 03:13:19.815648 async.go:63: INFO Flush Interval set to: 1s
2022/03/02 03:13:19.815667 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/02 03:13:19.816004 metrics.go:23: INFO Metrics logging every 30s
2022/03/02 03:13:19.816103 beat.go:221: INFO filebeat start running.
2022/03/02 03:13:19.816165 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/02 03:13:20.403378 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/02 03:13:20.403473 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/02 03:13:20.403564 crawler.go:38: INFO Loading Prospectors: 1
2022/03/02 03:13:20.403628 sync.go:41: INFO Start sending events to output
2022/03/02 03:13:20.403627 registrar.go:236: INFO Starting Registrar
2022/03/02 03:13:20.403774 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/02 03:13:20.403903 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/02 03:13:20.404085 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/02 03:13:20.404148 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/02 03:13:30.405217 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/02 03:13:30.405372 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/02 03:13:30.405571 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/02 03:13:30.405660 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/02 03:13:30.405689 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/02 03:13:35.549509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:35.549543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:36.553671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:36.553710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:38.557904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:38.557939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:42.571440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:42.571478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:49.816332 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=72 registrar.writes=1
2022/03/02 03:13:50.577095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:13:50.577129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:14:06.588644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:14:06.588680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:14:19.816235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:14:38.594739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:14:38.594768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:14:49.816279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:15:19.816346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:15:38.632392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:15:38.632427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:15:49.816299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:16:19.816271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:16:38.637884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:16:38.637934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:16:49.816280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:17:19.816302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:17:38.644557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:17:38.644600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:17:49.816266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:18:19.816228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:18:35.414208 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/02 03:18:38.650407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:18:38.650437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:18:49.816285 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/02 03:19:19.816291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:19:38.655500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:19:38.655532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:19:49.816276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:20:19.816352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:20:38.661322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:20:38.661369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:20:49.816280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:21:19.816269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:21:38.667070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:21:38.667096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:21:49.816240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:22:19.816268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:22:38.673253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:22:38.673293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:22:49.816246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:23:19.816352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:23:38.678796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:23:38.678832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:23:49.816273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:24:19.816282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:24:38.685192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:24:38.685224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:24:49.816244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:25:19.816247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:25:38.690681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:25:38.690734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:25:49.816264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:26:19.816351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:26:38.697224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:26:38.697276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:26:49.816343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:27:19.816282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:27:38.703003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:27:38.703091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:27:49.816257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:28:19.816265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:28:38.709085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:28:38.709129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:28:49.816306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:29:19.816266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:29:38.715473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:29:38.715513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:29:49.816279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:30:19.816330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:30:38.721975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:30:38.722008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:30:49.816288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:31:19.816304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:31:38.727069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:31:38.727099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:31:49.816262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:32:19.816274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:32:38.734123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:32:38.734166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:32:49.816316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:33:19.816228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:33:38.739719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:33:38.739753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:33:49.816239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:34:19.816267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:34:38.745888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:34:38.745927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:34:49.816252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:35:19.816296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:35:38.751370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:35:38.751396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:35:49.816326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:36:19.816258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:36:38.756921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:36:38.756978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:36:49.816295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:37:19.816225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:37:38.763314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:37:38.763398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:37:49.816284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:38:19.816270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:38:38.769589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:38:38.769618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:38:49.816273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:39:19.816322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:39:38.774663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:39:38.774691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:39:49.816338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:40:19.816335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:40:38.780474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:40:38.780505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:40:49.816285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:41:19.816294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:41:38.786980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:41:38.787018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:41:49.816390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:42:19.816256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:42:38.792703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:42:38.792747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:42:49.816378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:43:19.816268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:43:38.798957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:43:38.799073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:43:49.816246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:44:19.816320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:44:38.805269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:44:38.805306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:44:49.816346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:45:19.816277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:45:38.810695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:45:38.810841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:45:49.816289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:46:19.816273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:46:38.817405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:46:38.817442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:46:49.816276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:47:19.816298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:47:38.823261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:47:38.823297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:47:49.816347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:48:19.816277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:48:38.828643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:48:38.828672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:48:49.816321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:49:19.816236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:49:38.834484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:49:38.834522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:49:49.816274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:50:19.816245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:50:38.840197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:50:38.840253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:50:49.816362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:51:19.816305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:51:38.846003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:51:38.846034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:51:49.816306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:52:19.816288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:52:38.852042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:52:38.852083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:52:49.816351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:53:19.816294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:53:38.858047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:53:38.858090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:53:49.816279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:54:19.816278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:54:38.863584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:54:38.863614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:54:49.816263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:55:19.816249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:55:38.869263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:55:38.869290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:55:49.816364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:56:19.816328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:56:38.875622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:56:38.875674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:56:49.816288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:57:19.816296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:57:38.881419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:57:38.881485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:57:49.816239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:58:19.816274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:58:38.886441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:58:38.886471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:58:49.816260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:59:19.816308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 03:59:38.891841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:59:38.891877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 03:59:49.816411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:00:19.816267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:00:38.897006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:00:38.897050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:00:49.816312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:01:19.816303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:01:38.904046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:01:38.904077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:01:49.816256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:02:19.816471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:02:38.909946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:02:38.909994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:02:49.816368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:03:19.816263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:03:38.916328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:03:38.916357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:03:49.816217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:04:19.816290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:04:38.922392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:04:38.922423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:04:49.816279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:05:19.816344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:05:38.928287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:05:38.928476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:05:49.816251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:06:19.816450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:06:38.934483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:06:38.934512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:06:49.816389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:07:19.816377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:07:38.939955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:07:38.939985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:07:49.816253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:08:19.816286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:08:38.946257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:08:38.946291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:08:49.816313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:09:19.816245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:09:38.952750 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:09:38.952793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:09:49.816267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:10:19.816337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/02 04:10:38.958883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:10:38.958918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/02 04:10:49.816426 metrics.go:34: INFO No non-zero metrics in the last 30s