Original Summary

When a test fails across multiple devices, you end up jumping between SSH sessions, searching logs, checking metrics, and opening Wireshark just to understand what happened. So I built LogOctopus — an open source tool that brings all that evidence into one test session. https://reddit.com/link/1xa9ttu/video/el5ahuaoshwh1/player 🎬 Live demo: https://kkuuba.github.io/LogOctopus/ What it does: 🔌 Collects logs from multiple devices over SSH — no agents required 📊 Combines logs, metrics, and command outputs in one timeline 📡 Lets you inspect packet captures alongside logs 🔄 Reconnects after device reboots 🤖 Integrates with automated tests through a REST API The goal is simple: spend less time gathering evidence and more time finding the actual cause of a failure. GitHub: https://github.com/kkuuba/LogOctopus I'd especially appreciate feedback on a few things: Would this be useful in your testing or debugging workflow? If not, what's missing? How do you currently collect and correlate logs when a test spans multiple devices? What would make you choose a tool like this over your existing scripts or a general-purpose logging stack? If you tried the project, was the setup and configuration straightforward?   submitted by   /u/kkuuba [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/20 05:34:33