Troubleshoot Cisco ThousandEyes and RUM integration

Answers to commonly asked support questions about the Cisco ThousandEyes integration with RUM.

When you set up the Cisco ThousandEyes integration and don't see your data in Splunk Real User Monitoring (RUM), follow these troubleshooting steps.

Tokens don't work during integration setup

If the ThousandEyes bearer token is invalid, then most of the integration actions will not work as expected. Use a valid ThousandEyes token, which can be found in your profile in Cisco ThousandEyes. Copy the OAuth bearer token and input this token during integration setup.

Tests not appearing in map view

When your tests are not appearing, check for the following issues:
  • Tests don't match the provided application names
  • Alerts are not in the specified time range
  • Tests don't cover the specified domains/location
Follow these steps to address these issues:
  • Verify app names match the matchedTestsMap
  • Check ThousandEyes platform for active tests
  • Expand time range or check test coverage

Tests don't appear as matched

Check for the following issues exist if your tests don't match:

  • Does the RUM app have the correct domain configured?

  • Does the TE test URL/server/domain have the exact same domain string? For example, www.example.com ≠ example.com

  • Is the domain lowercase? Domains are case sensitive.

How do I reduce my MMS/IMM use?

You can calculate your projected metrics by multiplying the number of agents by the metrics per test type.

The number of agents is determined by the number of agents running the test. The same location can appear multiple times if multiple agents are there.

For example, a http-server test running on 5 agents can be calculated as follows: 5 agents × 3 metrics = 15 projected metrics.

The metric per test type depends on the type of ThousandEyes test:

Test type Metrics per agent
http-server 3 3
agent-to-server 3
web-transactions 3
page-load 3
dns-server 3
dns-trace 3
Unknown/Other 2 (default)