GitHub Actions Buildevents

This GitHub Action instruments your workflows using Honeycomb’s buildevents tool. It populates the trace with metadata from the GitHub Actions environment and will always send a trace for the build, even if the build failed.

The Honeycomb Buildevents GitHub Action is maintained by Honeycomb.

How it works

Buildevents is a small binary used to help instrument builds to generate trace telemetry. Typically, it is installed during the setup phase and then invoked as part of each step in a build to capture invocation and output details. The trace generated at the end contains details about what occurred throughout the entire build. The gha-buildevents must be added to every job that should be instrumented to emit traces.

Generated traces contain spans for each section and subsection of the build, with each span representing individual or groups of actual commands that are executed. The duration of each span is how long that stage or specific command took to run. Each span also contains data such as whether or not the command succeeded and any additional data you choose to capture. When your build concludes, this integration ensures your trace is sent to Honeycomb.

This example shows a build workflow in GitHub Actions that is visualized as a trace.



Honeycomb Buildevents (GitHub Marketplace)

read more

Honeycomb Quickstart Guide

read more

GitHub Actions Buildevents Repo

read more

Announcing new GitHub Actions Integration Guide

read more
Terraform Module

Honeycomb Buildevents Starter Pack

read more