POC
Full cost analysis against the log analyzer before any deploy.
The POC runs with read-only credentials and processes events locally; events stay on the machine.
You
cost POC on our Splunk
Log10x
Pulling up to 1,000,000 events from Splunk over the last 14d. Returned snapshot_id=snap_abc123.
You
show report snap_abc123
Log10x
Top driver: Payment_Gateway_Timeout $4.2K/wk in payments-svc → recommend Receiver cap at 5%. Projected savings $306K/yr across the stack. Full report at /tmp/log10x-reports/poc_from_siem-snap_abc123.md.
| You ask | Example answer |
|---|---|
| cost POC on our Splunk | Pulls a sample of up to 1,000,000 events by default from your log analyzer (Splunk / Datadog / Elasticsearch / CloudWatch / Sumo / Azure / GCP / ClickHouse). Returns a snapshot_id. |
show report snap_abc123 |
A 9-section report: top patterns by cost, cost per service, projected savings, per-pattern recommendations, suggested filter configs. |
cost POC from kubectl, namespace production, 1h |
Industry-pricing matrix built from a kubectl-sourced sample. Use when no log analyzer credentials are available yet. Sample-composition table calls out which pods dominate the bytes so the projection isn't trusted blind. |
Prerequisites
Read-only credentials for your log analyzer for POC submit and POC status. Local POC needs kubectl on PATH instead.
Every path runs the local 10x engine, which also needs:
- the
tenxCLI (install for macOS/Linux/Windows), or - a local Docker container (
LOG10X_TENX_MODE=docker, auto-detected and preferred when the mode is unset).