Coralogix logs¶
By enabling this toolset, HolmesGPT will fetch pod logs from Coralogix.
You should enable this toolset to replace the default Kubernetes logs toolset if all your kubernetes pod logs are consolidated inside Coralogix. It will make it easier for HolmesGPT to fetch incident logs, including the ability to precisely consult past logs.
Logging Toolsets
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 Coralogix API key which is assigned the
DataQuerying
permission preset - A Coralogix domain. For example
eu2.coralogix.com
- Your team's name or hostname. For example
your-company-name
You can deduct the domain
and team_hostname
configuration fields by looking at the URL you use to access the Coralogix UI.
For example if you access coralogix at https://my-team.app.eu2.coralogix.com/
then the team_hostname
is my-team
and the coralogix domain
is eu2.coralogix.com
.
Configuration¶
Add the following to ~/.holmes/config.yaml, creating the file if it doesn't exist:
Capabilities¶
Tool Name | Description |
---|---|
coralogix_fetch_logs | Fetch logs from Coralogix for specified pods and time ranges |