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
    • groundcover MCP
      • Configure groundcover's MCP Server
      • Getting-started Prompts
      • Real-world Use Cases
  • 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
    • APIs
    • 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
      • Send groundcover Alerts to Email via Zapier
    • 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
  • Introducing: The Monitors section
  • Issues
  • Monitors
Export as PDF
  1. Product Updates
  2. Earlier updates
  3. 2024

Aug 2024

Last updated 8 months ago

Introducing: The Monitors section

Release Date: Aug 1, 2024

Affected Sections: Workloads

Using the left navigation pane, you can now access a new section of the platform titled "Monitors". groundcover introduced Monitors a few months ago, adding a set of out-of-the-box alerts that act as a safety net that allows you to effortlessly stay on top of the most important issues and irregularities in your environment. Today, all of these alerts are centralized in one dedicated section of the platform, allowing you to instantly get an overview of the health and status of your environment.

The section is divided into two tabs:

Issues

Offers a quick view of all current issues in your environment. See the name and labels of the Monitor, as well as a timeline offering you a quick overview of the change in status of the Monitor, where each bar represents a time period (which changes according to the time range chosen in the time picker in the upper right corner of the screen) and the color of the status (red = Altering, grey = Normal). The percentage on the left of the timeline shows the percentage of the selected time range in which the Monitor was Alerting.

Clicking on any of the issues will offer you expanded information, including:

  • The name of the Monitor - which is comprised of the name of the workload, the criteria, the cluster's name, and the namespace.

  • A timeline - showing the Monitor's threshold (orange), the monitored value (purple), and the status of the Monitor (upper bar), over time. This can help you visualize what happened before or after the Monitor changed status. The ability to select a specific area on the timeline itself enables an even quicker drill-down into the problematic time window.

  • Additional related data for context - view Kubernetes events, logs related to the Monitor (including the ability to filter based on log level), and a map to visualize all interactions with the Monitor's workload.

Monitors

Centralizes all your Monitors in one place, in addition to the different tabs inside each workload's individual information page.

You can use this new section to answer critical questions:

  • Know if anything requires your attention - see which monitors are currently on "Alerting" status.

  • Know where the issue is taking place - see the name of the workload, cluster, and namespace, detailed in the "Name" column.

  • Know what the issue is - view the criteria detailed in the Name column (for example - "memory usage > 85%"), and the description and query details by clicking on the Monitor and opening the extended information screen.

  • Evaluate the scope of the issue - see the number of "Live issues" in that column. You can also see all the workloads affected by this issue and and their statuses.

Clicking on any Monitor will open its full details, including a description, the query details, its status over time, and a list of all related issues.

You can leverage the search bar and filters on the left to show only certain Monitors, based on multiple criteria, such as status, category, and whether or not the Monitor is silenced.

There are many additional developments ahead for this new section, which will increasingly become a central piece of the platform, where you will be able to create and edit Monitors, choose where to be notified about alerting Monitors, view API and infrastructure issues, and much more.