This project is mirrored from https://github.com/prometheus/prometheus.git. Updated .
  1. 15 Sep, 2020 1 commit
  2. 27 Jul, 2020 1 commit
  3. 22 Jun, 2020 1 commit
  4. 21 Jun, 2020 1 commit
  5. 17 Jun, 2020 1 commit
  6. 11 Apr, 2020 1 commit
  7. 10 Apr, 2020 1 commit
  8. 25 Feb, 2020 1 commit
  9. 28 Oct, 2019 1 commit
    • React UI: Serve React UI under /new (#6229) · e8027ba5
      This makes React UI URLs look nicer than the previous
      /static/graph-new/app.html, but internally still serves all React UI
      files from the compiled-in static assets directory.
      
      Also, to allow future usage of the React / Reach router, we need to
      serve the main React app's index.html on certain sub-paths that
      correspond to current Prometheus's UI pages, instead of trying to serve
      actual files that match the provided path name.
      Signed-off-by: 's avatarJulius Volz <julius.volz@gmail.com>
      Julius Volz authored
  10. 17 Oct, 2019 1 commit
  11. 03 May, 2019 1 commit
  12. 18 Apr, 2019 1 commit
  13. 17 Apr, 2019 1 commit
  14. 11 Apr, 2019 1 commit
  15. 04 Apr, 2019 1 commit
  16. 15 Jan, 2019 1 commit
  17. 05 Oct, 2018 1 commit
    • proto: Allow reproducible proto generation. · c3434a39
      Current way of setting prometheus project to generate repo is tedious.
      If you just go install packages described in README.md
      it ends up with those (non buildable code)
      ```
      ../../../prompb/remote.pb.go:61:34: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ../../../prompb/remote.pb.go:109:33: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ../../../prompb/remote.pb.go:164:34: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ../../../prompb/remote.pb.go:214:27: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ../../../prompb/remote.pb.go:284:33: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ```
      The issue is that the guide presented in proto folder is asking to
      install some GO packages. It does not mention from what version and
      there is strong mismatch between those used to generate proto and those
      that are vendored and used to run the code later...
      The particular outdated packages in vendor are:
      `github.com/gogo/protobuf` and `google.golang.org/grpc`.
      
      Just updating vendor would be not enough, as it would only tmp fix.
      I propose adding script that will parse version from vendor.json and install correct version.
      
      Changes:
      - Added script that uses packages in *exactly* the same version the Go code is build against later.
      - Regenerated proto with those pinned deps.
      - Updated REAMDE.md
      - Added `make proto`Current way of setting prometheus project to generate code from proto files is tedious.
      If you just go install packages described in README.md, it ends up with this (non buildable code)
      ```
      ../../../prompb/remote.pb.go:61:34: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ../../../prompb/remote.pb.go:109:33: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ../../../prompb/remote.pb.go:164:34: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ../../../prompb/remote.pb.go:214:27: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ../../../prompb/remote.pb.go:284:33: undefined: "github.com/prometheus/prometheus/vendor/github.com/gogo/protobuf/proto".InternalMessageInfo
      ```
      The issue is that the guide presented in proto folder is asking to install some GO packages. It does not mention from what version and there is strong mismatch between those used to generate proto and those that are vendored and used to run the code later...
      The particular outdated packages in vendor are:
      `github.com/gogo/protobuf` and `google.golang.org/grpc`.
      
      Just updating vendor would be not enough, as it would only tmp fix.
      I propose adding script that will parse version from vendor.json and install correct version.
      
      Changes:
      - Added script that uses packages in *exactly* the same version the Go code is build against later.
      - Regenerated proto with those pinned deps.
      - Updated REAMDE.md
      - Added `make proto`
      Signed-off-by: 's avatarBartek Plotka <bwplotka@gmail.com>
      Bartek Plotka authored
  18. 19 Apr, 2018 1 commit
  19. 01 Mar, 2018 1 commit
  20. 27 Feb, 2018 1 commit
    • Cleanup licence check script (#3893) · e392b9a1
      * Cleanup licence check script
      
      * `echo -e` is not supported by POSIX shell.
      * Add a license to the check script.
      * Split out license check loop into function for clarity.
      
      * Exit 1
      Ben Kochie authored
  21. 17 Feb, 2018 1 commit
  22. 30 Nov, 2017 1 commit
  23. 02 Nov, 2017 1 commit
  24. 10 Jul, 2017 1 commit
  25. 18 Apr, 2016 1 commit
  26. 13 Apr, 2016 1 commit
  27. 05 Apr, 2016 1 commit
  28. 08 Mar, 2016 1 commit
  29. 05 Mar, 2016 1 commit
  30. 20 Feb, 2016 1 commit
  31. 27 Jan, 2016 2 commits
  32. 20 Jan, 2016 1 commit
  33. 18 Sep, 2015 2 commits
  34. 17 Sep, 2015 1 commit
  35. 10 Jun, 2015 1 commit
    • Building without a Makefile (on Windows) · a081c943
      Main changes:
      
      - Switched to using `go-bindata` in place of `scripts/embed-static.sh`.
      - Support for building Prometheus without a `Makefile`.
      - Minor typo fix to make Prometheus build on Windows (without Makefiles).
      
      Please note that this does not mean that prometheus will work on Windows.
      There are still failing tests!
      Sindre Myren authored
  36. 01 Jun, 2015 1 commit