1. Docs
  2. Observe
  3. Custom Boards
  4. Board Templates

Use Board Templates

Get instant insights into your system with Board templates.

Tip
This functionality is available only for teams using Honeycomb’s current data model. If you use Honeycomb Classic, we recommend migrating to Honeycomb Environments, so you can take advantage of its expanded data model and future product updates.

What is a Board Template? 

Board templates are pre-configured Boards that come with ready-made queries and visualizations, providing valuable insights with minimal setup. Use a template as starting point to create a Board.

Templates are designed for specific use cases and built around industry best practices, ensuring effective configurations for tracking key metrics and visualizing data accurately.

Board Templates At a Glance 

Choose from a variety of templates to quickly gain insights across different areas of your system:

  • General:
    • Service Health: Provides insights into service health, including request volumes and where slowest requests occur.
    • Real User Monitoring (RUM): Displays real user monitoring data for frontend applications, including performance and user experience insights.
    • Refinery Operations: Shows an overview of sampling operations, including trace throughput and sampling statistics. Automatically populated by Refinery metrics sent to Honeycomb.
  • Kubernetes:
    • Kubernetes Pod Metrics: Helps you investigate pod performance and resource usage within Kubernetes clusters.
    • Kubernetes Node Metrics: Helps you investigate node performance and resource usage within Kubernetes clusters.
    • Kubernetes Workload Health: Helps you investigate application problems related to Kubernetes workloads.
  • OpenTelemetry:
    • OpenTelemetry Collector Operations: Provides metrics emitted by the OpenTelemetry Collector during operation.
    • OpenTelemetry Java Metrics: Offers insights into Java Virtual Machine (JVM) health and performance via metrics reported by OpenTelemetry Java Agent or Honeycomb OpenTelemetry Distribution for Java.
  • Amazon Web Services (AWS):
    • AWS Lambda Health: Provides information about AWS Lambda function health, including invocations, errors, throttles, and concurrency.
  • Honeycomb Features:
    • Activity Log Security: Displays queries showing API Key activity.
    • Activity Log Leaderboard: Displays queries showing advanced and frequent Honeycomb usage by your team.
    • Activity Log Trigger and SLO Activity: Displays queries related to trigger and SLO activations and modifications.

General 

Service Health 

The Service Health Board template offers an overview of your services’ health. It provides insights into request volumes, identifies where the slowest requests are occurring, and more.

Tip
The Service Health Board template relies on your source data fields being mapped to Honeycomb standard fields. To learn how to map your fields, visit Dataset Definitions.

The Service Health Board template includes the following queries:

Query Name Query Description Required Fields
Trace Counts by Service Shows total trace volume by service.
  • Parent span ID or trace.parent_id
  • Service name or service.name or service_name
Trace Counts by HTTP Status Code Shows total trace volume by status code.
  • Parent span ID or trace.parent_id
  • HTTP Status Code or http.response.status.code or http.status_code
Trace Duration Heatmap Shows a heatmap of the duration for all traces.
  • Span duration or duration_ms
  • Parent span ID or trace.parent_id
Duration Heatmap Shows a heatmap of duration across all services.
  • Span duration or duration_ms
Duration by Service Shows key duration percentiles by service.
  • Span duration or duration_ms
  • Service name or service.name or service_name
Duration by Route Shows duration by route or endpoint.
  • Span duration or duration_ms
  • Route or http.route
Duration by Name Shows duration by function name.
  • Span duration or duration_ms
  • Name or name
Errors by Service Shows a count of errors grouped by service.
  • Error or error
  • Service name or service.name or service_name
Errors by Route Shows a count of errors grouped by route or endpoint.
  • Error or error
  • Route or http.route

Real User Monitoring (RUM) 

The RUM Board template provides an overview of real user monitoring data from your frontend applications.

Tip
The RUM Board template relies on your source data fields being mapped to Honeycomb standard fields. To learn how to map your fields, visit Dataset Definitions. To learn more about instrumenting your frontend application, visit Send Browser Data with Honeycomb Web Instrumentation.

The RUM Board template includes the following queries:

Query Name Query Description Required Fields
Largest Contentful Paint (LCP) Shows ratings based on the render time for the largest content on a page.
  • lcp.rating
  • name
Cumulative Layout Shift (CLS) Shows ratings based on the stability of content layout on a page.
  • cls.rating
  • name
Interaction to Next Paint (INP) Shows ratings based on the responsiveness of a page.
  • inp.rating
  • name
LCP P75 Shows the 75th percentile for LCP.
  • name
  • lcp.value
CLS P75 Shows the 75th percentile for CLS.
  • cls.value
  • name
INP P75 Shows the 75th percentile for INP.
  • inp.value
  • name
Total Events by Type Shows event types ranked by occurrence.
  • name
  • meta.annotation_type
Largest Resource Requests Shows the largest resource requests ranked by the average length of their response content.
  • http.response_content_length
  • http.url
  • name
Top 5 Endpoints by Request Count Shows the top 5 endpoints ranked by number of requests.
  • http.method
  • name
  • http.url
Slowest Requests by Endpoint Shows the slowest endpoints based on the 75th percentile of request durations.
  • http.url
  • duration_ms
  • name
Top Landing Pages by Session Count Shows the most visited landing pages ranked by session count.
  • entry_page.path
  • name
Pages With the Most Events Shows pages with the highest number of events, highlighting the most active pages.
  • Route or http.route

Refinery Operations 

For teams using Refinery to sample their data, the Refinery Board template provides an overview of sampling operations.

Tip
Refinery emits metrics that provide insights into its health, trace throughput, and sampling statistics. Required fields in the Refinery Board template map to these metrics and populate automatically when sent to Honeycomb. To learn more about these fields, visit Refinery Configuration.

The Refinery Board template includes the following queries:

Query Name Query Description Required Fields
Stress Relief Status Shows the current stress level on the Refinery cluster.
  • stress_level
  • stress_relief_activated
  • hostname or host.name
Dropped From Stress Shows how many traces are being dropped due to stress on the Refinery cluster.
  • dropped_from_stress
  • hostname or host.name
Stress Relief Log Shows reasons why Refinery is going into stress relief.
  • StressRelief
  • reason
  • msg
  • hostname or host.name
Cache Health Shows metrics for cache health.
  • collect_cache_buffer_overrun
  • memory_inuse
  • collect_cache_entries_max or collect_cache_entries.max
  • collect_cache_capacity
  • num_goroutines
  • process_uptime_seconds
  • hostname or host.name
Cache Ejections Shows number of traces ejected from cache.
  • trace_send_ejected_full
  • trace_send_ejected_memsize
  • hostname or host.name
Intercommunications Shows total events from outside Refinery and events redirected from a peer.
  • incoming_router_span
  • peer_router_batch
  • hostname or host.name
Receive Buffers Shows receive buffer operations.
  • incoming_router_dropped
  • peer_router_dropped
  • hostname or host.name
Peer Send Buffers Show metrics for the queue used to buffer spans to send to peer nodes.
  • libhoney_peer_queue_overflow
  • libhoney_peer_send_errors
  • hostname or host.name
Upstream Send Buffers Shows metrics for the queue used to buffer spans to send to Honeycomb.
  • libhoney_upstream_queue_length
  • libhoney_upstream_enqueue_errors
  • libhoney_upstream_response_errors
  • libhoney_upstream_send_errors
  • libhoney_upstream_send_retries
  • hostname or host.name
EMADynamicSampler Performance Shows EMADynamicSampler sampling effectiveness.
  • emadynamic_sample_rate_avg
  • emadynamic_keyspace_size
  • emadynamic_num_kept
  • emadynamic_num_dropped
EMAThroughputSampler Performance Shows EMAThroughputSampler sampling effectiveness.
  • emathroughput_sample_rate_avg
  • emathroughput_keyspace_size
  • emathroughput_num_kept
  • emathroughput_num_dropped
WindowedThroughput Performance Shows WindowedThroughput sampling effectiveness.
  • windowedthroughput_sample_rate_avg
  • windowedthroughput_keyspace_size
  • windowedthroughput_num_kept
  • windowedthroughput_num_dropped
TotalThroughputSampler Performance Shows TotalThroughputSampler sampling effectiveness.
  • totalthroughput_sample_rate_avg
  • etotalthroughput_keyspace_size
  • totalthroughput_num_kept
  • totalthroughput_num_dropped
DynamicSampler Performance Shows DynamicSampler sampling effectiveness.
  • dynamic_sample_rate_avg
  • dynamic_keyspace_size
  • dynamic_num_kept
  • dynamic_num_dropped
RulesBasedSampler Performance Shows RulesBasedSampler sampling effectiveness.
  • rulesbased_sample_rate_avg
  • rulesbased_num_kept
  • rulesbased_num_dropped
Trace Indicators Shows total traces sent before completion and span received for a trace already sent.
  • trace_sent_cache_hit
  • trace_send_no_root
Sampling Decisions Shows total traces accepted and sent or dropped.
  • trace_accepted
  • trace_send_dropped
  • trace_send_kept
Refinery Send Event Error Logs Shows errors when sending events to its peers or upstream to our API server.
  • msg
  • dataset
  • api_host
  • error
Refinery Handler Event Error Logs Shows errors when receiving or parsing events being sent to a node.
  • msg
  • dataset
  • api_host
  • error.err
  • error.msg
Refinery Events Exceeding Max Size Shows errors when events are too large to be sent to Honeycomb.
  • msg
  • dataset
  • api_host
  • error

Kubernetes 

Tip
Use the Kubernetes Quick Start to instrument the required fields for Kubernetes Board templates.

Kubernetes Pod Metrics 

The Kubernetes Pod Metrics Board template includes queries that help you investigate pod performance and resource usage within Kubernetes clusters:

Query Name Query Description Required Fields
Pod CPU Usage Shows the amount of CPU used by each pod in the cluster. CPU is reported as the average core usage measured in cpu units. One cpu, in Kubernetes, is equivalent to 1 vCPU/Core for cloud providers, and 1 hyper-thread on bare-metal Intel processors.
  • k8s.pod.cpu.utilization
  • k8s.pod.name
Pod Memory Usage Shows the amount of memory being used by each Kubernetes pod.
  • k8s.pod.memory.usage
  • k8s.pod.name
Pod Uptime Smokestacks As pod uptime ever-increases, this query uses the smokestack method, which applies a LOG10 to the Pod Uptime metric, and newly started or restarted pods appear more significantly than pods that have been running a long time, which move into a straight line eventually.
  • LOG10($k8s.pod.uptime)
  • k8s.pod.name
  • k8s.pod.uptime
Unhealthy Pods Shows trouble that pods may be experiencing during their operating lifecycle. Many of these events are present during start-up and get resolved so the presence of a count isn’t necessarily bad.
  • k8s.namespace.name
  • k8s.pod.name
  • reason
Pod CPU Utilization vs. Limit When a CPU Limit is present in a pod configuration, this query shows how much CPU that each pod uses as a percentage against that limit.
  • k8s.pod.cpu_limit_utilization
  • k8s.pod.name
Pod CPU Utilization vs. Request When a CPU Request is present in a pod configuration, this query shows how much CPU that each pod uses as a percentage against that request value.
  • k8s.pod.cpu_request_utilization
  • k8s.pod.name
Pod Memory Utilization vs. Limit When a Memory Limit is present in a pod configuration, this query shows how much memory that each pod uses as a percentage against that limit value.
  • k8s.pod.memory_limit_utilization
  • k8s.pod.name
Pod Memory Utilization vs. Request When a Memory Request is present in a pod configuration, this query shows how much memory that each pod uses as a percentage against that request value.
  • k8s.pod.memory_request_utilization
  • k8s.pod.name
Pod Network IO Rates Displays Network IO RATE_MAX for Transmit and Receive network traffic (in bytes) as a stacked graph, and gives the overall network rate and the individual rate for each node.
  • k8s.pod.name
  • k8s.pod.network.io.receive
  • k8s.pod.network.io.transmit
Pods With Low Filesystem Availability Shows any pods where filesystem availability is below 5 GB.
  • k8s.pod.filesystem.available
  • k8s.pod.name
Pod Filesystem Usage Shows the amount of filesystem usage per Kubernetes pod, displayed in a stack graph to show total filesystem usage of all pods.
  • k8s.pod.filesystem.usage
  • k8s.pod.name
Pods Per Namespace Shows the number of pods currently running in each Kubernetes namespace.
  • k8s.namespace.name
  • k8s.pod.name
Pods Per Node Shows the number of pods currently running in each Kubernetes Node.
  • k8s.node.name
  • k8s.pod.name
Pod Network Errors Shows network errors in receive and transmit, grouped by pod.
  • k8s.pod.name
  • k8s.pod.network.errors.receive
  • k8s.pod.network.errors.transmit
Pods Per Deployment Shows the number of pods currently deployed in different Kubernetes deployments.
  • k8s.deployment.name
  • k8s.pod.name

Kubernetes Node Metrics 

The Kubernetes Node Metrics Board template includes queries that help you investigate node performance and resource usage within Kubernetes clusters:

Query Name Query Description Required Fields
Node CPU Usage Shows the amount of CPU used on each node in the cluster. CPU is reported as the average core usage measured in cpu units. One cpu, in Kubernetes, is equivalent to 1 vCPU/Core for cloud providers, and 1 hyper-thread on bare-metal Intel processors.
  • k8s.node.cpu.utilization
  • k8s.node.name
Node Memory Utilization Shows percent of memory used on each Kubernetes node.
  • IF(EXISTS($k8s.node.memory.available), MUL(DIV($k8s.node.memory.working_set, $k8s.node.memory.available), 100))
  • k8s.node.memory.available
  • k8s.node.memory.usage
  • k8s.node.name
Node Network IO Rates Displays Network IO RATE_MAX for Transmit and Receive network traffic as a stacked graph, and gives overall network rate and the individual rate for each node.
  • k8s.node.name
  • k8s.node.network.io.receive
  • k8s.node.network.io.transmit
Unhealthy Nodes Shows errors that Kubernetes nodes are experiencing.
  • k8s.namespace.name
  • k8s.node.name
  • reason
  • severity_text
Node Filesystem Utilization Shows percent of filesystem used on each node.
  • IF(EXISTS($k8s.node.filesystem.usage),MUL(DIV($k8s.node.filesystem.usage,$k8s.node.filesystem.capacity), 100))
  • k8s.node.filesystem.capacity
  • k8s.node.filesystem.usage
  • k8s.node.name
Node Uptime Smokestack As node uptime ever-increases, this query uses the smokestack method, which applies a LOG10 to the Node Uptime metric, and newly started or restarted nodes appear more significantly than nodes that have been running a long time, which move into a straight line eventually.
  • LOG10($k8s.node.uptime)
  • k8s.node.name
  • k8s.node.uptime
Node Network Errors Shows network transmit and receive errors for each node.
  • k8s.node.name
  • k8s.node.network.errors.receive
  • k8s.node.network.errors.transmit
Pods and Containers per Node Shows the number of pods and the number of containers per node as stacked graphs, and also shows total number of pods and containers across the environment.
  • k8s.container.name
  • k8s.node.name
  • k8s.pod.name

Kubernetes Workload Health 

The Kubernetes Workload Health Board template includes queries that help you diagnose Kubernetes-related application issues:

Query Name Query Description Required Fields
Container Restarts Shows the total number of restarts per pod, and the rate of restarts of pods where the restart count is greater than zero.
  • k8s.container.name
  • k8s.container.restarts
  • k8s.namespace.name
  • k8s.pod.name
Unhealthy Pods Shows trouble that pods may be experiencing during their operating lifecycle. Many of these events are present during start-up and get resolved so the presence of a count isn’t necessarily bad.
  • k8s.namespace.name
  • k8s.pod.name
  • reason
Pending Pods Shows pods in a “Pending” state.
  • k8s.pod.name
  • k8s.pod.phase
Failed Pods Shows pods in a “Failed” or “Unknown” state.
  • k8s.pod.name
  • k8s.pod.phase
Unhealthy Nodes Shows errors that Kubernetes nodes are experiencing.
  • k8s.namespace.name
  • reason
  • k8s.pod.name
  • reason
  • severity_text
Unhealthy Volumes Shows volume creation and attachment failures.
  • k8s.namespace.name
  • k8s.pod.name
  • reason
  • severity_text
Unscheduled Daemonset Pods Tracks cases where a pod in a daemonset is not currently running on every node in the cluster as it should be.
  • SUB($k8s.daemonset.desired_scheduled_nodes, $k8s.daemonset.current_scheduled_nodes)
  • k8s.daemonset.current_scheduled_nodes
  • k8s.daemonset.desired_scheduled_nodes
  • k8s.daemonset.name
    • k8s.namespace.name
Stateful Set Pod Readiness Tracks any stateful sets where pods are in an non-ready state that should be in a ready state.
  • SUB($k8s.statefulset.desired_pods,$k8s.statefulset.ready_pods)
  • k8s.statefulset.desired_pods
  • k8s.statefulset.name
  • k8s.statefulset.ready_pods
Deployment Pod Status Shows Deployments where Pods have not fully deployed. Numbers greater than zero show pods in a deployment that are not yet “ready”.
  • SUB($k8s.deployment.desired,$k8s.deployment.available)
  • k8s.deployment.available
  • k8s.deployment.desired
  • k8s.deployment.name
Job Failures Tracks the number of failed pods in Kubernetes jobs.
  • k8s.job.failed_pods
  • k8s.job.name
Active Cron Jobs Tracks the number of active pods in each Kubernetes cron job.
  • k8s.cronjob.active_jobs
  • k8s.cronjob.name

OpenTelemetry 

OpenTelemetry Collector Operations 

The OpenTelemetry Collector Operations Board template includes queries with key metrics emitted by the OpenTelemetry Collector during its operation:

Query Name Query Description Required Fields
Exporter Span Failures Shows when errors happen during enqueueing or sending in exporters.
  • net.host.name
  • otelcol_exporter_enqueue_failed_spans
  • otelcol_exporter_send_failed_spans
Collector Uptime Smokestacks Shows the uptime for different pods with a Log10 to make it clearer where restarts are happening.
  • LOG10($otelcol_process_uptime)
  • net.host.name
  • otelcol_process_uptime
Exporter Metric Send Failures Shows when errors happen during sending from exporters.
  • net.host.name
  • otelcol_exporter_enqueue_failed_metric_points
  • otelcol_exporter_send_failed_metric_points
Exporter Metrics Enqueue Failures Shows when errors happen during enqueueing in exporters.
  • net.host.name
  • otelcol_exporter_send_failed_metric_points
Exporter Log Records Failures Shows when errors happen during enqueueing or sending in exporters.
  • net.host.name
  • otelcol_exporter_enqueue_failed_log_records

OpenTelemetry Java Metrics 

The OpenTelemetry Java Metrics Board template includes queries that help you investigate application issues related to the Java Virtual Machine (JVM).

Metrics for Java applications are sourced from the JVM and reported by the OpenTelemetry Java Agent or Honeycomb OpenTelemetry Distribution for Java.

Query Name Query Description Required Fields
JVM Memory Usage (Young Generation) Shows memory usage for Eden space on the JVM heap, which is where newly created objects are stored. When it fills, a minor Garbage Collection (GC) occurs, moving all “live” objects to the Survivor space. In addition to current memory usage, committed represents the guaranteed available memory, and limit represents maximum usable.
  • host.name
  • pool
  • process.runtime.jvm.memory.committed
  • process.runtime.jvm.memory.limit
  • process.runtime.jvm.memory.usage
  • process.runtime.jvm.memory.usage_after_last_gc
  • service.name
  • type
JVM Memory Usage (Old Generation) Shows memory usage for tenured Gen JVM heap space, which stores long-lived objects. When a Full or Major GC is performed, it is expensive and may pause app execution. Committed represents guaranteed available memory, and limit represents maximum usable memory.
  • host.name
  • pool
  • process.runtime.jvm.memory.committed
  • process.runtime.jvm.memory.limit
  • process.runtime.jvm.memory.usage
  • process.runtime.jvm.memory.usage_after_last_gc
  • service.name
  • type
JVM Garbage Collection (GC) Activity Shows JVM garbage collection activity. JVM GC actions occur periodically to reclaim memory but consume CPU cycles to do so. In the worst cases, a GC can cause the entire JVM to pause, making the application appear unresponsive.
  • process.runtime.jvm.gc.duration.count
  • action
  • gc
  • host.name
  • process.runtime.jvm.gc.duration.avg
  • process.runtime.jvm.gc.duration.max
  • service.name
JVM CPU Utilization Shows system CPU utilization and 1-minute load average, as captured by the JVM.
  • host.name
  • process.runtime.jvm.cpu.utilization
  • process.runtime.jvm.system.cpu.load_1m
  • service.name
JVM Buffer Memory Usage Shows usage of buffer memory, which is provided by the OS and is outside the JVM’s heap memory allocation. Buffer memory is used by Java NIO to quickly write data to network or disk.
  • host.name
  • process.runtime.jvm.buffer.limit
  • process.runtime.jvm.buffer.usage
  • service.name
JVM Non-Heap Memory Usage Shows usage of JVM non-heap memory, which is allocated above and beyond the heap size you’ve configured. JVM non-heap memory is a section of memory in the JVM that stores class information (Metaspace), compiled code cache, thread stack, and so on. It cannot be garbage collected.
  • host.name
  • pool
  • process.runtime.jvm.memory.committed
  • process.runtime.jvm.memory.limit
  • process.runtime.jvm.memory.usage
  • service.name
  • type

AWS 

AWS Lambda Health 

The AWS Lambda Health Board template includes queries that monitor the health of AWS Lambda functions, including metrics for invocations, errors, throttles, and concurrency:

Query Name Query Description Required Fields
Duration & Execution by ID/Version Tracks the execution time of Lambda functions, identified by their ID or version. Useful for analyzing the performance and efficiency of different versions or instances of a function over time.
  • duration_ms
  • faas.execution
  • faas.name
  • faas.version
Lambda Invocations by Function Shows the total number of times each Lambda function is invoked. It helps in tracking the frequency of usage of different functions, enabling a clear understanding of which functions are most or least used.
  • FunctionName
  • MetricName
  • Namespace
Latency by Function/Metric Shows the response time for each Lambda function, broken down by specific metrics. Useful for identifying functions that may be experiencing performance issues due to high latency.
  • FunctionName
  • MetricName
  • Namespace
  • amazonaws.com/AWS/Lambda/Duration.max
  • amazonaws.com/AWS/Lambda/PostRuntimeExtensionsDuration.max
Function Error Count and Rate Shows two key pieces of information: the total number of errors encountered by each Lambda function and the error rate, calculated as the ratio of errors to total invocations. Useful for pinpointing functions that are failing or experiencing issues.
  • FunctionName
  • MetricName
  • Namespace
  • amazonaws.com/AWS/Lambda/Errors.count
Lambda Throttles Shows the instances where Lambda invocations are being throttled, such as when the number of function calls exceeds the concurrency limits. Tracking this helps in managing and optimizing the scalability settings for each function.
  • FunctionName
  • MetricName
  • Namespace
  • amazonaws.com/AWS/Lambda/Throttles.count
Function Concurrency Monitors the simultaneous execution count of each Lambda function, tracking how many instances of a function are running at the same time.
  • FunctionName
  • MetricName
  • Namespace
  • amazonaws.com/AWS/Lambda/ConcurrentExecutions.avg
  • amazonaws.com/AWS/Lambda/UnreservedConcurrentExecutions.avg

Honeycomb Features 

Activity Log Security 

Tip
Honeycomb automatically creates the required fields for the Activity Log Board templates when it generates Activity Log events.

The Activity Log Security Board template includes queries that track API Key activity:

Query Name Query Description Required Fields
API Key Added Permissions Shows when permissions are added to an existing API key.
  • resource.type
  • resource.changed_fields
  • environment.slug
API Key Activities by User Displays the number of changes to API keys broken down by user.
  • key_type
  • environment.slug
  • user.email
  • resource.action
Authentication Type by User Displays which type of authentication is used for each user.
  • authentication_method
  • user.email

Activity Log Leaderboard 

Tip
Honeycomb automatically creates the required fields for the Activity Log Board templates when it generates Activity Log events.

The Activity Log Leaderboard Board template includes queries that highlight advanced and frequent usage of Honeycomb by your team:

Query Name Query Description Required Fields
Queries by User Shows which environments are being queried.
  • resource.type
  • user.email
Complex Queries by User Shows which users frequently use Visualize, Where, and Having clauses.
  • resource.type
  • SUM( IF(EXISTS($query.having), 3, 0), REG_COUNT($query.where, `,`), REG_COUNT($query.visualize, `,`))
  • user.email
Top Query Visualizations Shows the most commonly used visualizations.
  • resource.type
  • SUM( IF(EXISTS($query.having), 3, 0), REG_COUNT($query.where, `,`), REG_COUNT($query.visualize, `,`))
  • query.visualize
Top Tinkerers Lists which users perform the most updates to SLOs, Triggers, and Calculated Fields.
  • resource.type
  • user.email
Queries by Dataset Shows which datasets are being queried the most.
  • resource.type
  • environment.slug
  • dataset.slug
Queries by Environment Shows a count of run queries as grouped by environment.
  • resource.type
  • environment.slug

Activity Log Trigger and SLO Activity 

Tip
Honeycomb automatically creates the required fields for the Activity Log Board templates when it generates Activity Log events.

The Activity Log Trigger and SLO Activity Board template includes queries related to trigger and SLO activations and modifications:

Query Name Query Description Required Fields
Trigger State Changes Shows instances when triggers have been triggered or resolved.
  • resource.type
  • resource.action
  • name
Trigger Modifications Shows creations, modifications, and deletions of triggers.
  • resource.type
  • resource.action
Most Updated Triggers Shows triggers that received the most changes recently.
  • resource.type
  • resource.action
  • name
Top Updated SLOs by Update Type Shows creations, modifications, and deletions of SLOs and the supporting SLI (Calculated Field).
  • resource.type
  • resource.action
  • environment.slug
  • resource.changed_fields
  • name
  • user.email
SLOs Created and Deleted Shows creation and deletion of SLOs.
  • resource.type
  • resource.action
  • environment.slug
  • name
  • resource.changed_fields
  • user.email
SLI Expression Changes by SLO Shows when SLIs (Calculated Fields) related to SLOs have been changed.
  • resource.type
  • resource.action
  • resource.changed_fields
  • environment.slug
  • name
  • sli.expression
  • before.sli.expression
  • user.email

Troubleshooting 

To explore common issues when working with Board Templates, visit Common Issues with Visualization: Board Templates.

On this page: