Configuring custom New Relic Synthetics monitors for Adobe Experience Manager URLs

This article explains how to configure and validate custom New Relic Synthetics monitors to proactively check the availability of critical URLs delivered through Adobe Experience Manager (AEM) and associated CDNs.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • Adobe-managed New Relic access through Cloud Manager, or a customer-owned New Relic account
  • Custom monitoring for production URLs, when the environment and support entitlement qualify

Issue/Symptoms

  • You need to monitor important AEM-published pages, CDN delivery, or third-party endpoints for availability.
  • You need to confirm that AEM and integrated services are reachable from the monitoring locations.
  • You encounter an account or entitlement limit, or a monitor reports that a URL is invalid or unreachable.

Cause

The available monitoring options depend on who owns the New Relic account. The Adobe-managed New Relic account provides read-only APM and doesn’t allow customers to create Synthetic monitors. Adobe-managed Custom Monitoring is a separate, entitlement-based service for eligible production environments. If you use your own New Relic account, monitor features and limits depend on that account and plan.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Decide whether you will use Adobe-managed Custom Monitoring or a customer-owned New Relic account.

  2. To request Adobe-managed Custom Monitoring, confirm that your environment is a production environment and that your organization has Advanced Cloud Support. Provide Adobe with the public URLs you want monitored before go-live. Note: Adobe-managed Custom Monitoring supports up to five distinct production URLs. Each URL must be valid and return HTTP 200. Adobe configures this service; you don’t create these monitors in the Adobe-managed New Relic account.

  3. If you use your own New Relic account, identify the important public URLs to monitor, such as:

    • https://brand.example.com
    • https://service.example.com
    • https://brand.example.com/forms/contact
    • https://api.partner.com
  4. Sign in to your customer-owned New Relic account with permission to manage Synthetic monitors. For each URL:

    • Open Synthetic monitoring and select Create a monitor.
    • Select the Ping monitor type if it is available in your account and appropriate for the check.
    • Enter the target URL and set the monitoring frequency and locations supported by your account.

    Note: New Relic monitor types and quotas depend on your account and plan. The five-URL allowance described above applies to Adobe-managed Custom Monitoring, not to every customer-owned New Relic account.

  5. Save and activate each monitor. Repeat for the URLs you need to monitor, within the applicable Adobe entitlement or New Relic account limit.

  6. Verify that each monitor is active and checking the intended endpoint. Review its status and results in New Relic.

  7. If a URL is reported as invalid or unreachable:

    • Check the URL for typos and access restrictions.
    • Confirm that the endpoint is publicly reachable from the selected monitoring locations.
    • Work with your internal network team or third-party provider to resolve access issues.
  8. If you reach the applicable URL or account limit, prioritize the most important endpoints. For customer-owned New Relic, remove or rotate monitors according to your account’s limit. For Adobe-managed Custom Monitoring, contact your Adobe account team to request changes to the monitored URL list.

  9. Document the monitored URLs and their status. For customer-owned New Relic monitors, share a summary or screenshot with stakeholders. For Adobe-managed Custom Monitoring, retain the request confirmation.

  10. Review the monitored URLs periodically and update them when your business or service endpoints change.

recommendation-more-help
experience-cloud-kcs-help-kbarticles