pull/3628/merge
ANISHSAJIKUMAR 2 weeks ago committed by GitHub
commit f2a6c5958c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
  1. 2
      docs/TIME.md
  2. 2
      docs/V0_16_UPGRADE_GUIDE.md
  3. 2
      docs/node-mixin/config.libsonnet
  4. 4
      end-to-end-test.sh

@ -4,7 +4,7 @@
NOTE: This collector is deprecated and will be removed in the next major version release.
This collector is intended for usage with local NTP daemons including [ntp.org](http://ntp.org/), [chrony](https://chrony.tuxfamily.org/comparison.html), and [OpenNTPD](http://www.openntpd.org/).
This collector is intended for use with local NTP daemons including [ntp.org](http://ntp.org/), [chrony](https://chrony.tuxfamily.org/comparison.html), and [OpenNTPD](http://www.openntpd.org/).
Note, some chrony packages have `local stratum 10` configuration value making chrony a valid server when it is unsynchronised. This configuration makes one of the heuristics that derive `node_ntp_sanity` unreliable.

@ -14,7 +14,7 @@ We have provided a [sample recording rule set that translates old metrics to new
## Run both old and new versions simultaneously.
It's possible to run both the old and new exporter on different ports, and include an additional scrape job in Prometheus. It's recommended to enable only the collectors that have name changes that you care about.
It's possible to run both the old and new exporter on different ports, and include an additional scrape job in Prometheus. We recommend enabling only the collectors whose name changes matter to you.
[naming best practices]: https://prometheus.io/docs/practices/naming/
[sample recording rule set that translates old metrics to new ones]: example-16-compatibility-rules.yml

@ -39,7 +39,7 @@
// Some of the alerts are meant to fire if a critical failure of a
// node is imminent (e.g. the disk is about to run full). In a
// true “cloud native” setup, failures of a single node should be
// true “cloud native” deployment, failures of a single node should be
// tolerated. Hence, even imminent failure of a single node is no
// reason to create a paging alert. However, in practice there are
// still many situations where operators like to get paged in time

@ -313,10 +313,10 @@ trap finish EXIT
get() {
if command -v curl > /dev/null 2>&1
then
curl -s -f "$@"
curl -k -s -f "$@"
elif command -v wget > /dev/null 2>&1
then
wget -O - "$@"
wget --no-check-certificate -qO - "$@"
else
echo "Neither curl nor wget found"
exit 1

Loading…
Cancel
Save