|
Key Takeaways
|
|
With application synthetic monitoring capabilities, DX Operational Observability (DX O2) can monitor websites and other services by probing the target from various globally distributed monitoring stations. These capabilities, which support SaaS and on-premises deployments, help teams shift from reactive to proactive management, elevate user experience for monitoring, and raise observability to a new level.
Previously, with DX Application Performance Manager and DX Operational Intelligence, integrating ASM metrics was achieved through an extension of the Application Performance Management Infrastructure Agent (APMIA).
Now, with DX O2, the integration can be done natively through the product’s user interface. The Preferences menu appears in the top-right menu, under the logged in user name.
Only two variables are needed: Ingestion URL and Agent Token. To get these variables, log into the DX O2 that you want to enable for synthetics.
1. The NASS endpoint URL (Ingestion URL). You will find this value in DX O2 under "Settings" => Access Tokens/Security => Connector Parameters".
In the Connection Parameters section, the NASS URL is identified as the Ingestion URL.
2. The Agent Token (authentication and identification). To create the Agent Token required by DX O2, go to "Settings" => Access Tokens/Security => Agent Tokens". Paste this into the "Tenant Agent Token" field in the DX ASM preferences configuration.
After you enter and save the configured setting, you will see the "Synthetic" root entry displayed in the Metric Tree. This may take a few minutes.
Operators will now be able to configure alerts and trigger levels as they do for regular applications in DX O2.
Operators can also create dashboards to show the current operations of the Synthetic Monitor. Dashboards for synthetics can display metrics such as Connection Time (ms), DNS Resolution Time (ms), Download Size (bytes), Download Time (ms), Duration (ms), Performance Bad, Performance Good, Probes, and more.
To help operators get started, DX O2 includes pre-built dashboards that include these metrics. See a sample dashboard and its description below.
In conclusion, integrating synthetics with DX O2 provides the ability to monitor both the user experience and the application’s health in a more comprehensive and effective manner. This combination enables proactive identification of issues so they may be resolved before they affect production. Ultimately, this leads to enhanced application reliability and better user experiences.
The sample dashboard below includes all reported synthetic metrics. The dashboard includes:
- Current reported request times compared to configured targets.
- Current availability of configured monitors, displayed as heat maps.
- Information on reported monitoring metrics, displayed as graphs.
- Monitoring filter(s) applied, displayed in the top row.
Note: For SaaS customers, contact support for assistance to enable native synthetics integration for your tenant.
For additional details, visit the Frequently Asked Questions page here.
Jörg Mertin
Jörg Mertin, a Master Solution Engineer on the AIOps and Observability team, is a self-learner and technology enthusiast. A testament to this is his early adopter work to learn and evangelize Linux in the early 1990s. Whether addressing coordinating monitoring approaches for full-fledged cloud deployments or a...
Other Resources You might be interested In
Handling Incomplete User Stories at the End of an Iteration
When a team reaches the end of an iteration, some user stories may not be completed. This post details causes and options for managing these scenarios.
What’s Hiding in Your Wiring Closets?
See why you must move from periodic audits to a state of perpetual awareness. Track every change, validate it against policy, and understand its impact.
All Network Monitoring Tools Are Created Equal, Right?
See how observability platforms provide a unified view across multi-vendor environments and correlate network configuration changes with performance issues.
Scale Observability, Streamline Operations with AppNeta Monitoring Policies
This post reveals how, with AppNeta’s monitoring policies, you can leverage a powerful framework for scalable, flexible, and accurate network observability.
AppNeta: Current Network Violation Map Dashboard
Learn how to configure and use the Current Network Violation Map dashboard in AppNeta to identify geographic regions impacted by WAN performance issues.
AppNeta On-Prem: Minimize Unplanned Downtime
Learn how to configure the AppNeta On-Prem environment following best practices for high availability and disaster recovery to maintain service continuity and minimize unplanned downtime.
Rally Office Hours: August 7, 2025
Get tips on how to use the Capacity Planning feature in Rally, then follow the weekly Q&A session with Rally product experts.
dSeries Version 25.0 Boosts Insights, Security, and Operational Efficiency
Discover how ESP dSeries Workload Automation 25.0 represents a significant leap forward, making workload automation more secure, visible, and efficient.
What Your SD-WAN Isn't Telling You
SD-WAN's limited view blinds it to underlay issues. Augment SD-WAN with end-to-end visibility to validate decisions and diagnose root causes for network resilience.