Migrations
Migrating to 2.X¶
Version 2.X consists of a major rewrite that turns spectator-go into a thin client designed to send metrics through spectatord. As a result some functionality has been moved to other packages or removed.
New¶
Writers¶
spectator.Registry
now supports different writers. The default writer is writer.UdpWriter
which
sends metrics to spectatord through UDP.
See Usage > Output Location for more details.
Meters¶
The following new Meters have been added:
meter.MaxGauge
meter.Gauge
with TTL
Common Tags¶
A few local environment common tags are now automatically added to all Meters. Their values are read from the environment variables.
Tag | Environment Variable |
---|---|
nf.container | TITUS_CONTAINER_NAME |
nf.process | NETFLIX_PROCESS_NAME |
Tags from environment variables take precedence over tags passed on code when creating the Config
.
Note that common tags sourced by spectatord can't be overwritten.
Config¶
Config
is now created through a constructor which throws error if the passed in parameters are not valid.Config
members are now private.
Moved¶
- Runtime metrics collection has been moved to spectator-go-runtime-metrics. Follow instructions in the README to enable collection.
- Some types have been moved to different packages. For example,
spectator.Counter
is now inmeter.Counter
.
Removed¶
spectator.HttpClient
has been removed. Use the standardhttp.Client
instead.spectator.Meter
s no longer have aMeasure() []Measurement
function. Meters are now stateless and do not store measurements.spectator.Clock
has been removed. Use the standardtime
package instead.spectator.Config
is simplified and local to this library. There is no longer a need to import the internal configuration library.spectator.Registry
no longer has aStart()
function. TheRegistry
is now effectively stateless and there is nothing to start other than opening the output location.spectator.Registry
no longer has aStop()
function. Instead, useClose()
to close the registry. Once the registry is closed, it can't be started again. This is intended for final clean up of sockets or file handles.spectator.Config.IpcTimerRecord
has been removed. Use ameter.Timer
instead to record Ipc metrics.spectator.MeterFactoryFun
has been removed. If you need to create a custom meter you can do so by wrapping one of the meters returned byspectator.Registry
.spectator.Registry
no longer reportsspectator.measurements
metrics. Instead, you can use similar metrics fromspectatord
for visibility.spectator.Registry
no longer keeps track of the Meters it creates. This means that you can't get a list of all Meters from the Registry. If you need to keep track of Meters, you can do so in your application code.Percentile*
meters no longer support defining min/max values.spectator.Registry
no longer allows setting a different logger after creation. A custom logger can be set in thespectator.Config
before creating the Registry.- File-based configuration is no longer supported.
Migration Steps¶
- Make sure you're not relying on any of the removed functionality.
- Update imports for
Config
andRegistry
, and use themeters
package instead ofspectator
for Meters. - If you want to collect runtime metrics, add the spectator-go-runtime-metrics library, and follow the instructions in the README.
- If you use
PercentileDistributionSummary
orPercentileTimer
, then you need to update your code to use the respective functions provided by theRegistry
to initialize these meters. - Remove the dependency on the
spectator-go
internal configuration library - it is no longer required. - There is no longer an option to
start()
orstop()
theRegistry
at runtime. If you need to configure aRegistry
that doesn't emit metrics, for testing purposes, you can use thespectator.Config.Location
option withnone
to configure a no-op writer.