When integrating a new language binding, collector, or third-party service with AppOptics we recommend setting a User Agent header on each API request that identifies your integration. A custom User Agent allows us to identify those requests made on-behalf of your integration and/or originating from your third-party service.
Setting a custom User Agent has the following benefits:
- We can track usage statistics for each collector. This let's us know which service integration we should focus our collaborative efforts on or where we can help improve the collector ecosystem.
- We can better assist customers that have problems using the service by identifying which services they are using and directing them appropriately.
- We can identify customers that are using know buggy or vulnerable service integrations and assist them in updating.
A custom User Agent can be sent on any request to the AppOptics API by setting the HTTP header "User-Agent". For example, in curl you would set the header with the -H flag:
curl -H 'User-Agent: my-integration/1.2.3'
The full format for a User Agent header is explained in this Wikipedia article, but a simple User Agent should follow the format:
For example, if you were integrating the service "BrowserMetrics.io", and the current version of your integration library is "4.5.9", the User Agent header should look like:
A User Agent can also include additional meta-data that identifies the particular request. This data is specified as a semi-colon separated string, included in parenthesis spaced after the User Agent string.
For example, if a service could be accessed from different devices (e.g. an iPad) and from different locales, an example User Agent would be:
BrowserMetrics.io/4.5.9 (iPad; en-us)
A single User Agent header can include multiple agents separated by spaces. If a service integration is built upon an existing client library it is beneficial to include these library names and versions as well. Different client library versions may behave differently, so it is imperative to know which ones were used in the integration.
For example, the AppOptics AppOptics-metrics Ruby gem uses the following User Agent that identifies the name of the HTTP client library (faraday) and its version:
AppOptics-metrics/1.0.2 (ruby; 1.8.7p358; x86_64-linux) direct-faraday/0.8.4
When the APM Integrated Experience is enabled, AppOptics shares a common navigation and settings with the other integrated experiences' products. How you navigate AppOptics and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.