New Relic¶
By enabling this toolset, HolmesGPT will be able to pull traces and logs from New Relic for investigations.
Important: Disable Default Logging Toolset
Only one logging toolset should be enabled at a time. If you enable this toolset, disable the default kubernetes/logs
toolset.
Available Log Sources:
- Kubernetes logs - Direct pod log access (enabled by default)
- Grafana Loki - Centralized logs via Loki
- OpenSearch logs - Logs from OpenSearch/Elasticsearch
- Coralogix logs - Logs via Coralogix platform
- DataDog - Logs from DataDog
💡 Choose one: Only enable one logging toolset at a time for best performance.
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:
nr_api_key: "<your New Relic API key>"
nr_account_id: "<your New Relic account ID>"
kubernetes/logs:
enabled: false # Disable default Kubernetes logging if using New Relic for logs
After making changes to your configuration, run:
The table below describes the specific capabilities provided by this toolset. HolmesGPT can decide to invoke any of these capabilities when answering questions or investigating issues.
Capabilities¶
Tool Name | Description |
---|---|
| newrelic_get_logs
| Retrieve logs from New Relic for a specific application and time range |
| newrelic_get_traces
| Retrieve traces from New Relic based on duration threshold or specific trace ID |
For more information, see the New Relic API documentation.