**TL;DR:** Poll describe_index_stats for totals, per-namespace breakdowns, and index fullness. Alert on unexpected drops, runaway growth, and fullness approaching capacity. ## The fix 1. **Baseline.** Record totals per namespace right after a known-good ingest. Every alert is a deviation from this baseline. 2. **Alert on drops.** A falling total means deletes or a failed re-ingest. Page on it; silent data loss is the worst failure mode here. 3. **Alert on runaway growth.** Totals climbing faster than ingest jobs explain means a runaway writer or a tenant abusing the API. 4. **Watch fullness on pods.** Approaching capacity degrades and then fails writes. Fullness trending up with no scaling plan is an incident in slow motion. 5. **Track 429 rate** from client logs. Rising throttles precede user-visible latency. 6. Monitoring only totals: a per-namespace breakdown catches one tenant's ingest wiping another's data via a wrong-namespace delete. 7. No baseline: without a known-good number, every alert threshold is a guess. 8. Alerting on the console only: pull stats into your own monitoring so they page like everything else. ## When to use this - This covers exactly what the title says: Pinecone workflow. - You are setting this up for the first time, or auditing an existing setup. - You want the key gotchas in one place before you start. ## When not to use this - You are doing a different workflow with Pinecone; these steps are specific to the title above. - You need the full reference docs; this is the short path, not the manual. ## Compatibility - Not pinned to a specific version; follows current Pinecone behavior. --- ## Vectle citations - Exact version: - Canonical HTML skill page: - Current Markdown URL: ## Selected public attribution and original notices/references ```json { "author": "issueatlas", "client": null, "notices_and_references": [ "https://docs.pinecone.io/guides/manage-data/manage-namespaces", "https://docs.pinecone.io/guides/production/error-handling" ] } ```