syahra712 commented on issue #5: URL: https://github.com/apache/solr-orbit/issues/5#issuecomment-6290458845
Thanks. #134 is merged, #137 is open for #136, and I'll work on #138 next. Once those land, the guide can describe one path that actually works. On OS-level telemetry, here's a split that I think keeps solr-orbit responsible only for what it can measure reliably: - **Any cluster, via Solr itself.** `SolrNodeStats` already reads `/api/node/system`, which exposes host CPU and memory, so this works for external clusters too with no agent. One small fix: `cpu_usage_percent` currently uses `processCpuLoad` and falls back to `systemCpuLoad` without saying so. Recording `process_cpu_percent` and `system_cpu_percent` as separate metrics would make runs comparable. - **Provisioned on the same host (from-distribution / from-sources / docker).** Orbit knows the Solr PID or container, so it can sample host and process CPU, RAM, disk I/O and network itself. psutil is already a dependency, and `DiskIo` already does the disk part per process. For Docker, the per-container numbers would come from the container stats API, so the host's other load doesn't pollute them. - **Remote or orchestrated (launchr / EC2).** Orbit can't sample a remote host well without running an agent there, so I'd delegate that to launchr. It could run node_exporter or something similar next to Solr and record the results alongside the run, and reportr would then join them by run id. solr-orbit would just document that boundary. If that split works for you, I'd open one issue for the separate CPU metrics plus the same-host sampler, after #138. The guide section for this issue can describe all three tiers. Does that match how you see the responsibility for solr-orbit vs. launchr? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
