2744a26b60
* tie defaults to releases this change makes it so that by default, the flag defaults are chosen based on whether the build was built as a release build or an ordinary build. release builds by default get release defaults, whereas ordinary builds by default get dev defaults. any binary can have its defaults changed by specifying --defaults=dev or --defaults=release Change-Id: I6d216aa345d211c69ad913159d492fac77b12c64 * make release defaults more clear this change extends cfgstruct structs to support either a 'default' tag, or a pair of 'devDefault' and 'releaseDefault' tags, but not both, for added clarity Change-Id: Ia098be1fa84b932fdfe90a4a4d027ffb95e249c6 * clarify cfgstruct.DefaultsFlag Change-Id: I55f2ff9080ebbc0ce83abf956e085242a92f883e |
||
|---|---|---|
| .. | ||
| luacfg | ||
| common.go | ||
| copy.go | ||
| db.go | ||
| example.lua | ||
| file.go | ||
| filter.go | ||
| graphite.go | ||
| main.go | ||
| parser.go | ||
| print.go | ||
| README.md | ||
| sanitizer.go | ||
| schema.sql | ||
| udp.go | ||
statreceiver
This package implements a Lua-scriptable pipeline processor for zeebo/admission telemetry packets (like monkit or something).
There are a number of types of objects involved in making this work:
- Sources - A source is a source of packets. Each packet is a byte slice that, when parsed, consists of application and instance identification information (such as the application name and perhaps the MAC address or some other id of the computer running the application), and a list of named floating point values. There are currently two types of sources, a UDP source and a file source. A UDP source appends the current time as the timestamp to all packets, whereas a file source should have a prior timestamp to attach to each packet.
- Packet Destinations - A packet destination is something that can handle a packet with a timestamp. This is either a packet parser, a UDP packet destination for forwarding to another process, or a file destination that will serialize all packets and timestamps for later replay.
- Metric Destinations - Once a packet has been parsed, the contained metrics can get sent to a metric destination, such as a time series database, a relational database, stdout, a metric filterer, etc.
Please see example.lua for a good example of using this pipeline.
Setup
If you use a relational database metric destination, make sure to instantiate the schema provided in schema.sql first.