New Relic Synthetics released support to establish non http connection from public locations. We’ve added a set of additional libraries to our runtime allowing scripted monitors to connect using FTP, SFTP, LDAP, TCP, and SMTP. This allows New Relic Synthetics users to create scripted browser and scripted API monitors to establish connections using these non-http connection types.
Expanding the reach of your Synthetics monitors
The world of Synthetics monitoring needs have expanded beyond the current website and endpoint monitoring model. This allows customers who have complex technical architecture that cross multiple applications and endpoints to proactively monitor their transaction using Synthetics. Combine this with the scripting capabilities that Synthetics offers, this unlocks the ability to monitor transactions that span multiple hops.
How do I use it?
The new libraries are now available across all public locations, to access you’ll need to refer to the library within a scripted browser (using the script editor). More details on the libraries and capabilities can be found on our docs site (under runtime v0.6x).
If your monitor is using a previous version of the runtime, or your private location (CPM) is outdated, you’ll need to update both to the latest version to take advantage of this capability.
Frequently asked questions
How do I learn more about the libraries and their capabilities?
Each library is listed on the New Relic docs site and has a link to the repo where you can learn more about. Here’s a link to our docs site with the libraries.
Can I use these libraries on New Relic public locations?
Yes, with this update all libraries are available to leverage from all of the New Relic Synthetics public locations.
Are there any templates for how to use these libraries in a scripted monitor?
Yes, New Relics own, Brian Peck, has posted some great example scripts that use these libraries. Check out Brian’s post