New Relic¶
By enabling this toolset, HolmesGPT will be able to pull traces and logs from New Relic for investigations.
Prerequisites¶
- A New Relic API Key with necessary permissions to access traces and logs
- Your New Relic Account ID
You can find these in your New Relic account under Administration > API keys and Account settings.
Configuration¶
Add the following to ~/.holmes/config.yaml. Create the file if it doesn't exist:
toolsets:
newrelic:
enabled: true
config:
api_key: "<your New Relic API key>"
account_id: "<your New Relic account ID>"
is_eu_datacenter: false # Set to true if using New Relic EU region
enable_multi_account: false # Optional: set to true to query across multiple accounts
After making changes to your configuration, run:
Capabilities¶
| Tool Name | Description |
|---|---|
| newrelic_execute_nrql_query | Execute NRQL queries for Traces, APM, Spans, Logs and more |
Multi-Account Mode¶
If your organization has multiple New Relic accounts, setting enable_multi_account: true lets Holmes query across all of them.
Your API key must have access to all the accounts you want Holmes to query. Without the required permissions, Holmes won't be able to retrieve data from those accounts.
The account_id in your config is used as the default when no specific account is specified.
How it Works¶
You don't need to know NRQL to use this toolset. Holmes will automatically construct and execute NRQL queries based on your investigation needs.
For example, when investigating application logs, Holmes might execute a query like:
To learn more about NRQL syntax, see the New Relic Query Language documentation.