Documentation
¶
Overview ¶
Package expvastic can read from any endpoints that provides expvar data and ships them to elasticsearch. You can inspect the metrics with kibana.
Please refer to golang's expvar documentation for more information. Installation guides can be found on github page: https://github.com/arsham/expvastic
At the heart of this package, there is Engine. It acts like a glue between multiple Readers and a Recorder. Messages are transferred in a package called DataContainer, which is a list of DataType objects.
Example configuration ¶
Save it somewhere (let's call it expvastic.yml for now):
settings: log_level: info readers: # You can specify the applications you want to show the metrics FirstApp: # service name type: expvar # the type of reader. More to come soon! type_name: AppVastic # this will be the _type in elasticsearch endpoint: localhost:1234 # where the application routepath: /debug/vars # the endpoint that app provides the metrics interval: 500ms # every half a second, it will collect the metrics. timeout: 3s # in 3 seconds it gives in if the application is not responsive backoff: 10 # after 10 times the application didn't response, it will stop reading from it AnotherApplication: type: expvar type_name: this_is_awesome endpoint: localhost:1235 routepath: /metrics timeout: 13s backoff: 10 recorders: # This section is where the data will be shipped to main_elasticsearch: type: elasticsearch # the type of recorder. More to come soon! endpoint: 127.0.0.1:9200 index_name: expvastic timeout: 8s backoff: 10 the_other_elasticsearch: type: elasticsearch endpoint: 127.0.0.1:9201 index_name: expvastic timeout: 18s backoff: 10 routes: # You can specify metrics of which application will be recorded in which target route1: readers: - FirstApp recorders: - main_elasticsearch route2: readers: - FirstApp - AnotherApplication recorders: - main_elasticsearch route3: # Yes, you can have multiple! readers: - AnotherApplication recorders: - main_elasticsearch - the_other_elasticsearch
Then run the application:
expvasyml -c expvastic.yml
You can mix and match the routes, but the engine will choose the best set-up to achieve your goal without duplicating the results. For instance assume you set the routes like this:
readers: app_0: type: expvar app_1: type: expvar app_2: type: expvar app_3: type: expvar app_4: type: expvar app_5: type: expvar not_used_app: type: expvar # note that this one is not specified in the routes, therefore it is ignored recorders: elastic_0: type: elasticsearch elastic_1: type: elasticsearch elastic_2: type: elasticsearch elastic_3: type: elasticsearch routes: route1: readers: - app_0 - app_2 - app_4 recorders: - elastic_1 route2: readers: - app_0 - app_5 recorders: - elastic_2 - elastic_3 route3: readers: - app_1 - app_2 recorders: - elastic_0 - elastic_1
Expvastic creates three engines like so:
elastic_0 records data from app_0, app_1 elastic_1 records data from app_0, app_1, app_2, app_4 elastic_2 records data from app_0, app_5 elastic_3 records data from app_0, app_5
You can change the numbers to your liking:
gc_types: # These inputs will be collected into one list and zero values will be removed memstats.PauseEnd memstats.PauseNs memory_bytes: # These values will be transoformed from bytes StackInuse: mb # To MB memstats.Alloc: gb # To GB
To run the tests for the codes, in the root of the application run:
go test $(glide nv)
Or for testing readers:
go test ./readers
To show the coverage, se this gist https://gist.github.com/arsham/f45f7e7eea7e18796bc1ed5ced9f9f4a. Then run:
goverall
It will open a browser tab and show you the coverage.
To run all benchmarks:
go test $(glide nv) -run=^$ -bench=.
For showing the memory and cpu profiles, on each folder run:
BASENAME=$(basename $(pwd)) go test -run=^$ -bench=. -cpuprofile=cpu.out -benchmem -memprofile=mem.out go tool pprof -pdf $BASENAME.test cpu.out > cpu.pdf && open cpu.pdf go tool pprof -pdf $BASENAME.test mem.out > mem.pdf && open mem.pdf
Use of this source code is governed by the Apache 2.0 license. License that can be found in the LICENSE file.
Index ¶
Examples ¶
Constants ¶
This section is empty.
Variables ¶
var ( // ErrNoReader is returned when no reader has been provided to the engine ErrNoReader = fmt.Errorf("no reader provided") )
Functions ¶
func StartEngines ¶ added in v0.1.0
func StartEngines(ctx context.Context, log internal.FieldLogger, confMap *config.ConfMap) (chan struct{}, error)
StartEngines creates some Engines and returns a channel that closes it when it's done its work. For each routes, we need one engine that has multiple readers and writes to one recorder. When all recorders of one reader go out of scope, the Engine stops that reader because there is no destination.
Types ¶
type Engine ¶ added in v0.0.4
type Engine struct {
// contains filtered or unexported fields
}
Engine represents an engine that receives information from readers and ships them to a recorder. The Engine is allowed to change the index and type names at will. When the context times out or cancelled, the engine will close and return. Use the shutdown channel to signal the engine to stop recording. The ctx context will create a new context based on the parent.
Example (SendingJobs) ¶
log := internal.DiscardLogger() ctx, cancel := context.WithCancel(context.Background()) recorded := make(chan string) ts := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { recorded <- "Job was recorded" })) defer ts.Close() red, redTearDown := getReader(log) defer redTearDown() rec := getRecorder(ctx, log, ts.URL) e, err := expvastic.New(ctx, log, rec, red) if err != nil { panic(err) } done := make(chan struct{}) go func() { e.Start() done <- struct{}{} }() fmt.Println("Engine creation success:", err == nil) fmt.Println(<-recorded) cancel() <-done fmt.Println("Client closed gracefully")
Output: Engine creation success: true Job was recorded Client closed gracefully
func New ¶ added in v0.7.0
func New(ctx context.Context, log internal.FieldLogger, rec recorder.DataRecorder, reds map[string]reader.DataReader) (*Engine, error)
New creates an Engine instance with already set-up reader and recorders. The Engine's work starts from here by streaming all readers payloads to the recorder. Returns an error if there are recorders with the same name, or any of constructions results in errors.
func WithConfig ¶ added in v0.7.0
func WithConfig(ctx context.Context, log internal.FieldLogger, recorderConf config.RecorderConf, readers ...config.ReaderConf) (*Engine, error)
WithConfig creates an engine by instantiating readers and recorder from the configurations and sends them to the New function.
Directories
¶
Path | Synopsis |
---|---|
cmd
|
|
Package config reads the configurations from a yaml file and produces necessary configuration for instantiating readers and recorders.
|
Package config reads the configurations from a yaml file and produces necessary configuration for instantiating readers and recorders. |
datatype
Package datatype contains necessary logic to sanitise a JSON object coming from a reader.
|
Package datatype contains necessary logic to sanitise a JSON object coming from a reader. |
token
Package token contains necessary logic for passing messages.
|
Package token contains necessary logic for passing messages. |
Package reader contains logic for reading from a provider.
|
Package reader contains logic for reading from a provider. |
expvar
Package expvar contains logic to read from an expvar provide.
|
Package expvar contains logic to read from an expvar provide. |
self
Package self contains codes for recording expvastic's own metrics.
|
Package self contains codes for recording expvastic's own metrics. |
testing
Package testing is a test suit for readers.
|
Package testing is a test suit for readers. |
Package recorder contains logic to record data into a database.
|
Package recorder contains logic to record data into a database. |
elasticsearch
Package elasticsearch contains logic to record data to an elasticsearch index.
|
Package elasticsearch contains logic to record data to an elasticsearch index. |
testing
Package testing is a test suit for recorders.
|
Package testing is a test suit for recorders. |