Connect AI agents to Algolia Monitoring

Scalekit connector

The Algolia Monitoring connector lets your AI agent act in each user's Algolia Monitoring account. Each user connects their own Algolia Monitoring API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 9 tools.

Tools: 9
What they doRead · write · destructive: 9 · 0 · 09 read0 write0 destructive
Users sign in with: API key

Setup

Install the SDK
- Node.js
- Python
Terminal window
npm install @scalekit-sdk/node dotenv
Terminal window
pip install scalekit-sdk-python python-dotenv
Set your credentials
Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.
.env
```
SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
SCALEKIT_CLIENT_ID=<your-client-id>
SCALEKIT_CLIENT_SECRET=<your-client-secret>
```
Create the Algolia Monitoring connection
In AgentKit > Connections, create an Algolia Monitoring connection. The name you give it is the connection_name your code passes. See Configure connections.

Authorize a user and make your first call

Node.js
Python

1
import { ScalekitClient } from '@scalekit-sdk/node'
2
import 'dotenv/config'
3
import { createInterface } from 'node:readline/promises'
4

5
const scalekit = new ScalekitClient(
6
  process.env.SCALEKIT_ENVIRONMENT_URL,
7
  process.env.SCALEKIT_CLIENT_ID,
8
  process.env.SCALEKIT_CLIENT_SECRET,
9
)
10
const actions = scalekit.actions
11

12
const connector = 'algoliamonitoring'
13
const identifier = 'user_123'
14

15
// Generate an authorization link for the user
16
const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
17
console.log('Authorize Algolia Monitoring:', link)
18
const rl = createInterface({ input: process.stdin, output: process.stdout })
19
await rl.question('Press Enter after authorizing...')
20
rl.close()
21

22
// Make your first call
23
const result = await actions.executeTool({
24
  connector,
25
  identifier,
26
  toolName: 'algoliamonitoring_get_status',
27
  toolInput: {},
28
})
29
console.log(result)

npx tsx quickstart.mts

1
import os
2
from scalekit import ScalekitClient
3
from dotenv import load_dotenv
4
load_dotenv()
5

6
scalekit_client = ScalekitClient(
7
    env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
8
    client_id=os.getenv("SCALEKIT_CLIENT_ID"),
9
    client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
10
)
11
actions = scalekit_client.actions
12

13
connection_name = "algoliamonitoring"
14
identifier = "user_123"
15

16
# Generate an authorization link for the user
17
link_response = actions.get_authorization_link(
18
    connection_name=connection_name,
19
    identifier=identifier,
20
)
21
print("Authorize Algolia Monitoring:", link_response.link)
22
input("Press Enter after authorizing...")
23

24
# Make your first call
25
result = actions.execute_tool(
26
    tool_input={},
27
    tool_name="algoliamonitoring_get_status",
28
    connection_name=connection_name,
29
    identifier=identifier,
30
)
31
print(result)

python quickstart.py

Each user opens the link once and enters their Algolia Monitoring credentials there. See Authorize a user for the full flow and statuses.

Tools

Pass the exact name to execute_tool

Try in Playground Request a tool

algoliamonitoring_get_cluster_statusGet the current operational status of one or more specific Algolia clusters.Read-only
Get Status of Selected Clusters
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.
Inputs
clustersstringrequired
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_timeGet indexing latency metrics for one or more Algolia clusters.Read-only
Get Indexing Time
Get indexing latency metrics for one or more Algolia clusters. Returns time series per cluster name, where each point has a millisecond Unix timestamp and a latency value in milliseconds, measured on Algolia's internal monitoring index. Use this for infrastructure-level monitoring, not for the indexing performance of your own index. Use get_latency for search latency.
Inputs
clustersstringrequired
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. These are infrastructure-level metrics, not a measure of a single application's indexing.
algoliamonitoring_get_infrastructure_metricsGet infrastructure metrics for your Algolia application, aggregated over a chosen time window.Read-only
Get Infrastructure Metrics
Get infrastructure metrics for your Algolia application, aggregated over a chosen time window. Returns time series keyed by metric and then by server name, where each point has a millisecond Unix timestamp and a value. Metrics cover CPU idleness, SSD usage, RAM used for search and indexing, and average build time. Use this for resource usage trends. Requires an Algolia Premium or Elevate plan. Use get_latency for search latency and get_cluster_status for current health.
Inputs
metricstringrequired
Infrastructure metric to report. One of avg_build_time (average index build time in seconds), ssd_usage (SSD usage as a percentage of RAM), ram_search_usage (RAM used for search in MB), ram_indexing_usage (RAM used for indexing in MB), cpu_usage (CPU idleness in percent), or * to return all metrics. Example: cpu_usage.one of avg_build_timessd_usageram_search_usageram_indexing_usagecpu_usage*
periodstringrequired
Time window over which to aggregate the metrics. One of minute (last minute, 1 data point per 10 seconds), hour (last hour, 1 per minute), day (last day, 1 per 10 minutes), week (last week, 1 per hour), or month (last month, 1 per day). Example: week.one of minutehourdayweekmonth
algoliamonitoring_get_latencyGet the average search request latency for one or more Algolia clusters.Read-only
Get Search Latency
Get the average search request latency for one or more Algolia clusters. Returns time series per cluster name, where each point has a millisecond Unix timestamp and a latency value in milliseconds. Use this to measure search speed. Use get_indexing_time for indexing latency, and get_cluster_status for current health.
Inputs
clustersstringrequired
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_reachabilityTest whether one or more Algolia clusters are reachable from Algolia's monitoring probes.Read-only
Get Cluster Reachability
Test whether one or more Algolia clusters are reachable from Algolia's monitoring probes. Returns a map keyed by cluster name, where each value maps a probe name to true when reachable or false when not. Use this to diagnose connectivity problems. Use get_cluster_status for the reported operational status.
Inputs
clustersstringrequired
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_statusGet the current operational status of all Algolia clusters and instances.Read-only
Get Status of All Clusters
Get the current operational status of all Algolia clusters and instances. Returns a status map keyed by cluster name, where each value is operational, degraded_performance, partial_outage, or major_outage. Use this for a fleet-wide health overview. Use get_cluster_status to check specific clusters, and list_incidents for known incidents.
Inputs
This tool takes no inputs.
algoliamonitoring_list_cluster_incidentsList known incidents for one or more specific Algolia clusters.Read-only
List Incidents for Selected Clusters
List known incidents for one or more specific Algolia clusters. Returns incidents grouped by cluster name; each entry has a millisecond Unix timestamp and a details object with a title and a status (operational, degraded_performance, partial_outage, or major_outage). Use this when you know the cluster names. Use list_incidents for all clusters, and get_cluster_status for current health only.
Inputs
clustersstringrequired
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_list_incidentsList known incidents across all Algolia clusters.Read-only
List All Incidents
List known incidents across all Algolia clusters. Returns incidents grouped by cluster name; each entry has a millisecond Unix timestamp and a details object with a title and a status (operational, degraded_performance, partial_outage, or major_outage). Use this for a fleet-wide incident history. Use list_cluster_incidents to limit results to specific clusters, and get_status for current health only.
Inputs
This tool takes no inputs.
algoliamonitoring_list_serversList the servers that belong to Algolia clusters.Read-only
List Servers
List the servers that belong to Algolia clusters. Returns an inventory array where each server has a name, cluster, region, replica flag, status, and type. When authenticated, the list covers the cluster assigned to your Algolia application. Use this to discover cluster and server names before calling get_cluster_status, get_latency, or other cluster-specific tools.
Inputs
This tool takes no inputs.

Setup

Install the SDK

Set your credentials

Create the Algolia Monitoring connection

Authorize a user and make your first call

Tools

Call it

Returns

Get Status of Selected Clusters

Inputs

Get Indexing Time

Inputs

Get Infrastructure Metrics

Inputs

Get Search Latency

Inputs

Get Cluster Reachability

Inputs

Get Status of All Clusters

Inputs

List Incidents for Selected Clusters

Inputs

List All Incidents

Inputs

List Servers

Inputs

Related: other Monitoring connectors