Getting SupportΒΆ

Ask for help, or just say hi!

Slack
Github Issue

Commercial SupportΒΆ

Contact support@robusta.dev for details.

Common ErrorsΒΆ

This list contains some common errors we have encountered over time. If you can't find your answer here, contact support@robusta.dev or go to our slack channel.

command not found: robusta (CLI not in path)
  1. Determine where the Robusta-cli binary file is located

find / -regex '.*/bin/robusta' 2>/dev/null
  1. Add the path you found (e.g /opt/homebrew/bin/) to your PATH. To do so, find your shell config file ( ~/.profile or ~/.bash_profile or ~/.zshrc etc...) and append the following:

export PATH="$PATH:<new-path>"
  1. Reopen the terminal or run:

source <your-shell-config-file>

Alternative Solution

Instead of modifying PATH, run Robusta commands via the python3 binary: python3 -m robusta.cli.main gen-config

SSL certificate errors on Mac OS

This implies a python package with certificates is missing on your system.

To fix it, run /Applications/Python 3.9/Install Certificates.command

For more info see: https://stackoverflow.com/questions/52805115/certificate-verify-failed-unable-to-get-local-issuer-certificate

unknown field in com.coreos.monitoring.v1.Prometheus.spec, ValidationError(Prometheus.spec)

This indicates potential discrepancies between the version of Prometheus you are trying to use and the version of the CRDs in your cluster.

Follow this guide for upgrading CRDs from an older version.

robusta-runner isn't working or has exceptions

Check the pod's memory consumption. If necessary, increase the memory request in the Helm values:

runner:
  resources:
    requests:
      memory: 2048Mi
    limits:
      memory: 2048Mi

Here's a representative error caused by too little memory:

Discovery Error
2023-04-17 23:37:43.019 ERROR    Discovery process internal error
2023-04-17 23:37:43.022 INFO     Initialized new discovery pool
2023-04-17 23:37:43.022 ERROR    Failed to run publish discovery for robusta_ui_sink
Traceback (most recent call last):
  File "/app/src/robusta/core/sinks/robusta/robusta_sink.py", line 175, in __discover_resources
    results: DiscoveryResults = Discovery.discover_resources()
  File "/app/src/robusta/core/discovery/discovery.py", line 288, in discover_resources
    raise e
  File "/app/src/robusta/core/discovery/discovery.py", line 280, in discover_resources
    return future.result()
  File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 446, in result
    return self.__get_result()
  File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.
AlertManager Silences are Disappearing

This happens when AlertManager does not have persistent storage enabled.

When using Robusta's embedded Prometheus Stack, persistent storage is enabled by default.

For other Prometheus distributions set the following Helm value (or it's equivalent):

# this is the setting in in kube-prometheus-stack
# the exact setting will differ for other Prometheus distributions
alertmanager:
  alertmanagerSpec:
    storage:
      volumeClaimTemplate:
        spec:
          accessModes: ["ReadWriteOnce"]
          resources:
            requests:
              storage: 10Gi

ContributingΒΆ

More TutorialsΒΆ

Here are more tutorials from the Robusta community: