Custom Deployment (Optional)

​groundcover supports many custom configurations so you can fit it to the way your deployment works and to your exact needs.

Kubernetes deployment

Our helm chart provides access to many values passed into the chart via the standard values.yaml interface. The deployment can be configured based on most constraints and controls Kubernetes allows around pod assignments to nodes.
Among which groundcover's deployment supports:
  1. 1.
    nodeSelector - a simple form of node selection constraint. You can add the nodeSelector field to your Pod specification and specify the node labels you want the target node to have.
  2. 2.
    nodeAffinity - allowing you to constrain which nodes your Pod can be scheduled on based on node labels and is more expressive than nodeSelector and allows you to specify soft rules.
groundcover supports most K8s primitives out there. Can't find what you need? let us know over Slack.​

Data collection

​groundcover allows you to control the way data is being collected and treated across your cluster in many ways.
Here are a few worth knowing:
  1. 1.
    Namespace blacklist - by default the groundcover agent collects and stores data from all namespaces found in the cluster. In some cases it makes sense to avoid collecting and storing from specific namespaces. These namespaces can be specified as blacklisted at the agent's installation.
  2. 2.
    Sensitive data obfuscation - as any application monitoring system, the data collected by groundcover is by nature sensitive and contains payloads of full requests and queries. Raw traces can go a long way in a troubleshooting process, but you can choose to obfuscate their payload.
  3. 3.
    Node label collection - by default the groundcover agent will add any node label to the labels of every metric generated under this agent. This allows intelligent dissection of the data by labels which may be much more meaningful than a node name. This collection can be turned off at any time.

IaaC or Package managers

​groundcover has been tested to work with Helm, Pulumi, simple YAML installation and many other methods.
Using a different method to manage your deployment and not sure how to integrate groundcover? let us know over Slack.​