Read the following FAQs to learn more about CA ASM.
Read the following FAQs to learn more about CA ASM.
Should I have all my stations in the same country/region?
You should have every station in the country where it is really located. Otherwise, we'll report inaccurate data in reports or charts (for example, when grouping by continent, on PSPs).
Within the country, you can create a new location (for example, city) for every station or you can put all your stations in one location.
The first option is good if you want to control if this particular monitor will be run on this station and not on the other.
The second way is good for improving the performance of a station. If your station is not performing well you just add another station to the same location and do not have to reconfigure your monitors. Our system will automatically load balance the load among the stations in the location.
Can I get an alert if a station is down?
During the installation, you are asked if you want the station monitored. This will monitor services on the station and send an email (from the station) in case some error occurs, but it is self-monitoring with the drawback that it cannot inform you if the station fails completely. For such cases, you can create a simple HTTPS monitor from any public station that will monitor this URL
where XXX is the client tunnel CID you can find on your OPMS in /etc/asm/optunnel.yaml. Do not publish the client tunnel CID anywhere, for example, do not place such monitors in public folders. In the future, we plan to automatically monitor OPMS.https://assetproxy.asm.ca.com/ oppop/XXX/localhost/api/ status/system
Can you save six months of logs?
We save the check results and metrics for 2 years. However, the details of the checks (jtl files, har files, videos of the webdriver sessions etc.) are available for 14 days only to save space on the local disk on the stations. If you have a huge disk on your on-premise station you can change the retention period of the assets by changing keep-jobs in /etc/asm/smartpop.yaml and restarting the API.
Why are checkpoints not working as expected?
It can have many reasons. First of all you should check if all the services on your system are up and running by calling "monit summary". All services should report OK. If not, try to restart the failing service, for example, "monit restart api". If everything is running, try to test the station from DX APM web - go to On-Premise / Stations and select the station. First, use the localhost as a URL and if it works try any service that is accessible from the station.
Can I remove bad data to improve my past SLAs?
Unfortunately not. We provide a monitoring system which reports what it finds. To save and retrieve such a huge amount of data efficiently our storage is optimized for adding new entries but not for updating or deleting. Any update or delete is very inefficient and generates new data (yes, even delete means adding new data!). The result is then suboptimal for fast access and slows down all queries. Additionally, we generate reports from that data and send them via email. Such reports cannot be modified retrospectively and could report different data than charts in UI display. That's why we do not support the backward modification of monitoring logs. In very rare situations within 24 hours from the event we can mark some error checks as maintenance checks (sometimes customers forget to create a maintenance window) but this must always be done manually and we try to reduce such requests to a minimum.
My response looks different across stations. Why is this?
The stations are real stations around the globe and the conditions are unique at each station. The internet connection in some countries or cities may be poor or there can be some weak point on the road. The internet routes often do not follow the closest distance or real routes and even if the servers are geographically close internet distance may be much longer (for example, different ISPs can route all traffic through their central routers in other countries). Some countries have specific conditions (for example, China aggressively controlling and filtering web traffic). You should also keep in mind that the speed of light can be a limiting factor in some cases. If you monitor your US stations for example, from India, the direct (shortest) distance between India and U.S.A. maybe (it depends on the cities) approx. 12500 km (over Russia and the north pole - not respecting internet cable infrastructure). Since even the light travels this distance 12500/300000 s = 42 ms, you cannot expect the ping response to arrive in less than 2*42 ms = 84 ms.
Some services use CDNs and the hostnames are resolved and the request directed to different servers based on your geographical locations (for example, facebook, google, amazon, and so on). The result can also be affected by the current date-time in both the monitoring station or the monitored service location (for example, overloaded internet when the working hours start), accidents (service disruptions).
Thus, the monitoring represents "real life" tests and it is often very hard to hunt milliseconds and can be misleading to compare the results from different stations, different or even the same time.
DX APP Synthetic Monitorwork with local monitoring software?
DX APP Synthetic Monitorworks with local monitoring software by using an OPMS.
How long are root cause analysis details available?
Error logs of root cause analysis details are available for seven days.
Do local internet problems affect monitoring?
Local internet problems do not cause interruptions in monitoring. Monitoring is performed from a network of servers that are located outside your local internet network.
How can I select a monitor station by IP address?
Follow these steps:
- SelectProducts, then selectMonitoring Stations.
- Note the name of the Monitoring Station with the IP address you want to use.
- SelectMonitoring,Monitors,New Monitor.
- SelectMore Options, and then selectCheckpoint Selection.
- SelectClearto clear all monitors.
- Select the monitoring station with the IP address that you want to use. Enter the other required fields and selectSave.A monitor is created with the IP address.
DX APP Synthetic Monitorplan is best for me?
To view available plans, log in to
DX APP Synthetic Monitorand select
Plans. To select the package right for you, consider the following questions:
- Which services or protocols (http, https, SMTP, ftp, and so on) do you want to monitor?
- How many sites or aspects of the sites do you want to monitor?
- How often do you want checks?
- How many contacts for alerts and reports do you want?
- Do you want to monitor systems behind a firewall or do tailored checks?
- How long do you want log files to remain?
- Do you need phone support?
Why are Real Browser Monitors (RBM) more expensive than other types of monitors?
RBMs cost more because they are more expensive to operate. For example, RBMs run Firefox which uses more CPU capacity and memory than other monitors.
Scripts can be recorded with the Script Recorder. RBMs allow screenshots (added in the tools window of the Script Recorder).
How can I receive SMS or text messaging functionality?
SMS or text messaging is not included in the free package. To enable this functionality, subscribe to the
How can I access test results?
Log in, mouseover
Reports, select a report. Reports let you do the following actions:
- See all monitor performance charts.
- ViewCurrent Statusof all monitors.
- View monitor performance with graphs.
- View all your monitors.
- BrowseLog Files.