Promptwatch Logo

NewRelic Minions

New Relic Synthetic monitoring infrastructure that performs API checks and virtual browser instances to monitor websites and applications from global locations
Monitoring

What is NewRelic Minions?

NewRelic Minions is the label used here for New Relic Synthetic monitoring traffic. A customer schedules a check for a site, application, or API, and New Relic runs it from a public monitoring location or a private location managed by that customer. The results return to the customer's monitoring account.

A simple ping monitor uses an HTTP client to see whether an application is online and does not execute JavaScript. Simple browser checks open Chrome or Firefox. Scripted browser monitors can navigate a chosen user journey, while API tests send scripted calls to endpoints. Logs can therefore show anything from one repeated URL to a browser session with many assets.

There is no stable NewRelic Minions user-agent token. New Relic says its ping monitor presents as Google Chrome, and browser identities can be customized. Synthetic requests instead include X-Abuse-Info, which names the New Relic account and monitor ID. Public-location address data and customer-defined headers can add context for expected traffic.

These checks measure availability and application behavior. New Relic does not document an AI search or model-training use for them. Blocking a monitor can produce a false failure or remove coverage of a tested journey, but it does not control AI discovery of the site.

Not relevant for AI search

Is NewRelic Minions relevant for AI search?

No. NewRelic Minions is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

NewRelic Minions runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle NewRelic Minions

Read X-Abuse-Info first. If you can access the named account, inspect or disable the monitor in New Relic. For owned checks, add a custom header and keep public-location firewall rules synchronized with New Relic's current address data. Scripted private flows should still use normal application credentials.

A robots.txt snippet is omitted because New Relic publishes no stable product token for Synthetics. Ping and browser checks may identify as Chrome, and no robots compliance statement appears in the operator documentation. If an unwanted monitor cannot be disabled, record its account and monitor IDs before applying an edge or application block.

Examples

  • A ping monitor repeatedly requests `/status` with a Chrome user agent. The `X-Abuse-Info` value lets the owner trace the request to the exact monitor and disable an obsolete check.
  • A scripted browser signs in and verifies a dashboard from two public locations. The application recognizes the owned run by a custom header while still requiring the test account's credentials.

Frequently asked questions about NewRelic Minions

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Browser and scripted browser monitors run a real browser, so the selected page or journey can request scripts, images, styles, and API calls. A ping monitor is much simpler.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard