home

AppDynamics SaaS

Splunk Observability CloudSplunk IT Service IntelligenceSplunk Cloud PlatformSplunk EnterpriseData ManagementSplunk Enterprise Security 8Splunk Enterprise Security 7Splunk SOARSecurity OfferingsAppDynamics SaaSAppDynamics On-PremisesAppDynamics SAP AgentRelease Notes and UpdatesSupported Add-onsSplunk Style Guide
search
search
Splunk Observability CloudSplunk IT Service IntelligenceSplunk Cloud PlatformSplunk EnterpriseData ManagementSplunk Enterprise Security 8Splunk Enterprise Security 7Splunk SOARSecurity OfferingsAppDynamics SaaSAppDynamics On-PremisesAppDynamics SAP AgentRelease Notes and UpdatesSupported Add-onsSplunk Style Guide

search

AppDynamics SaaS

AppDynamics SaaS Contents

close
  • はじめに

  • Release Notes and References

  • Application Performance Monitoring

  • Observability for AI

  • Database Visibility

  • Infrastructure Visibility

  • Analytics

  • Agent Management

  • Tag Management

  • Application Security Monitoring

  • Unified Observability Experience with the Splunk Platform

  • expand_more

    End User Monitoring

    • expand_more

      26.1.0

      • expand_more

        エンド ユーザ モニタリング データ

        • Browser Monitoring

  • Extend Splunk AppDynamics

  • Licensing

  • Accounts

  • Product Announcements and Alerts

  • PDFs

  • Glossary

  • Translated Documentation

  1. AppDynamics SaaS (26.1.0)
  2. arrow_right
  3. End User Monitoring
  4. arrow_right
  5. エンド ユーザ モニタリング データ
  6. arrow_right
  7. Browser Monitoring
  8. arrow_right
  9. Browser Real User Monitoring
  10. arrow_right
  11. JavaScript エージェントの構成

list_altShow Contents

chevron_left

AppDynamics SaaS

JavaScript エージェントの構成

chevron_right

Set the Exact Current Domain in the JavaScript Agent Cookie

This page describes how to set the current domain in the JavaScript Agent cookie.

The JavaScript Agent itself writes a session cookie to the page, for timing purposes. This cookie is set when the user clicks a link and the unload event is fired. By default, the cookie is set to the broadest possible version of the originating domain (such as, *.domain.com) to increase the likelihood that the next page opened in the same domain can access that cookie. See Cookies and Browser Monitoring Data.

In some cases, however, it may be necessary to limit the cookie to the full exact domain name. To do this, add a flag in the "adrum-start-time" script to the header of each page right after the <head> tag and before the entry that includes the location of the agent (adrum.js). The flag should read: window["adrum-use-strict-domain-cookies"] = true.

After you include the start-time line, the strict domain flag, and the agent, the <head> section in your monitored web pages should look something like this:

<head>
<script type='text/javascript' charset='UTF-8'>>
window["adrum-start-time"] = new Date().getTime();
window["adrum-use-strict-domain-cookies"] = true;
</script>
<script src='//cdn.appdynamics.com/adrum/adrum-latest.js' type='text/javascript' charset='UTF-8'></script>
...
</head>

Last updated: 2026年1月7日

chevron_leftchevron_right

Explore Topics

Splunk Observability Cloud

Splunk IT Service Intelligence

Splunk Cloud Platform

Splunk Enterprise

Data Management

Splunk Enterprise Security 8

Splunk Enterprise Security 7

Splunk SOAR

Security Offerings

AppDynamics SaaS

AppDynamics On-Premises

AppDynamics SAP Agent

Release Notes and Updates

Supported Add-ons

Splunk Style Guide

logo

Legal

Privacy

Website

Terms of Use

©2005-2025 Splunk Inc. All rights reserved.