Algolia Monitoring

Live

API KEY

SEARCH MONITORING

Monitoring

Algolia Monitoring gives your agent search monitoring for Algolia clusters: operational status, incidents, search latency, indexing time, reachability, server inventory, and infrastructure metrics.

  • Per-user credentials: each call uses the actual user's API key, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Algolia Monitoring
agent · Acme Q3
Run
Check the status of clusters c4-eu and c7-us.
S
algoliamonitoring_get_cluster_status
84ms
Ops agent
Both clusters report operational. Neither shows degraded performance or an outage right now.
Sources: Algolia status, 2 clusters
algoliamonitoring
2 clusters
18:29
Message Claude...

Tools your ops agent reaches for on Algolia Monitoring, scoped per user.

CALL ANY TOOL
9 read-only tools for search monitoring: cluster status and reachability, incidents, search and indexing latency, servers, and infrastructure metrics.
algoliamonitoring_get_cluster_status
Get cluster status
Get the current operational status of one or more specific Algolia clusters. Returns a status map keyed by cluster name, where each value is operational, degraded_performance, partial_outage, or major_outage. Use this to check clusters you already know by name. Use get_status for every cluster, and list_cluster_incidents for incident history on these clusters.
Parameters
Name
Type
Required
Description
clusters
string
Required
Comma-separated list of Algolia cluster names to query, with no spaces. Use the cluster names returned by get_status or list_servers. Example: c1-de,c2-de,c3-de.
algoliamonitoring_get_indexing_time
Get indexing time
algoliamonitoring_get_infrastructure_metrics
Get infrastructure metrics
algoliamonitoring_get_latency
Get latency
algoliamonitoring_get_reachability
Get reachability
algoliamonitoring_get_status
Get status
algoliamonitoring_list_cluster_incidents
List cluster incidents
algoliamonitoring_list_incidents
List incidents
algoliamonitoring_list_servers
List servers
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Algolia Monitoring tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["algoliamonitoring"], toolNames: [
    "algoliamonitoring_get_cluster_status",
    "algoliamonitoring_list_cluster_incidents",
    "algoliamonitoring_get_latency"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Check the status of clusters c4-eu and c7-us" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["algoliamonitoring"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Check the status of clusters c4-eu and c7-us" }],
  tools,
});

// Execute the tool call with the user's vaulted Algolia Monitoring API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["algoliamonitoring"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Check the status of clusters c4-eu and c7-us" }],
  tools,
});

// Tool call runs with the user's vaulted Algolia Monitoring API key
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["algoliamonitoring"] }, pageSize: 100,
});

const agent = new Agent({
  name: "ops_agent",
  model: "gemini-2.5-pro",
  instruction: "Algolia Monitoring tools scoped to this user",
  tools,
});

await agent.run("Check the status of clusters c4-eu and c7-us");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Algolia Monitoring tool. Click to copy, paste into your agent, done.
Status and incidents
Copy the prompt
Copied
Is any Algolia cluster degraded right now?
Copy the prompt
Copied
List incidents for clusters c4-eu and c7-us.
Copy the prompt
Copied
Check whether c4-eu is reachable from every probe.
Latency
Copy the prompt
Copied
Show average search latency for c4-eu.
Copy the prompt
Copied
Compare indexing time across our clusters.
Copy the prompt
Copied
Which of our clusters has the slowest search latency?
Infrastructure
Copy the prompt
Copied
List the servers in our Algolia cluster with their region and status.
Copy the prompt
Copied
Show CPU and SSD usage for our servers over the last day.
Copy the prompt
Copied
Summarize all known Algolia incidents across clusters.
SEE HOW AUTH WORKS
Each user connects their own Algolia Monitoring API key once; Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
Algolia Monitoring
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Algolia Monitoring
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Algolia Monitoring
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Algolia Monitoring
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other monitoring and observability connectors.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Support and Ops Teams
Support triage agent
Fetches new Zendesk tickets, classifies them by type and urgency, searches the Notion knowledge base for an answer, and routes what it cannot resolve to Slack. Every call runs on the support agent's own delegated OAuth.
Test other agents
See the same per-user auth pattern across other monitoring and observability connectors.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
SUPPORT
Support triage agent
Classify new Zendesk tickets, search the Notion knowledge base for an answer, and route what it cannot resolve to Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Algolia Monitoring API key looks fine in a demo. In production every status check looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Algolia Monitoring today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Algolia Monitoring as the user or as a shared key?
As the user. Each user connects their own Algolia Monitoring API key once, and Scalekit sends it with every call. Audit logs attribute every action to that user, not a shared service account.
Where is the Algolia Monitoring API key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in Algolia Monitoring?
Yes. Filter by tool name in listScopedTools to expose only what you want. Scalekit also enforces scope checks before every API call.
What happens when a user revokes Algolia Monitoring access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
What can the agent see in Algolia Monitoring?
9 read-only tools: operational status for all or selected clusters, reachability from Algolia's monitoring probes, incident history, average search latency, indexing time, the server inventory for your clusters, and infrastructure metrics such as CPU idleness and SSD usage. None of the tools change anything in Algolia.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""algoliamonitoring"": {
""url"": ""https://mcp.scalekit.com/algoliamonitoring"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.algoliamonitoring]
url = ""https://mcp.scalekit.com/algoliamonitoring""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""algoliamonitoring"": {
""url"": ""https://mcp.scalekit.com/algoliamonitoring"",
""type"": ""http""
}
}
}