Service API Integrations
Monitor Algolia with Crowswatch
Connect Algolia to track cluster status and incidents, search latency, indexing times, cluster reachability, and infrastructure metrics directly from Crowswatch. These are infrastructure and performance figures, not end-user data.
What Crowswatch Monitors
- Cluster Status: the current availability of your specific cluster or clusters
- Cluster Incidents: open and recent incidents affecting your cluster or clusters
- Search Latency: average search-request latency for your cluster infrastructure over time
- Indexing Times: average indexing operation time for your cluster infrastructure over time
- Reachability: reachability of your clusters from external probe locations
- Infrastructure Metrics: detailed cluster infrastructure metrics. Available on the Algolia Premium or Elevate plan only
Status Pages vs Integrations: Why Algolia Appears Twice
Crowswatch surfaces Algolia on two distinct surfaces, for two different jobs.
| Surface | What it shows | Setup |
|---|---|---|
| Status Pages | Algolia’s global public status (up, degraded, or down), rolled up across all clusters | None. Add it from Add Services like any status page |
| Integrations (this page) | Your account’s specific cluster status and cluster infrastructure performance | Connect with your Application ID and a Monitoring API key |
In short: Status Pages answers “is Algolia up globally?” with no setup. This Integration answers “how are my clusters doing?” once you connect credentials.
Prerequisites
| Requirement | Detail |
|---|---|
| Application ID | Your Algolia Application ID, from the Algolia dashboard (Account, then API Keys) |
| Monitoring API key | A Monitoring-scoped API key from the same page. Not your Admin key |
| Estimated setup time | ~5 minutes |
Security: Use a Monitoring Key, Not Your Admin Key
Create a dedicated Monitoring API key for Crowswatch. Do not use your Admin API key.
- The Admin key can read and write your entire search index
- Crowswatch only needs read access to monitoring data, which a Monitoring key provides
- Crowswatch stores the key encrypted, never logs it, and never exposes it after entry
How to Connect
Navigate to: Crowswatch, Integrations, Connect Algolia
- Enter your Application ID
- Enter your Monitoring API Key
- Leave Clusters blank to auto-detect, or enter a comma-separated list to override
- Click Check feed access. Crowswatch validates the credentials, resolves your cluster or clusters, and shows which feeds are available
- Click Save
- Select the feeds you want to pull into your Insights view
Crowswatch resolves your cluster from the Monitoring key so the per-cluster feeds are scoped to your account rather than every Algolia cluster.
Choosing Feeds
You do not need to enable everything. Cluster Status and Search Latencyare the natural starting point: they answer “is my cluster healthy, and is search getting slower?” with the least noise. Add Indexing Times, Reachability, and Infrastructure Metrics as you need them.
| Feed | Shows | Availability |
|---|---|---|
| Cluster Status | Availability of your specific cluster or clusters | Connected |
| Cluster Incidents | Incidents affecting your cluster or clusters | Connected |
| Search Latency | Cluster infrastructure search latency over time | Connected |
| Indexing Times | Cluster infrastructure indexing time over time | Connected |
| Reachability | Cluster reachability from external probes | Connected |
| Infrastructure Metrics | Detailed cluster infrastructure metrics | Premium or Elevate plan only |
Troubleshooting Unavailable Feeds
When you run Check feed access, any feed the credentials or plan cannot serve is flagged with a specific reason rather than failing silently. The states are distinct on purpose.
Your Algolia Monitoring API key or Application ID is invalid.
A credentials problem. Confirm both the Application ID and the key, and make sure you used a Monitoring API key rather than the Admin key. This affects every feed.
Your Monitoring API key lacks access to this feed.
The key is valid but is not granted monitoring access for that feed. Adjust the key’s permissions in the Algolia dashboard.
Not available on your Algolia plan (Premium or Elevate required).
The Infrastructure Metrics feed is plan-gated. It becomes available on the Algolia Premium or Elevate plan. This is a plan state, not a credentials problem.
No cluster resolved yet. Add your cluster to enable this feed.
Automatic cluster detection found nothing for this key. Enter your cluster or clusters in the Clusters field as a comma-separated list, then check feed access again.
Alerting (Coming Soon)
Live metrics display is available now. Alerting on these feeds is not yet available for this integration. When it ships, it will follow the standard Crowswatch approach: a baseline-and-delta model that alerts on sustained deviation rather than single blips, one low-noise alert per event, and a recovery follow-up when a signal returns to normal.