Http traffic capture vs KubeGlance

HTTP Traffic Capture is a lightweight HTTP & HTTPs packet capture tool for common users who have network analysis capabilities. Features: 1. Support HTTP and HTTPs traffic analysis 2. Support HTML, Javascript, CSS, picture (webp, jpeg, png) preview, and binary data viewing 3. Support for setting packet capture rules 4. Support historical packet capture records 5. Support filtering historical packet content 6. Support exporting the captured packet content Instructions: 1. The software can support HTTP packet capture by default. If you need to capture and parse HTTPs traffic, you need to install a certificate 2. Click the start button, the system will create and connect to the vpn, and start the packet capture process; if you reject the vpn configuration, the packet capture cannot be performed 3. Click the orange task bar to view the current session, and click the session to view the session request and response 4. Click the request line and response line in the session to export the corresponding value 5. You can filter the content of a specific domain name through the filter button 6. You can export the session content through the export button 7. Click the stop button, a history record will be generated for subsequent viewing 8. If you need to clean up all data, you can go to the settings page and click the clear all data button How the software works: After opening the packet capture, the software will start a vpn and direct the vpn data packet to the local HTTP proxy server. Complete the analysis and storage of the data packet in the local proxy server. For HTTTPs data, you need to install and trust the certificate to successfully parse it. Data security: Since packet capture software involves user privacy data, privacy protection is the most important design consideration for software. To this end, we have made the following mechanism for this purpose: 1. The software's CA key and CA certificate are dynamically and randomly generated by the software and stored in the sandbox. No one can know the user's CA private key. 2. The certificate cannot be shared between different users. 3. After reinstalling the application, the history will cause the certificate to become invalid, and the user can manually delete the certificate in the settings. 4. The certificate is valid for one year. After the certificate expires, the user needs to regenerate it before it can be used. 5. The HTTP data captured by the software is only stored locally and will not be uploaded to any other place. 6. The user cannot modify the network request through the software to prevent some improper behavior. System configuration instructions: HTTP proxy server: 127.0.0.1:9080 Certificate description file name: Traffic Capture YYYY-MM-dd HH:mm, where YYYY-MM-dd HH:mm is the time when the certificate is generated VPN description file name: "Traffic Capture"

KubeGlance is a native Kubernetes dashboard for iPhone, iPad, and Mac — a real client for the everyday questions: is my cluster okay, what are my pods doing, and what just changed? Import a kubeconfig and you are looking at your clusters in seconds. No account, no in-cluster agent, no telemetry. KubeGlance talks directly to your Kubernetes API servers with the credentials you already have, and it is read-only by default — you can leave it open against production without a second thought. ONE VIEW, EVERY CLUSTER Enable any set of contexts and pods, workloads, nodes, and events merge into a single live view, each row tagged with its source cluster. Name your clusters and color them — a red "prod" banner follows you everywhere. One unreachable cluster never blanks the others. BUILT FOR INCIDENTS Follow merged logs across all replicas of a workload — or hand-pick any pods, even across namespaces and clusters — in one chronological stream. Structured JSON and nginx lines parse into fields with level filters. Bookmark the line that matters and jump back to it. Search the whole buffer instantly, with regex when you want it. THE DETAILS THAT MATTER - Live pod tables with kubectl-accurate statuses (CrashLoopBackOff and friends) - Workload tables: Deployments, StatefulSets, DaemonSets, Jobs — ready over desired, trouble highlighted - Rollout history with revision compare: see exactly what each deploy changed - Search that speaks kubectl: type namespace:prod status:crash and filters become chips - CPU and memory from metrics-server; history and efficiency (reserved vs used, suggested requests) from Prometheus, VictoriaMetrics or Thanos, auto-detected - Cluster events feed with reason and namespace filters AFTER EVERY DEPLOY The checks you would otherwise run in a terminal, as views that appear only when your cluster has the capability: - GitOps: Flux Kustomizations and Helm releases with applied vs attempted revision and what blocks a reconcile, plus Argo CD apps with sync, health and drift - Autoscaling: HPA and KEDA merged per workload, with fallback, missing metrics and at-max called out, and replica and metric charts - Certificates: cert-manager and TLS secrets sorted by days left - Network: Services with the endpoints actually behind them, plus Ingress routing and Gateway API - Config: ConfigMaps and Secrets with the pods that read them, and which pods still run an older version - Releases: what image is running where, and when it rolled out - CronJobs with a last-run verdict, pod memory as a percent of its limit, and node pools against the provider ceiling - Storage: claims that never bound, volumes nobody mounts, namespace quotas and GPU claims - Resources: browse any kind the API server knows, with kubectl's own columns ALERTS Native notifications for crash loops, restart storms, NotReady nodes, stalled rollouts, failed jobs, expiring certificates, services without endpoints, and pods near their memory limit. Rules are scoped by cluster color, namespace and name patterns. Real-time on the Mac; best-effort background checks on iPhone and iPad. No kubeconfig handy? Tap "Try with a Demo Cluster" and explore with sample data — nothing real is contacted. Auth support: client certificates (mTLS) and bearer tokens, including inline PEM and multi-file kubeconfigs with kubectl merge semantics. KUBEGLANCE PRO — WHAT'S PAID, WHAT'S FREE Connecting your own clusters on iPhone and iPad requires a subscription: KubeGlance Pro. Current pricing and any free trial are shown in the app before you subscribe. Everything else is free — the built-in demo cluster, where you can explore the full app with sample data first, and the entire Mac app, which has no in-app purchases at all. Subscriptions renew automatically unless cancelled at least 24 hours before the end of the current period; manage or cancel anytime in your App Store account settings. Terms of Use: https://kubeglance.com/terms Privacy Policy: https://kubeglance.com/privacy