LogoLogo
Log in|Playground
  • Welcome
    • Introduction
    • FAQ
  • Capabilities
    • Log Management
    • Infrastructure Monitoring
    • Application Performance Monitoring (APM)
      • Application Metrics
      • Traces
      • Supported Technologies
    • Real User Monitoring (RUM)
  • Getting Started
    • Requirements
      • Kubernetes requirements
      • Kernel requirements for eBPF sensor
      • CPU architectures
      • ClickHouse resources
    • Installation & updating
    • Connect Linux hosts
    • Connect RUM
    • 5 quick steps to get you started
  • Use groundcover
    • Monitors
      • Create a new Monitor
      • Issues page
      • Monitor List page
      • Silences page
      • Monitor Catalog page
      • Monitor YAML structure
      • Embedded Grafana Alerts
        • Create a Grafana alert
    • Dashboards
      • Create a dashboard
      • Embedded Grafana Dashboards
        • Create a Grafana dashboard
        • Build alerts & dashboards with Grafana Terraform provider
        • Using groundcover datasources in a Self-hosted Grafana
    • Insights
    • Explore & Monitors query builder
    • Workflows
      • Create a new Workflow
      • Workflow Examples
      • Alert Structure
    • Search & Filter
    • Issues
    • Role-Based Access Control (RBAC)
    • Service Accounts
    • API Keys
    • Log Patterns
    • Drilldown
    • Scraping custom metrics
      • Operator based metrics
      • kube-state-metrics
      • cadvisor metrics
    • Backup & Restore Metrics
    • Metrics & Labels
    • Add custom environment labels
    • Configuring Pipelines
      • Writing Remap Transforms
      • Logs Pipeline Examples
      • Traces Pipeline Examples
      • Logs to Events Pipeline Examples
      • Logs/Traces Sensitive Data Obfuscation
      • Sensitive Data Obfuscation using OTTL
      • Log Filtering using OTTL
    • Querying your groundcover data
      • Query your logs
        • Example queries
        • Logs alerting
      • Query your metrics
      • Querying you data using an API
      • Using KEDA autoscaler with groundcover
  • Log Parsing with OpenTelemetry Pipelines
  • Log and Trace Correlation
  • RUM
  • Customization
    • Customize deployment
      • Agents in host network mode
      • API Key Secret
      • Argo CD
      • On-premise deployment
      • Quay.io registry
      • Configuring sensor deployment coverage
      • Enabling SSL Tracing in Java Applications
    • Customize usage
      • Filtering Kubernetes entities
      • Custom data retention
      • Sensitive data obfuscation
      • Custom storage
      • Custom logs collection
      • Custom labels and annotations
        • Enrich logs and traces with pod labels & annotations
        • Enrich metrics with node labels
      • Disable tracing for specific protocols
      • Tuning resources
      • Controlling the eBPF sampling mechanism
  • Integrations
    • Overview
    • Workflow Integrations
      • Slack Webhook Integration
      • Opsgenie Integration
      • Webhook Integration
        • Incident.io
      • PagerDuty Integration
      • Jira Webhook Integration
    • Data sources
      • OpenTelemetry
        • Traces & Logs
        • Metrics
      • Istio
      • AWS
        • Ingest CloudWatch Metrics
        • Ingest CloudWatch Logs
        • Ingest Logs Stored on S3
        • Integrate CloudWatch Grafana Datasource
      • GCP
        • Ingest Google Cloud Monitoring Metrics
        • Stream Logs using Pub/Sub
        • Integrate Google Cloud Monitoring Grafana Datasource
      • Azure
        • Ingest Azure Monitor Metrics
      • DataDog
        • Traces
        • Metrics
      • FluentBit
      • Fluentd
      • JSON Logs
    • 3rd-party metrics
      • ActiveMQ
      • Aerospike
      • Cassandra
      • CloudFlare
      • Consul
      • CoreDNS
      • Etcd
      • HAProxy
      • Harbor
      • JMeter
      • K6
      • Loki
      • Nginx
      • Pi-hole
      • Postfix
      • RabbitMQ
      • Redpanda
      • SNMP
      • Solr
      • Tomcat
      • Traefik
      • Varnish
      • Vertica
      • Zabbix
    • Source control (Gitlab/Github)
  • Architecture
    • Overview
    • inCloud Managed
      • Setup inCloud Managed with AWS
        • AWS PrivateLink Setup
        • EKS add-on
      • Setup inCloud Managed with GCP
      • Setup inCloud Managed with Azure
      • High Availability
      • Disaster Recovery
      • Ingestion Endpoints
      • Deploying in Sensor-Only mode
    • Security considerations
      • Okta SSO - onboarding
    • Service endpoints inside the cluster
  • Product Updates
    • What's new?
    • Earlier updates
      • 2025
        • Mar 2025
        • Feb 2025
        • Jan 2025
      • 2024
        • Dec 2024
        • Nov 2024
        • Oct 2024
        • Sep 2024
        • Aug 2024
        • July 2024
        • May 2024
        • Apr 2024
        • Mar 2024
        • Feb 2024
        • Jan 2024
      • 2023
        • Dec 2023
        • Nov 2023
        • Oct 2023
Powered by GitBook
On this page
  • Sign up to groundcover
  • Installing using our UI
  • To join an existing workspace:
  • To create a new workspace:
  • Enabling Auto-join for a new or existing Workspace
  • Installing using a CLI
  • Installing using Helm
  • What can you do next?
  • Adding more clusters
  • Updating groundcover
  • Using CLI
  • Using Helm
  • Uninstalling
Export as PDF
  1. Getting Started

Installation & updating

Get up and running in minutes

Last updated 2 months ago

Before installing groundcover, please make sure your cluster meets the .

Sign up to groundcover

The first thing you need to do to start using groundcover is using your email address (no credit card required for the free tier account). Signing up is only possible using a computer and will not be possible using a mobile phone or tablet. It is highly recommended you use your corporate email address, as it will make it easier to use other features such as inviting your colleagues to your workspace. However, signing up using Gmail, Outlook or any other public domains is also possible.

After signing up, you can install groundcover using any one of these methods:

Installing using our UI

When to groundcover for the first time, the platform automatically detects your organization based on the domain you used to sign in. If your organization already has existing workspaces available, the workspace selection screen will be displayed, where you can choose which of the existing workspaces you would like to join, or if you want to create a new workspace.

Available workspaces will be displayed only if either of the following applies:

  • You have been invited to join existing workspaces and haven't joined them yet

  • Someone has previously created a workspace that has enabled for the email domain that you used to sign in (applicable for corporate email domains only)

To join an existing workspace:

  1. Click the Join button next to the desired workspace

  2. You will be added as a user to that workspace with the user privileges that were assigned by default or those that were assigned to you specifically when the invite was sent.

  3. You will automatically be redirected to that workspace.

To create a new workspace:

  1. Click the Create a new workspace button

  2. Specify a workspace name

  3. Click continue

  1. Copy the command line displayed on the screen using the Copy Command button (Note: This is not your API key)

  2. Open your CLI

  3. Paste the command line in your CLI (Note: Make sure your kubectl context is pointing to the desired cluster)

  1. The installation screen will open automatically and will let you know on-screen when the installation has completed.

Enabling Auto-join for a new or existing Workspace

Workspace owners and admins can allow teammates that log in with the same email domain as them to join the Workspace they created automatically, without an admin approval. This capability is called "Auto-join". It is disabled by default, but can be switched on during the workspace set up process, or any time in the workspace settings.

If you logged in with a public email domain (Gmail, Yahoo, Proton, etc.) and are creating a new Workspace, you will not be able to switch on Auto-join for that Workspace.

Installing using a CLI

Use groundcover CLI to automate the installation process. The main advantages of using this installation method are:

  • Auto-detection of cluster incompatibility issues

  • Tolerations setup automation

  • Tuning of resources according to cluster size

  • It supports passing helm overrides

  • Automated detection of new versions and upgrades suggestions

Installing groundcover CLI

sh -c "$(curl -fsSL https://groundcover.com/install.sh)"
SET CLI_VERSION=0.22.3
SET ARCH=amd64 # [amd64,arm64]
curl -sSL https://github.com/groundcover-com/cli/releases/download/v%CLI_VERSION%/groundcover_%CLI_VERSION%_windows_%ARCH%.tar.gz -o groundcover.tar.gz
tar -xvf groundcover.tar.gz -C C:\Windows

Deploying groundcover using the CLI

groundcover deploy

------
# If you need to provide configuration values from a values.yaml file:
groundcover deploy -f values.yaml

Installing using Helm

groundcover can be installed using the official helm chart.

If you’re interested in installing the helm chart using a CI/CD solution, such as ArgoCD, make sure you read our CI/CD installation section as well.

# Make sure you have groundcover CLI installed

# (1) Login to your groundcover account
groundcover auth login

# (2) Fetch your api key
groundcover auth print-api-key

# (3) Make sure groundcover Helm repoistory is present (once)
helm repo add groundcover https://helm.groundcover.com

# (4) Update groundcover Helm repository to fetch latest charts
helm repo update groundcover

# (5) Deploy groundcover release
helm upgrade \
    groundcover \
    groundcover/groundcover \
    -i \
    --create-namespace \
    -n groundcover \
    --set global.groundcover_token={api-key},clusterId={cluster-name}
    
------

# If you need to provide configuration values from a values.yaml file:
# (5*) Deploy groundcover release
helm upgrade \
    groundcover \
    groundcover/groundcover \
    -i \
    --create-namespace \
    -n groundcover \
    --set global.groundcover_token={api-key},clusterId={cluster-name} \
    --values values.yaml

What can you do next?

  • Set up your first alert

  • Set up your first dashboard

  • Invite your colleagues

  • Installing groundcover on additional clusters

Adding more clusters

groundcover can monitor multiple clusters, and new clusters can be added at any given time. You can add new clusters using the UI.

Click on the cluster picker in the top right corner and then on the + Add Cluster option.

Updating groundcover

Using CLI

groundcover deploy

------
# If you need to provide configuration values from a values.yaml file:
groundcover deploy -f values.yaml

Using Helm

# Make sure you have groundcover CLI installed

# (1) Login to your groundcover account
groundcover auth login

# (2) Fetch your api key
groundcover auth print-api-key

# (3) Make sure groundcover Helm repoistory is present (once)
helm repo add groundcover https://helm.groundcover.com

# (4) Update groundcover Helm repository to fetch latest charts
helm repo update groundcover

# (5) Deploy groundcover release
helm upgrade \
    groundcover \
    groundcover/groundcover \
    -i \
    --create-namespace \
    -n groundcover \
    --set global.groundcover_token={api-key},clusterId={cluster-name}
    
------

# If you need to provide configuration values from a values.yaml file:
# (5*) Deploy groundcover release
helm upgrade \
    groundcover \
    groundcover/groundcover \
    -i \
    --create-namespace \
    -n groundcover \
    --set global.groundcover_token={api-key},clusterId={cluster-name} \
    --values values.yaml

Uninstalling

groundcover delete
helm uninstall groundcover -n groundcover

# delete the namespace in order to remove the PVCs as well
kubectl delete ns groundcover

Choose whether to enable (those settings can be changed later)

Coverage policy covers all nodes excluding control plane and fargate. .

Within 10 minutes after installation completes, all of your cluster's data will appear in .

Read more .

Coverage policy covers all nodes excluding control plane and fargate. .

Coverage policy covers all nodes excluding control plane and fargate. .

Note: Our free plan limits the use of groundcover on only one cluster. Check out our to install on an unlimited number of clusters.

To update the to the latest version:

See details here
your workspace
here
See details here
See details here
Team and Enterprise plans
groundcover agent
auto-join
requirements
sign up

Install using our UI

Install using a CLI

Install using Helm

Use Argo CD to deploy

signing in
auto-join