Skip to content

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.

HolmesGPT provides several out-of-the-box alternatives for log access. You can select from these options:

Prerequisites

  1. A Coralogix API key which is assigned the DataQuerying permission preset
  2. A Coralogix domain. For example eu2.coralogix.com
  3. 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:

toolsets:
  coralogix/logs:
    enabled: true
    config:
      api_key: "<your coralogix API key>"
      domain: "eu2.coralogix.com"
      team_hostname: "your-company-name"

  kubernetes/logs:
    enabled: false  # Disable default Kubernetes logging
holmes:
  toolsets:
    coralogix/logs:
      enabled: true
      config:
        api_key: "<your coralogix API key>"
        domain: "eu2.coralogix.com"
        team_hostname: "your-company-name"

    kubernetes/logs:
      enabled: false  # Disable default Kubernetes logging

Update your Helm values and run a Helm upgrade:

helm upgrade robusta robusta/robusta --values=generated_values.yaml --set clusterName=<YOUR_CLUSTER_NAME>

Capabilities

Tool Name Description
coralogix_fetch_logs Fetch logs from Coralogix for specified pods and time ranges