Http user agent database8/31/2023 ![]() ![]() In HTTP this string is included in the header field User-Agent. An integration identifies itself by submitting a standard identification string. When writing applications to work with New Relic's RESTful APIs (referred to as an integration in this document), you are creating an HTTP agent to manage information exchange between your application and New Relic. Offering an "as a service" integration between your product and New Relic, without actually distributing your integration code, like Runscope's integration.Packaging your integration into a plugin, extension, or other package, and distributing it via a directory like WordPress Plugins.Publicizing your integration code on Github.This document assumes you plan to publicly distribute an integration that makes use of any of New Relic's public RESTful APIs. If you are only using your integration internally, and don't plan on sharing it with anyone outside your organization, you don't need to set a unique custom agent string. To ensure that New Relic correctly identifies API integration publishers, each integration needs a unique custom user agent string.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |