RepoMirrors
/
prometheus
mirror of https://github.com/prometheus/prometheus
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
1,308 Commits 245 Branches 436 Tags 655 MiB
Go 85.3%
TypeScript 13.4%
Yacc 0.4%
Shell 0.2%
SCSS 0.2%
Other 0.2%
Go to file
Julius Volz b3978fe869 Fix Rickshaw/D3 version mismatch. 
When Rickshaw was updated to 1.5.1 in
fd43daf82e,
the Rickshaw upstream package now contained 3 different D3 files:

d3.min.js
d3.v2.js
d3.v3.js

For details on why that is, see
https://groups.google.com/forum/#!topic/d3-js/lXQgKA7mtEw

For the 1.5.1 Rickshaw to work properly (being able to format dates with
D3 without causing a JS error), it needs d3.v2.js or d3.v3.js, not the
d3.min.js one. I chose to update us to d3.v3.js now, since that is the
most recent and minified version, and I didn't see any problems with it
(also, the current Rickshaw examples are using that D3 version).

Currently, displaying graphs with a range >14d is broken. This fixes
that.
 		2015-02-02 23:41:36 +01:00
.build Simplify makefiles. 2014-11-25 17:10:39 +01:00
Godeps Vendor external dependencies with godep. 2015-01-09 12:00:42 +01:00
config Change autogenerated protobuf code. 2015-01-23 14:44:30 +01:00
console_libraries Fix Rickshaw/D3 version mismatch. 2015-02-02 23:41:36 +01:00
consoles Add cassandra console. 2015-01-30 11:36:14 +00:00
documentation Update architecture diagram and include source file. 2014-12-23 14:04:58 +01:00
notification More efficient JSON query result format. 2015-01-26 13:06:22 +01:00
retrieval Clean up license issues. 2015-01-21 20:07:45 +01:00
rules Fix rule manager shutdown. 2015-01-29 15:05:10 +01:00
stats Clean up license issues. 2015-01-21 20:07:45 +01:00
storage Remove labels on persist error counter. 2015-02-01 14:03:34 +01:00
templates Clean up license issues. 2015-01-21 20:07:45 +01:00
tools Clean up license issues. 2015-01-21 20:07:45 +01:00
utility Improve comments about embedding. 2015-02-02 12:37:39 +01:00
web Fix Rickshaw/D3 version mismatch. 2015-02-02 23:41:36 +01:00
.gitignore Upgrade to Go 1.4 2014-12-15 14:05:43 +01: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
AUTHORS.md Tweak AUTHORS. 2015-01-22 14:12:26 +01:00
CHANGELOG.md Cut release 0.10.0. 2015-01-26 15:35:57 +01:00
CONTRIBUTING.md Update CONTRIBUTING.md. 2015-01-22 15:07:20 +01:00
Dockerfile Set console paths correctly 2015-01-28 19:52:32 +01:00
LICENSE Clean up license issues. 2015-01-21 20:07:45 +01:00
Makefile Merge pull request #462 from brian-brazil/godeps-format 2015-01-22 18:15:16 +01:00
Makefile.INCLUDE Use https:// GOURL 2015-01-31 23:17:56 +01:00
NOTICE Clean up license issues. 2015-01-21 20:07:45 +01:00
README.md Fixed the link of the Travis build status image. 2015-01-27 14:43:46 +01:00
VERSION Also update VERSION file. 2015-01-26 15:52:34 +01:00
build_info.go Clean up license issues. 2015-01-21 20:07:45 +01:00
main.go Clean up license issues. 2015-01-21 20:07:45 +01:00
travis-helper.sh Clean up license issues. 2015-01-21 20:07:45 +01:00

README.md

Prometheus Build Status

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.