eba01d1119
Due to on going issues, we've decided to remove gorest. It started with gorest
not being thread-safe (it does introspection to create a new handler which is
an easy process to mess up with multiple threads of execution):
https://code.google.com/p/gorest/issues/detail?id=15
While the issue has been marked fixed, it looks like the patch has introduced
more problems than the original issue and simply doesn't work properly.
I'm not sure the behaviour was thought through properly. If a new instance is
needed every request then a handler-factory is needed or the library needs to
set expectations about how the new objects should interact with their
constructor state.
While it was tempting to try out another routing library, I think for now
it's better to use dumb vanilla Go routing. At least until we decide which
URL format we intend to standardize on.
Change-Id: Ica3da135d05f8ab8fc206f51eeca4f684f8efa0e
|
||
|---|---|---|
| .build | ||
| coding | ||
| config | ||
| documentation/examples | ||
| model | ||
| notification | ||
| retrieval | ||
| rules | ||
| stats | ||
| storage | ||
| tools | ||
| utility | ||
| web | ||
| .gitignore | ||
| .pkgignore | ||
| .travis.yml | ||
| build_info.go | ||
| CONTRIBUTORS.md | ||
| Dockerfile | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| Makefile.INCLUDE | ||
| MANIFEST | ||
| README.md | ||
| tests-for-die-in-a-fire-travis.sh | ||
Prometheus
Bedecke deinen Himmel, Zeus! A new kid is in town.
Prometheus is a generic time series collection and computation server that is useful in the following fields:
- Industrial Experimentation / Real-Time Behavioral Validation / Software Release Qualification
- Econometric and Natural Sciences
- Operational Concerns and Monitoring
The system is designed to collect telemetry from named targets on given intervals, evaluate rule expressions, display the results, and trigger an action if some condition is observed to be true.
Prerequisites
If you read below in the Getting Started section, the build infrastructure will take care of the following things for you in most cases:
- Go 1.1.
- LevelDB: https://code.google.com/p/leveldb/.
- Protocol Buffers Compiler: http://code.google.com/p/protobuf/.
- goprotobuf: the code generator and runtime library: http://code.google.com/p/goprotobuf/.
- Levigo, a Go-wrapper around LevelDB's C library: https://github.com/jmhodges/levigo.
- GoRest, a RESTful style web-services framework: http://code.google.com/p/gorest/.
- Prometheus Client, Prometheus in Prometheus https://github.com/prometheus/client_golang.
- Snappy, a compression library for LevelDB and Levigo http://code.google.com/p/snappy/.
Getting Started
For basic help how to get started:
- The source code is periodically indexed: Prometheus Core.
- For UNIX-like environment users users, please consult the Travis CI configuration in .travis.yml and Makefile.
- All of the core developers are accessible via the Prometheus Developers Mailinglist.
General
For first time users, simply run the following:
$ make
If you run into problems, try the following:
$ SILENCE_THIRD_PARTY_BUILDS=false make
Upon having a satisfactory build, it's possible to create an artifact for end-user distribution:
$ make package
$ find build/package
build/package will be sufficient for whatever archiving mechanism you
choose. The important thing to note is that Go presently does not
staticly link against C dependency libraries, so including the lib
directory is paramount. Providing LD_LIBRARY_PATH or
DYLD_LIBRARY_PATH in a scaffolding shell script is advised.
Executing the following target will start up Prometheus for lazy users:
$ ARGUMENTS="-foo -bar -baz" make run
${ARGUMENTS} is passed verbatim into the makefile and thusly Prometheus as
$(ARGUMENTS). This is useful for quick one-off invocations and smoke
testing.
Problems
If at any point you run into an error with the make build system in terms of
its not properly scaffolding things on a given environment, please file a bug or
open a pull request with your changes if you can fix it yourself.
Please note that we're explicitly shooting for stable runtime environments and not the latest-whiz bang releases; thusly, we ask you to provide ample architecture and release identification remarks for us.
Testing
$ make test
Packaging
$ make package
Race Detector
Go 1.1 includes a race detector which can be enabled at build time. Here's how to use it with Prometheus (assumes that you've already run a successful build).
To run the tests with race detection:
$ GORACE="log_path=/tmp/foo" go test -race ./...
To run the server with race detection:
$ go build -race .
$ GORACE="log_path=/tmp/foo" ./prometheus
Contributing
-
To start, reach out via our mailing list (mentioned above) and ask us what the current priorities are. We can find a good isolated starter project for you.
-
Keeping code hygiene is important. We thusly have a practical preference for the following:
-
Run
make formatto ensure the correctness of the Go code's layout. -
Run
make adviceto find facial errors with a static analyzer. -
Try to capture your changes in some form of a test. Go makes it easy to write Table Driven Tests. There is no mandate to use this said scaffolding mechanism, but it can make your life easier in the right circumstances.
-
-
Welcome aboard!
License
Apache License 2.0