package module
v0.0.0-...-95baaf8 Latest Latest

This package is not in the latest version of its module.

Go to latest
Published: May 2, 2023 License: Apache-2.0 Imports: 12 Imported by: 8



OpenCensus and OpenTracing have merged to form OpenTelemetry, which serves as the next major version of OpenCensus and OpenTracing.

OpenTelemetry has now reached feature parity with OpenCensus, with tracing and metrics SDKs available in .NET, Golang, Java, NodeJS, and Python. All OpenCensus Github repositories, except census-instrumentation/opencensus-python, will be archived on July 31st, 2023. We encourage users to migrate to OpenTelemetry by this date.

To help you gradually migrate your instrumentation to OpenTelemetry, bridges are available in Java, Go, Python, and JS. Read the full blog post to learn more.

OpenCensus Go Graphite Exporter

Build Status

Gitter chat

The OpenCensus Graphite Stats Exporter for Go is a package that exports data to Graphite, a real-time graphing system that stores and renders graphs of received numeric time-series data on demand.


import ""

The API of this project is still evolving. The use of vendoring or a dependency management tool is recommended.

Register the exporter
func main() {
    // Namespace is an optional part of the Options struct.
    // Stats will be reported every second by default.
    exporter, err := graphite.NewExporter(graphite.Options{Namespace: "opencensus"})

It is possible to set different reporting intervals by using SetReportingPeriod(), for example:

func main() {
    graphite.NewExporter(graphite.Options{Namespace: "opencensus"})
    view.SetReportingPeriod(5 * time.Second)
Options for the Graphite exporter

There are some options that can be defined when registering and creating the exporter. Those options are shown below:

Field Description Default Value
Host Type string. The Host contains the host address for the graphite server ""
Port Type int. The Port in which the carbon/graphite endpoint is available 2003
Namespace Type string. The Namespace is a string value to build the metric path. It will be the first value on the path None
ReportingPeriod Type time.Duration. The ReportingPeriod is a value to determine the buffer timeframe in which the stats data will be sent. 1 second

Implementation Details

To feed data into Graphite in Plaintext, the following format must be used: <metric path> <metric value> <metric timestamp>.

  • metric_path is the metric namespace.
  • value is the value of the metric at a given time.
  • timestamp is the number of seconds since unix epoch time and the time in which the data is received on Graphite.

Frequently Asked Questions

How the stats data is handled?

The stats data is aggregated into Views (which are essentially a collection of metrics, each with a different set of labels). To know more about the definition of views, check the Opencensus docs

How the path is built?

One of the main concepts of Graphite is the metric path. This path is used to aggregate and organize the measurements and generate the graphs.

In this exporter, the path is built as follows:


  • Options.Namespace: Defined in the Options object.
  • View.Name: The name given to the view.
  • Tags: The view tag key and values in the format key=value

For example, in a configuration where:

  • Options.Namespace: 'opencensus'
  • View.Name: 'video_size'
  • Tags: { "name": "video1", "author": "john"}

The generated path will look like:


Graph visualization on Graphite

Graph visualization on Graphite

Heatmap visualization on Grafana

On Grafana it's possible to generate heatmaps based on time series bucket. To do so, it's necessary to configure the Axes, setting the Data format to Time series bucket as shown in the image below:

Axes Configuration

It's also necessary to sort the values so that Grafana displays the buckets in the correct order. For that, it's necessary to insert a SortByName(true) function on the metrics query as shown in the image below:

Metrics Configuration

With this configuration, Grafana automatically identifies the bucket boundaries in the data that's being sent and generate the correct heatmap without the need of further configuration.

In the next image, it's possible to see the heatmap created from a gRPC client latency view, that can be found in the ocgrpc package as ClientRoundtripLatencyView.

The code for generating this example is not much different from the grpc example contained in the example folder. The main change is on line 45 of the client:

// Register the view to collect gRPC client stats.
if err := view.Register(ocgrpc.ClientRoundtripLatencyView); err != nil {

Heatmap example with ClientRoundtripLatencyView



Package graphite contains a Graphite exporter that supports exporting OpenCensus views as Graphite metrics.

package main

import (



func main() {
	exporter, err := graphite.NewExporter(graphite.Options{})
	if err != nil {

	// Serve the scrape endpoint on port 9999.
	log.Fatal(http.ListenAndServe(":9999", nil))




This section is empty.


This section is empty.


This section is empty.


type Exporter

type Exporter struct {
	// contains filtered or unexported fields

Exporter exports stats to Graphite

func NewExporter

func NewExporter(o Options) (*Exporter, error)

NewExporter returns an exporter that exports stats to Graphite.

func (*Exporter) ExportView

func (e *Exporter) ExportView(vd *view.Data)

ExportView exports to the Graphite if view data has one or more rows. Each OpenCensus stats records will be converted to corresponding Graphite Metric

func (*Exporter) Flush

func (e *Exporter) Flush()

type Options

type Options struct {
	// Host contains de host address for the graphite server.
	// The default value is "".
	Host string

	// Port is the port in which the carbon endpoint is available.
	// The default value is 2003.
	Port int

	// Namespace is optional and will be the first element in the path.
	Namespace string

	// Tags specifies a set of default tags to attach to each metric.
	// Tags is optional and will work only for Graphite above 1.1.x.
	// Example : []string{"tagName1=tagValue1", "tagName2=tagValue2"}
	Tags []string

	// OnError is the hook to be called when there is
	// an error uploading the stats or tracing data.
	// If no custom hook is set, errors are logged.
	// Optional.
	OnError func(err error)

Options contains options for configuring the exporter.


Path Synopsis
Command graphite is an example program that collects data for video size.
Command graphite is an example program that collects data for video size.
Package helloworld is a generated protocol buffer package.
Package helloworld is a generated protocol buffer package.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL