RepoMirrors
/
prometheus
mirror of https://github.com/prometheus/prometheus
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
1,175 Commits 210 Branches 425 Tags 699 MiB
Go 85%
TypeScript 13.7%
Yacc 0.5%
Shell 0.2%
SCSS 0.2%
Other 0.1%
Go to file
Julius Volz 00a2a93a05 Add regression tests for metrics mutations in AST. 
It turned out in the end, that only drop_common_metrics() produced any
erroneous output in the old system. The second expression in the test
("sum(testmetric) keeping_extra") already worked in the old code, but
why not keep it in...

The way to test ranged evaluations is a bit clumsy so far, so I want to
build a nicer test framework in the end, where all the test cases can be
specified as text files which specify desired inputs, outputs, query
step widths, etc.

Change-Id: I821859789e69b8232bededf670a1b76e9e8c8ca4
 		2014-12-12 20:34:55 +01:00
.build Simplify makefiles. 2014-11-25 17:10:39 +01:00
config Fix typos and import order. 2014-12-10 17:46:56 +01:00
documentation Update architecture diagram. 2014-12-07 01:58:20 +01:00
notification Apply a giant code cleanup. 2014-12-10 16:16:49 +01:00
retrieval Apply a giant code cleanup. 2014-12-10 16:16:49 +01:00
rules Add regression tests for metrics mutations in AST. 2014-12-12 20:34:55 +01:00
stats Apply a giant code cleanup. 2014-12-10 16:16:49 +01:00
storage Introduce copy-on-write for metrics in AST. 2014-12-12 20:34:55 +01:00
templates Introduce copy-on-write for metrics in AST. 2014-12-12 20:34:55 +01:00
tools Changes after pair code review. 2014-11-25 17:12:59 +01:00
utility Fix typos and import order. 2014-12-10 17:46:56 +01:00
web Fix typos and import order. 2014-12-10 17:46:56 +01:00
.gitignore More updates for first time users. 2013-10-22 20:54:43 +02:00
.pkgignore Make prometheus build on bazooka repo manager 2013-06-13 16:31:33 +02:00
.travis.yml Use less offensive language WRT Travise. 2014-12-09 14:25:37 +01:00
CHANGELOG.md Cut v0.8.0. 2014-11-25 17:02:01 +01:00
CONTRIBUTING.md Link to relevant style guidelines. 2014-05-06 12:23:03 +02:00
CONTRIBUTORS.md Update community documentation. 2013-03-28 10:46:41 +01:00
Dockerfile Use ENTRYPOINT and CMD 2014-12-04 20:47:17 +01:00
LICENSE Address outstanding comments from PR/47 and other cleanups. 2013-02-07 11:38:01 +01:00
MANIFEST Add MANIFEST listing 3rd party libs and versions. 2013-04-09 13:31:56 +02:00
Makefile Simplify makefiles. 2014-11-25 17:10:39 +01:00
Makefile.INCLUDE Remove spurious quotes in Makefile.INCLUDE. 2014-11-28 16:16:29 +01:00
README.md Update architecture diagram link in README.md. 2014-12-07 02:06:53 +01:00
build_info.go Simplify makefiles. 2014-11-25 17:10:39 +01:00
main.go Apply a giant code cleanup. 2014-12-10 16:16:49 +01:00
travis-helper.sh Use less offensive language WRT Travise. 2014-12-09 14:25:37 +01:00

README.md

Prometheus

Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

Prometheus' main distinguishing features as compared to other monitoring systems are:

  • a multi-dimensional data model (timeseries defined by metric name and set of key/value dimensions)
  • a flexible query language to leverage this dimensionality
  • no dependency on distributed storage; single server nodes are autonomous
  • timeseries collection happens via a pull model over HTTP
  • pushing timeseries is supported via an intermediary gateway
  • targets are discovered via service discovery or static configuration
  • multiple modes of graphing and dashboarding support
  • federation support coming soon

Architecture overview

Install

There are various ways of installing Prometheus.

Precompiled packages

We plan to provide precompiled binaries for various platforms and even packages for common Linux distributions soon. Once those are offered, it will be the recommended way of installing Prometheus.

Use make

In most cirumstances, the following should work:

$ make build
$ ./prometheus -config.file=documentation/examples/prometheus.conf

The above requires a number of common tools to be installed, namely curl, git, gzip, hg (Mercurial CLI), sed, xxd. Should you need to change any of the protocol buffer definition files (*.proto), you also need the protocol buffer compiler protoc, v2.5.0 or higher, in your $PATH.

Everything else will be downloaded and installed into a staging environment in the .build sub-directory. That includes a Go development environment of the appropriate version.

The Makefile offers a number of useful targets. Some examples:

  • make test runs tests.
  • make tarball creates a tarball with the binary for distribution.
  • make race_condition_run compiles and runs a binary with the race detector enabled. To pass arguments when running Prometheus this way, set the ARGUMENTS environment variable (e.g. ARGUMENTS="-config.file=./prometheus.conf" make race_condition_run).

Use your own Go development environment

Using your own Go development environment with the usual tooling is possible, too, but you have to take care of various generated files (usually by running make in the respective sub-directory):

  • Compiling the protocol buffer definitions in config (only if you have changed them).
  • Generating the parser and lexer code in rules (only if you have changed parser.y or lexer.l).
  • The files.go blob in web/blob, which embeds the static web content into the binary.

Furthermore, the build info (see build_info.go) will not be populated if you simply run go build. You have to pass in command line flags as defined in Makefile.INCLUDE (see ${BUILDFLAGS}) to do that.

More information

  • The source code is periodically indexed: Prometheus Core.
  • You will find a Travis CI configuration in .travis.yml.
  • All of the core developers are accessible via the Prometheus Developers Mailinglist and the #prometheus channel on irc.freenode.net.

Contributing

Refer to CONTRIBUTING.md

License

Apache License 2.0, see LICENSE.