Ellipse Gradient for Header

Cisco ThousandEyes Integration Guide

Connect Cisco ThousandEyes REST APIs and selected alert notifications with enterprise workflows, incident platforms, data stores, and observability systems.

Cisco ThousandEyes integration options at a glance

Cisco ThousandEyes provides versioned REST APIs for monitoring configuration, Tests, Agents, Agent Clusters, Alerts, test results, and performance metrics. Selected alert and event scenarios can generate webhook-style notifications, although coverage is not universal across all resources. Martini can consume these APIs with bearer-token authentication, transform ThousandEyes JSON, schedule paginated metric or configuration synchronization, and expose an API endpoint for supported notifications. Workflows can apply checkpoints, deduplicate alerts, enrich notifications with REST lookups, and route normalized data to incident, CMDB, database, analytics, or messaging platforms. Bulk exports, GraphQL, SOAP, file APIs, and direct database access were not confirmed.

Integration pointSupported by Cisco ThousandEyes?Common use casesHow Martini supports it
REST APIsYesRetrieve and manage documented monitoring configuration and observability resources, including Tests, Agents, Agent Clusters, Alerts, results, and metrics.Martini can consume versioned REST endpoints, authenticate with a bearer token, map JSON, apply workflow logic, and expose normalized APIs.
Webhooks / outbound callbacksLimitedSend selected alert or event notifications to external systems when configured conditions occur; coverage is not universal across ThousandEyes resources.Martini can expose an API endpoint, validate and deduplicate notifications, enrich them with REST calls, and route them downstream.
Metrics and reporting APIsYesRetrieve availability, latency, loss, response-time, DNS, network-path, and related monitoring measurements for reporting and correlation.Martini can schedule bounded queries, paginate results, checkpoint progress, transform measurements, and write them to databases or analytics platforms.
AuthenticationYesAPI requests use bearer credentials issued as ThousandEyes API tokens, with access governed by the associated user or account permissions.Martini can store tokens in secrets or secure environment configuration and inject them into requests without placing them in workflow definitions or payloads.
Bulk / async / batch APIsNot confirmedA dedicated bulk or asynchronous export should be validated for each resource before large-scale extraction is designed.Where no bulk endpoint exists, Martini can process controlled pages with deterministic ordering, checkpoints, concurrency limits, and retries.
File / attachment APIsNot confirmedNo general ThousandEyes file import, export, or attachment API was confirmed.Martini should use documented REST resources or notifications rather than assuming file-based exchange.
Database / analytics accessNot confirmedDirect database access was not confirmed; integrations should use ThousandEyes APIs or documented notifications.Martini can write retrieved and transformed data to an approved downstream database without requiring direct ThousandEyes database access.
GraphQL APIsNot confirmedNo official Cisco ThousandEyes GraphQL API documentation was identified.Martini can use the documented REST APIs instead and expose a normalized API if consumers require a different contract.

How Cisco ThousandEyes exposes data and business events

Cisco ThousandEyes REST APIs

Cisco ThousandEyes versioned REST APIs provide access to monitoring configuration and observability data, including Tests, Agents, Agent Clusters, Alerts, results, and metrics. Available fields and operations depend on the API version, resource, subscription, and account permissions.

Martini implementation pattern

Martini uses a workflow to call the relevant REST endpoints with a bearer token, process JSON responses, apply pagination or time-window logic, and map the result to a downstream contract. The workflow can expose a normalized Martini API so consumers do not depend directly on ThousandEyes response formats.

Implementation sequence

Authenticate with a least-privilege ThousandEyes API token
Call the documented resource endpoint
Process pages or bounded metric windows
Validate required identifiers and response fields
Map ThousandEyes JSON to the target model
Apply filtering, enrichment, and business rules،

ThousandEyes webhook-style notifications

ThousandEyes supports webhook-style notifications for selected alert or event scenarios. These notifications are partial event coverage rather than a universal change stream for every ThousandEyes object.

Martini implementation pattern

Martini exposes an API endpoint for the configured notification, validates the request and payload, uses replay and idempotency controls, and retrieves authoritative alert or test details from the REST API when the notification is only a summary. The workflow then routes the normalized event to an incident, messaging, or analytics platform.

Implementation sequence

Receive the configured ThousandEyes notification
Validate the request and required event identifiers
Reject or quarantine malformed payloads
Deduplicate using an alert or event identifier
Retrieve authoritative details from the REST API
Apply severity and routing rules and deliver the event

Scheduled metrics synchronization

ThousandEyes metrics and reporting resources can be queried periodically for availability, latency, loss, response time, DNS, network-path, and related measurements. Retention, granularity, and query limits depend on the account and endpoint.

Martini implementation pattern

A Martini scheduler starts a workflow that reads a bounded time window, processes pages in deterministic order, stores a checkpoint, and writes normalized measurements to a database or analytics platform. Failed pages can be retried without replaying successfully committed data.

Implementation sequence

Start the scheduled synchronization workflow
Load the last successful checkpoint
Request a bounded metric window
Process each response page in deterministic order
Transform measurements and dimensions
Write results and persist the new checkpoint

Common Cisco ThousandEyes integration patterns

Pattern 1: Route ThousandEyes alerts to ServiceNow

When to use this pattern

Use this pattern when network, web, DNS, endpoint, or other ThousandEyes conditions must create or update operational incidents. It combines selected webhook notifications with REST enrichment and idempotent incident handling.

Integration direction
Cisco ThousandEyes
Martini
ServiceNow
Example Mapping
Cisco ThousandEyes FieldCanonical FieldTarget Field
alertIdexternalAlertIdcorrelation_id
alertStatestatusstate
severitypriorityurgency
testNamemonitoringTestshort_description
Martini implementation pattern

A Martini API receives the supported notification, validates and deduplicates it, then a workflow retrieves the current Alert, Test, or Agent details. Business rules map severity and recovery state to ServiceNow behavior. The workflow creates or updates the incident using the ThousandEyes identifier and retries transient downstream failures without creating duplicates.

Martini capabilities used
  • APIs
  • workflows
  • data mapping
  • business rules
  • error handling
  • idempotency

Pattern 2: Synchronize ThousandEyes metrics to a data warehouse

When to use this pattern

Use this pattern for historical availability, latency, loss, response-time, DNS, or network-path reporting across tests, agents, regions, and applications.

Integration direction
Cisco ThousandEyes
Martini
PostgreSQL
Example Mapping
Cisco ThousandEyes FieldCanonical FieldTarget Field
testIdmonitoringTestIdtest_id
agentIdmeasurementAgentIdagent_id
latencylatencyMslatency_ms
measurementTimestampobservedAtobserved_at
Martini implementation pattern

A scheduled Martini workflow queries bounded metric windows, handles pagination, and stores a timestamp or identifier checkpoint. It transforms ThousandEyes measurements into warehouse rows, validates late-arriving data, and uses an idempotent key for safe retries. Failed pages remain replayable while completed windows are not reinserted.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination and checkpointing
  • data mapping
  • SQL database integration
  • error handling

Pattern 3: Send actionable events to PagerDuty or Teams

When to use this pattern

Use this pattern when operations teams need filtered notifications rather than every ThousandEyes event. Severity, environment, ownership, alert state, and recovery information determine the destination and message.

Integration direction
Cisco ThousandEyes
Martini
PagerDuty
Example Mapping
Cisco ThousandEyes FieldCanonical FieldTarget Field
alertIdeventKeydedup_key
severityurgencyseverity
alertStateeventActionevent_action
affectedTestserviceContextcomponent
Martini implementation pattern

Martini receives a supported notification or polls alert state, enriches it with REST data, and applies routing and suppression rules. It formats the target request, preserves the ThousandEyes identifier, and handles open, update, and recovery states consistently. Retry and deduplication logic prevents repeated on-call incidents or channel messages.

Martini capabilities used
  • API endpoints
  • workflows
  • transformation
  • business rules
  • retry handling
  • duplicate prevention

Pattern 4: Synchronize ThousandEyes configuration with a CMDB

When to use this pattern

Use this pattern when the organization needs monitoring coverage and network-observability configuration represented alongside configuration-management data.

Integration direction
Cisco ThousandEyes
Martini
ServiceNow
Example Mapping
Cisco ThousandEyes FieldCanonical FieldTarget Field
testIdconfigurationItemExternalIdcorrelation_id
testNameconfigurationItemNamename
agentClusterIdmonitoringLocationGrouplocation_group
testStatuslifecycleStatusinstall_status
Martini implementation pattern

A scheduled workflow retrieves Tests, Agents, Agent Clusters, and relevant metadata, compares the result with the CMDB representation, and classifies new, changed, and removed objects. Martini applies target-specific upsert and retirement rules, records synchronization outcomes, and isolates API or target failures for retry.

Martini capabilities used
  • scheduler triggers
  • REST API consumption
  • mapping
  • comparison logic
  • business rules
  • workflow monitoring

Applications commonly integrated with Cisco ThousandEyes

Cisco ThousandEyes data can be orchestrated with incident management, notification, analytics, application-performance, and configuration-management products. The exact delivery method should be validated for each target; Martini can consume the ThousandEyes APIs or supported notifications and then call the target application's documented interfaces.

Application Scenario Direction Martini Pattern
ServiceNow Create or update incidents, events, and operational records from ThousandEyes alerts and enriched test details. Cisco ThousandEyes → Martini → ServiceNow Receive a supported notification or poll alert status, retrieve authoritative ThousandEyes details, map severity and identifiers to ServiceNow fields, and use an idempotent create-or-update workflow.
PagerDuty Trigger on-call incidents for significant network, application, endpoint, or availability conditions. Cisco ThousandEyes → Martini → PagerDuty Normalize alert state and severity, apply routing and suppression rules, and invoke the PagerDuty interface while retaining the ThousandEyes alert identifier for correlation and recovery handling.
Splunk Centralize ThousandEyes alerts and performance measurements with broader operations and security data. Cisco ThousandEyes → Martini → Splunk Schedule bounded metric extraction or process notifications, normalize the JSON into an analytics event model, enrich with test and agent metadata, and forward accepted events to Splunk.
Slack Send concise, actionable monitoring notifications and alert summaries to operational channels. Cisco ThousandEyes → Martini → Slack Receive or poll ThousandEyes events, filter by severity, ownership, and environment, format a channel message, and prevent repeated deliveries using alert-state tracking.
Microsoft Teams Deliver network and application alert notifications to enterprise operations channels. Cisco ThousandEyes → Martini → Microsoft Teams Map normalized ThousandEyes alert data to the receiving Teams interface, apply routing rules, and handle retries without producing duplicate notifications.
Cisco AppDynamics Correlate ThousandEyes network-experience measurements with application-performance information. Cisco ThousandEyes → Martini → Cisco AppDynamics Retrieve selected metrics, correlate tests or monitored services with AppDynamics identifiers, transform measurements into the target model, and route only validated correlations.
Jira Create engineering or operations work items for recurring performance problems and investigation follow-up. Cisco ThousandEyes → Martini → Jira Apply recurrence and severity rules to alerts or metric summaries, enrich the issue payload with test context, and create or update Jira work items using a stable correlation key.
Datadog Correlate ThousandEyes network telemetry with infrastructure and application monitoring data. Cisco ThousandEyes → Martini → Datadog Extract bounded metric windows or notifications, map dimensions such as test, agent, region, and latency, and deliver normalized measurements through the target's supported ingestion interface.

How to build a Cisco ThousandEyes integration in Martini

Objective

Establish a secure connection to Cisco ThousandEyes using an API token with only the permissions required by the integration.

Instructions in Martini

  • Create or identify a least-privilege ThousandEyes API identity
  • Store the bearer token in Martini secrets or secure environment configuration
  • Configure the REST request without exposing the token in workflow data or logs
  • Test access against the intended account, organization, and resource scope

Objective

Select push notifications, scheduled polling, or an API-led invocation based on the required freshness and the coverage of the ThousandEyes event type.

Instructions in Martini

  • Use a Martini API for supported ThousandEyes notifications
  • Use a scheduler for metrics, configuration, or alert polling
  • Document the resource-specific event coverage and polling interval
  • Define the checkpoint or correlation key before processing data

Objective

Call the appropriate versioned ThousandEyes REST resource and handle response boundaries explicitly.

Instructions in Martini

  • Retrieve Tests, Agents, Agent Clusters, Alerts, metrics, or other documented resources
  • Process pagination and bounded time windows
  • Validate response status, identifiers, and required fields
  • Persist checkpoints only after successful downstream processing

Objective

Coordinate enrichment, routing, transformation, target writes, and recovery behavior in a reusable Martini workflow.

Instructions in Martini

  • Separate notification intake from REST enrichment when appropriate
  • Apply severity, environment, ownership, and target-routing rules
  • Use reusable workflow logic for common alert and metric processing
  • Keep vendor-specific request handling separate from downstream contracts

Objective

Transform ThousandEyes JSON into a stable canonical or target-specific model.

Instructions in Martini

  • Map alert identifiers, states, severities, tests, agents, and timestamps
  • Normalize metric units and dimensions for warehouse or analytics use
  • Validate required fields before target writes
  • Preserve source identifiers for correlation and troubleshooting

Objective

Deliver normalized data to incident, messaging, CMDB, database, or analytics systems without creating duplicates.

Instructions in Martini

  • Use target APIs or documented receiving interfaces
  • Implement create-or-update behavior where a stable ThousandEyes identifier exists
  • Commit records and checkpoints in an order that supports safe replay
  • Route target failures to retryable or non-retryable handling

Common Cisco ThousandEyes data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
TestsRepresent configured network, web, DNS, HTTP, BGP, endpoint, and other monitoring tests.ServiceNow, CMDBs, data warehouses, Splunk, DatadogMartini retrieves test configuration and metadata, validates required identifiers, maps it to a canonical monitoring model, and synchronizes changes.
AgentsRepresent Cloud Agents, Enterprise Agents, Endpoint Agents, and other monitoring locations.CMDBs, data warehouses, Cisco AppDynamics, analytics platformsMartini pages through agent resources, enriches records with location and ownership data where available, and applies checkpointed upsert logic.
Agent ClustersGroup Enterprise Agents for monitoring from defined network or geographic locations.CMDBs, operational dashboards, data warehousesMartini maps cluster membership and metadata, compares it with the target representation, and records synchronization results.
AlertsRepresent alert definitions and alert state information generated when conditions exceed configured thresholds.ServiceNow, PagerDuty, Slack, Microsoft Teams, JiraMartini receives selected notifications or polls alert resources, deduplicates by stable identifiers, enriches details, and performs idempotent downstream updates.
Test metrics and dataProvide latency, loss, availability, response-time, DNS-performance, and network-path measurements.Splunk, Datadog, data warehouses, analytics platformsMartini retrieves bounded time windows, handles pagination and late measurements, transforms dimensions and values, and writes normalized measurements.
Dashboards and viewsPresent ThousandEyes monitoring information for operational analysis, subject to the resource and account configuration.Operational portals, reporting stores, analytics platformsMartini can retrieve supported view data through documented resources and expose a stable internal representation, without assuming every view is writable.

Authentication and security considerations

Bearer-token authentication

Cisco ThousandEyes API requests use bearer credentials in the Authorization header. Martini can keep the token in secure secrets or environment configuration and inject it into REST requests without storing it in workflow definitions, mappings, payloads, or logs.

Least-privilege access

Use a dedicated ThousandEyes user or service identity with only the permissions required for the target Tests, Agents, Alerts, metrics, or administrative resources. Confirm account and organization scope before production use.

Notification protection

For webhook-style notifications, validate the request and payload according to the configured ThousandEyes mechanism, add replay protection and idempotency checks, and retrieve authoritative details from the REST API when the notification is only a summary.

Operational considerations for Cisco ThousandEyes integrations

Rate limits and pagination

Confirm limits for the account, API version, and resource. Use consolidated queries where available, controlled concurrency, bounded metric windows, deterministic ordering, pagination, and exponential backoff for throttling.

Idempotency and checkpoints

Use a stable alert or event identifier when available. Store processing state and checkpoints durably so retries do not create duplicate incidents or reinsert completed metric pages.

Retention and late data

Validate retention and granularity for each metric endpoint. Record the source query window and account for delayed measurements or late-arriving alert information.

Versioning and testing

Pin workflows to a documented API version, validate required fields, and isolate vendor-specific transformations from downstream contracts. Test permissions, alert states, pagination, throttling, recovery events, and schema changes before deployment.

Failure handling

Retry transient HTTP failures, route authentication and validation failures separately, preserve replayable payloads where permitted, and avoid marking an alert processed until downstream delivery succeeds.

Why use Martini instead of scripts or point-to-point integrations?

Reusable orchestration

Martini keeps ThousandEyes authentication, API calls, notification intake, enrichment, routing, and target delivery in maintainable workflows rather than scattered scripts.

Stable contracts

Martini can transform versioned ThousandEyes JSON into normalized APIs and data models, limiting the impact of provider-specific response changes on downstream applications.

Operational control

Scheduling, checkpoints, validation, retries, idempotency, monitoring, and error handling support reliable synchronization of alerts, configuration, and metrics.

Flexible integration design

Martini can consume REST APIs, expose APIs for supported notifications, write to databases, and call downstream application interfaces without requiring a dedicated Cisco ThousandEyes connector.

Frequently asked questions

How can Cisco ThousandEyes be integrated with enterprise systems?

Cisco ThousandEyes can be integrated through its versioned REST APIs, bearer-token authentication, and webhook-style notifications for selected alert or event scenarios. REST APIs support monitoring configuration, Tests, Agents, Agent Clusters, Alerts, results, and metrics. Scheduled workflows can retrieve and synchronize data when push coverage is unavailable or insufficient.

Can Martini integrate with Cisco ThousandEyes?

Yes. Martini can consume Cisco ThousandEyes REST APIs, receive supported webhook-style notifications through a Martini API, transform ThousandEyes JSON, schedule polling workflows, and route normalized data to incident, CMDB, database, analytics, and messaging platforms.

Do I need a connector to integrate Cisco ThousandEyes with Martini?

No dedicated Cisco ThousandEyes connector is required. Martini can use Cisco ThousandEyes native REST APIs, supported webhook-style notifications, bearer-token authentication, and scheduled workflows to implement the integration.

Is there any extra Lonti cost to integrate Cisco ThousandEyes with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Cisco ThousandEyes. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Cisco ThousandEyes, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.

Which Cisco ThousandEyes integration methods should be used?

Use the documented versioned REST APIs for Tests, Agents, Agent Clusters, Alerts, results, and metrics. Use webhook-style notifications for selected alert or event scenarios when their coverage meets the requirement, and use scheduled REST polling with checkpoints for configuration or metric synchronization.

Does Cisco ThousandEyes provide webhooks, GraphQL, or SOAP APIs?

Cisco ThousandEyes supports webhook-style notifications for selected alert or event scenarios. No official Cisco ThousandEyes GraphQL or SOAP API was confirmed in the reviewed documentation, so integrations should use the documented REST APIs and supported notification mechanisms.

How does synchronization with Cisco ThousandEyes work?

Martini can run scheduled workflows that request bounded time windows or paginated resources, apply deterministic ordering, store timestamps or object identifiers as checkpoints, and write normalized results to a target. Webhook notifications can provide faster alert processing, with REST retrieval used for enrichment and authoritative details.

How are Cisco ThousandEyes data mapping, retries, and duplicate alerts handled?

Martini maps ThousandEyes fields into canonical or target-specific models, validates required identifiers, and applies business rules before writing downstream data. Workflows can retry transient failures and throttling responses, separate authentication or validation errors, preserve failed payloads for replay, and use alert or event identifiers for idempotent processing. Martini can also expose a normalized API façade for downstream consumers.

Related Martini documentation

APIs

Webhooks

Workflows

Security

Operations

Connect Cisco ThousandEyes with Martini

Use Martini to orchestrate Cisco ThousandEyes APIs and selected notifications into reliable enterprise workflows for incidents, metrics, configuration, and observability.

EXPLORE MARTINI
BOOK A DEMO