> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/integration-guides/splunk-synthetic-monitoring-integration.md).

# Splunk Synthetic Monitoring Integration

## Overview

The Splunk Synthetic Monitoring Integration brings ThousandEyes network and web measurements into Splunk. Site reliability engineering (SRE), DevOps, and network operations teams can compare these signals with application results to troubleshoot issues.

This page summarizes the integration’s capabilities and use cases.

## Capabilities

* Create, view, manage, and import ThousandEyes HTTP Server tests from Splunk.
* View application results alongside ThousandEyes network signals.
* Use application and network data in Splunk detectors and dashboards.
* Open ThousandEyes to investigate network issues in more detail.

## Use Cases

* Identify whether a test failure involves the application, the HTTP server being tested, DNS resolution, or the underlying network.
* Check whether packet loss, latency, or routing changes contribute to a poor user experience.
* Compare backend and network signals to reduce handoffs between SRE and network teams.
* Share ThousandEyes path or alert details with network teams for deeper investigation.

## Supported Scope

At launch, you can use the integration with ThousandEyes HTTP Server tests. Additional test types, such as page load, transaction, and API tests, will become available in future releases. You can also combine ThousandEyes network metrics with browser and mobile application data through Splunk Real User Monitoring (RUM). For more information, refer to [Integrate Splunk RUM with Cisco ThousandEyes](https://help.splunk.com/en/splunk-observability-cloud/digital-experience-monitoring/real-user-monitoring/splunk-rum-and-cisco-thousandeyes-integration).

## Network Path Detail

Splunk groups a network path into segments to provide a concise overview and help you locate the part of the path that may be causing a problem. For full hop-by-hop and node details, open the test in ThousandEyes and use [Path Visualization](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/path-visualization/).

## Requirements

Before you connect Splunk to ThousandEyes, confirm these requirements:

| Requirement                              | Details                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ThousandEyes account                     | Use an active ThousandEyes account.                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| ThousandEyes API key                     | Use an organization-owned [API key](https://docs.thousandeyes.com/product-documentation/user-management/authorization/api-keys) for this production integration. Give it the *View tests* and *Edit tests and run instant tests* permissions for each account group so Splunk can import, create, and manage tests. See [Built-In Roles and Permissions](https://docs.thousandeyes.com/product-documentation/user-management/authorization/rb-access-control/built-in-roles-and-permissions). |
| API key rotation                         | API keys expire after 180 days. Before the key expires, [regenerate it](https://docs.thousandeyes.com/product-documentation/user-management/authorization/api-keys#managing-expiration) and update the Splunk integration with the new key so it can continue to authenticate.                                                                                                                                                                                                                |
| Account groups                           | Each Splunk organization can have only one ThousandEyes integration configuration, which can include up to 35 account groups. Splunk can use tests only from the selected account groups. Make sure the API key can access each selected group.                                                                                                                                                                                                                                               |
| ThousandEyes units                       | Make sure the relevant account groups have enough available units to create and run tests. If an applicable quota is reached, ThousandEyes can prevent new scheduled tests. For details, see [Setting Quotas](https://docs.thousandeyes.com/product-documentation/user-management/usage-and-billing/setting-quotas).                                                                                                                                                                          |
| Splunk Synthetic Monitoring subscription | Your Splunk Observability Cloud subscription must include Splunk Synthetic Monitoring. See the [Splunk Observability Cloud service description](https://help.splunk.com/en/splunk-observability-cloud/get-started/service-description/splunk-observability-cloud-service-description) for subscription details.                                                                                                                                                                               |
| Splunk access                            | A Splunk admin must set up the integration. The admin also needs permission to use Synthetic Monitoring.                                                                                                                                                                                                                                                                                                                                                                                      |

## Learn More

* For an overview and setup instructions, refer to [Integrate Splunk Synthetics with Cisco ThousandEyes](https://help.splunk.com/en/splunk-observability-cloud/digital-experience-monitoring/synthetic-monitoring/integrate-splunk-synthetics-with-cisco-thousandeyes).

## Related Content

* [Cisco ThousandEyes App for Splunk](https://docs.thousandeyes.com/product-documentation/integration-guides/custom-built-integrations/splunk-app) collects and displays ThousandEyes data in Splunk; it does not cover managing HTTP Server tests from Splunk.
* [Splunk Observability Cloud with OpenTelemetry](https://docs.thousandeyes.com/product-documentation/integration-guides/opentelemetry/observability-platforms/splunk-observability-cloud) sends ThousandEyes telemetry to Splunk Observability Cloud; it does not cover managing HTTP Server tests from Splunk.
