The Prometheus monitoring system and time series database.

Last update: Jan 10, 2023

Overview

Prometheus

Visit prometheus.io for the full documentation, examples and guides.

Prometheus, a Cloud Native Computing Foundation project, 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 when specified conditions are observed.

The features that distinguish Prometheus from other metrics and monitoring systems are:

A multi-dimensional data model (time series defined by metric name and set of key/value dimensions)
PromQL, a powerful and flexible query language to leverage this dimensionality
No dependency on distributed storage; single server nodes are autonomous
An HTTP pull model for time series collection
Pushing time series is supported via an intermediary gateway for batch jobs
Targets are discovered via service discovery or static configuration
Multiple modes of graphing and dashboarding support
Support for hierarchical and horizontal federation

Architecture overview

Install

There are various ways of installing Prometheus.

Precompiled binaries

Precompiled binaries for released versions are available in the download section on prometheus.io. Using the latest production release binary is the recommended way of installing Prometheus. See the Installing chapter in the documentation for all the details.

Docker images

Docker images are available on Quay.io or Docker Hub.

You can launch a Prometheus container for trying it out with

$ docker run --name prometheus -d -p 127.0.0.1:9090:9090 prom/prometheus

Prometheus will now be reachable at http://localhost:9090/.

Building from source

To build Prometheus from source code, You need:

You can directly use the go tool to download and install the prometheus and promtool binaries into your GOPATH:

$ GO111MODULE=on go install github.com/prometheus/prometheus/cmd/...
$ prometheus --config.file=your_config.yml

However, when using go install to build Prometheus, Prometheus will expect to be able to read its web assets from local filesystem directories under web/ui/static and web/ui/templates. In order for these assets to be found, you will have to run Prometheus from the root of the cloned repository. Note also that these directories do not include the new experimental React UI unless it has been built explicitly using make assets or make build.

An example of the above configuration file can be found here.

You can also clone the repository yourself and build using make build, which will compile in the web assets so that Prometheus can be run from anywhere:

$ mkdir -p $GOPATH/src/github.com/prometheus
$ cd $GOPATH/src/github.com/prometheus
$ git clone https://github.com/prometheus/prometheus.git
$ cd prometheus
$ make build
$ ./prometheus --config.file=your_config.yml

The Makefile provides several targets:

build: build the prometheus and promtool binaries (includes building and compiling in web assets)
test: run the tests
test-short: run the short tests
format: format the source code
vet: check the source code for common errors
assets: build the new experimental React UI

Building the Docker image

The make docker target is designed for use in our CI system. You can build a docker image locally with the following commands:

$ make promu
$ promu crossbuild -p linux/amd64
$ make npm_licenses
$ make common-docker-amd64

NB if you are on a Mac, you will need gnu-tar.

React UI Development

For more information on building, running, and developing on the new React-based UI, see the React app's README.md.

More information

The source code is periodically indexed, but due to an issue with versioning, the "latest" docs shown on Godoc are outdated. Instead, you can use the docs for v2.31.1.
You will find a CircleCI configuration in .circleci/config.yml.
See the Community page for how to reach the Prometheus developers and users on various communication channels.

Contributing

Refer to CONTRIBUTING.md

License

Apache License 2.0, see LICENSE.

Comments

TSDB data import tool for OpenMetrics format.

Created a tool to import data formatted according to the Prometheus exposition format. The tool can be accessed via the TSDB CLI.

closes prometheus/prometheus#535

Signed-off-by: Dipack P Panjabi [email protected]

(Port of https://github.com/prometheus/tsdb/pull/671)

opened by dipack95 126
Add mechanism to perform bulk imports

Currently the only way to bulk-import data is a hacky one involving client-side timestamps and scrapes with multiple samples per time series. We should offer an API for bulk import. This relies on https://github.com/prometheus/prometheus/issues/481.

EDIT: It probably won't be an web-based API in Prometheus, but a command-line tool.
kind/enhancement priority/P2 component/tsdb

opened by juliusv 112
Create a section ANNOTATIONS with user-defined payload and generalize RUNBOOK, DESCRIPTION, SUMMARY into fields therein.
RUNBOOK was added in a hurry in #843 for an internal demo of one of our users, which didn't give it enough time to be fully discussed. The demo has been done, so we can reconsider this.

I think we should revert this change, and remove RUNBOOK:

Our general policy is that if it can be done with labels, do it with labels

All notification methods in the alertmanager will need extra code to deal with this

In future, all alertmanager notification templates will need extra code to deal with this

In general, all user code touching the alertmanager will need extra code to deal with this

This presumes a certain workflow in that you have something called a "runbook" (and not any other name - playbook is also common) and that you have exactly one of them

Runbooks are not a fundamental aspect of an alert, are not in use by all of our users and thus I don't believe they meet the bar for first-class support within prometheus. This is especially true considering that they don't add anything that isn't already possible with labels.
opened by brian-brazil 102
Implement strategies to limit memory usage.

Currently, Prometheus simply limits the chunks in memory to a fixed number.

However, this number doesn't directly imply the total memory usage as many other things take memory as well.

Prometheus could measure its own memory consumption and (optionally) evict chunks early if it needs too much memory.

It's non-trivial to measure "actual" memory consumption in a platform independent way.
kind/enhancement

opened by beorn7 90
'@ ' modifier
This PR implements @ <timestamp> modifier as per this design doc.

An example query:

rate(process_cpu_seconds_total[1m]) and topk(7, rate(process_cpu_seconds_total[1h] @ 1234))

which ranks based on last 1h rate and w.r.t. unix timestamp 1234 but actually plots the 1m rate.

Closes #7903

This PR is to be followed up with an easier way to represent the start, end, range of a query in PromQL so that we could do @ <end>, metric[<range>] easily.
opened by codesome 88
Port isolation from old TSDB PR

The original PR was https://github.com/prometheus/tsdb/pull/306 .

I tried to carefully adjust to the new world order, but please give this a very careful review, especially around iterator reuse (marked with a TODO).

On the bright side, I definitely found and fixed a bug in txRing.
prombench

opened by beorn7 78
2.3.0 significatnt memory usage increase.
Bug Report

What did you do? Upgraded to 2.3.0

What did you expect to see? General improvements.

What did you see instead? Under which circumstances? Memory usage, possibly driven by queries, has considerably increased. Upgrade at 09:27, the memory usage drops on the graph after then are from container restarts due to OOM.

container_memory_usage_bytes

Environment

Prometheus in kubernetes 1.9

System information: Standard docker containers, on docker kubelet on linux.

Prometheus version: 2.3.0 insert output of prometheus --version here

kind/bug
opened by tcolgate 77
Support for environment variable substitution in configuration file

I think that would be a good idea to substitute environment variables in the configuration file.

That could be done really easily using os.ExpandEnv on configuration string when loading configuration string.

That would be much easier to substitute environment variables only on configuration values. go -ini provides a valueMapper but yaml.v2 doesn't have such mechanism.

opened by dopuskh3 72
React UI: Implement more sophisticated autocomplete
It would be great to have more sophisticated expression field autocompletion in the new React UI.

Currently it only autocompletes metric names, and only when the expression field doesn't contain any other sub-expressions yet.

Things that would be nice to autocomplete:

metric names anywhere within an expression

label names

label values

function names

etc.

For autocomplete functionality not to annoy users, it needs to be as highly performant, correct, and unobtrusive as possible. Grafana does many things right here already, but they also have a few really annoying bugs, like inserting closing parentheses in incorrect locations of an expression.

Currently @slrtbtfs has indicated interest in building a language-server-based autocomplete implementation.
component/ui priority/P3 kind/feature
opened by juliusv 69
Benchmark tsdb master
DO NOT MERGE

Benchmark 1

Benchmark the following PRs against 2.11.1

For queries: https://github.com/prometheus/tsdb/pull/642

For compaction: https://github.com/prometheus/tsdb/pull/643 https://github.com/prometheus/tsdb/pull/654 https://github.com/prometheus/tsdb/pull/653

Opening block: https://github.com/prometheus/tsdb/pull/645

Results

Did not test for compaction from on-disk blocks. Could not really see the allocation optimizations in compaction, that might be because the savings are mostly in the number of allocations and not the size of allocation (size is what is showed in the dashboards). That would mean CPU to be saved, but couldn't make a huge difference, but a slight increase in gap during compaction.

The gains looked good in

Allocations

CPU (because of allocations?)

RSS was also lower (upto 10 GiB lower! ~60 vs ~70).

Also a tiny-good improvement in query inner_eval times.

Compaction time (this should help the increase in compaction time that https://github.com/prometheus/tsdb/pull/627 is going to bring).

System load.

And bad in

result_sort for the queries. Not sure why.

Benchmark 2

Benchmark https://github.com/prometheus/tsdb/pull/627 (which includes all the PRs from above Benchmark 1) against 2.11.1
opened by codesome 65
M-map full chunks of Head from disk
tl-dr desc for the PR from @krasi-georgiev

When appending to the head and a chunk is full it is flushed to the disk and m-mapped (memory mapped) to free up memory

Prom startup now happens in these stages

Iterate the m-maped chunks from disk and keep a map of series reference to its slice of mmapped chunks.

Iterate the WAL as usual. Whenever we create a new series, look for it's mmapped chunks in the map created before and add it to that series.

If a head chunk is corrupted the currpted one and all chunks after that are deleted and the data after the corruption is recovered from the existing WAL which means that a corruption in m-mapped files results in NO data loss.

Mmaped chunks format - main difference is that the chunk for mmaping now also includes series reference because there is no index for mapping series to chunks. The block chunks are accessed from the index which includes the offsets for the chunks in the chunks file - example - chunks of series ID have offsets 200, 500 etc in the chunk files. In case of mmaped chunks, the offsets are stored in memory and accessed from that. During WAL replay, these offsets are restored by iterating all m-mapped chunks as stated above by matching the series id present in the chunk header and offset of that chunk in that file.

Prombench results

WAL Replay

1h Wal reply time 30% less wal reply time - 4m31 vs 3m36 2h Wal reply time 20% less wal reply time - 8m16 vs 7m

Memory During WAL Replay

High Churn 10-15% less RAM - 32gb vs 28gb 20% less RAM after compaction 34gb vs 27gb No Churn 20-30% less RAM - 23gb vs 18gb 40% less RAM after compaction 32.5gb vs 20gb

Screenshots are in this comment

Prerequisite: https://github.com/prometheus/prometheus/pull/6830 (Merged)

Closes https://github.com/prometheus/prometheus/issues/6377. More info in the linked issue and the doc in that issue and the doc inside that doc inside that issue :)

[x] Add tests

[x] Explore possible ways to get rid of new globals added in head.go

[x] Wait for https://github.com/prometheus/prometheus/pull/6830 to be merged

[x] Fix windows tests

prombench
opened by codesome 64
Bump github.com/hetznercloud/hcloud-go from 1.38.0 to 1.39.0
Bumps github.com/hetznercloud/hcloud-go from 1.38.0 to 1.39.0.

Release notes

Sourced from github.com/hetznercloud/hcloud-go's releases.

v1.39.0

1.39.0 (2022-12-29)

Features

Use generics to get pointers to types (#219) (a5cd797)

Bug Fixes

deprecate PricingPrimaryIPTypePrice.Datacenter for Location (#222) (e0e5a1e)

Changelog

Sourced from github.com/hetznercloud/hcloud-go's changelog.

1.39.0 (2022-12-29)

Features

Use generics to get pointers to types (#219) (a5cd797)

Bug Fixes

deprecate PricingPrimaryIPTypePrice.Datacenter for Location (#222) (e0e5a1e)

Commits

5527a41 chore(main): release 1.39.0 (#224)

eb2f1c9 ci: setup release-please to automate new releases (#223)

e0e5a1e fix: deprecate PricingPrimaryIPTypePrice.Datacenter for Location (#222)

a5cd797 feat: Use generics to get pointers to types (#219)

69b0a11 ci: test against actually supported Go versions (#220)

See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependencies go
opened by dependabot[bot] 0
Bump github.com/prometheus/alertmanager from 0.24.0 to 0.25.0
Bumps github.com/prometheus/alertmanager from 0.24.0 to 0.25.0.

Release notes

Sourced from github.com/prometheus/alertmanager's releases.

0.25.0 / 2022-12-22

[CHANGE] Change the default parse_mode value from MarkdownV2 to HTML for Telegram. #2981

[CHANGE] Make api_url field optional for Telegram. #2981

[CHANGE] Use CanonicalMIMEHeaderKey instead of TitleCasing for email headers. #3080

[CHANGE] Reduce the number of notification logs broadcasted between peers by expiring them after (2 * repeat interval). #2982

[FEATURE] Add proxy_url support for OAuth2 in HTTP client configuration. #3010

[FEATURE] Reload TLS certificate and key from disk when updated. #3168

[FEATURE] Add Discord integration. #2948

[FEATURE] Add Webex integration. #3132

[ENHANCEMENT] Add --web.systemd-socket flag to systemd socket activation listeners instead of port listeners (Linux only). #3140

[ENHANCEMENT] Add enable_http2 support in HTTP client configuration. #3010

[ENHANCEMENT] Add min_version support to select the minimum TLS version in HTTP client configuration. #3010

[ENHANCEMENT] Add max_version support to select the maximum TLS version in HTTP client configuration. #3168

[ENHANCEMENT] Emit warning logs when truncating messages in notifications. #3145

[ENHANCEMENT] Add --data.maintenance-interval flag to define the interval between the garbage collection and snapshotting to disk of the silences and the notification logs. #2849

[ENHANCEMENT] Support HEAD method for the /-/healty and /-/ready endpoints. #3039

[ENHANCEMENT] Truncate messages with the … ellipsis character instead of the 3-dots string .... #3072

[ENHANCEMENT] Add support for reading global and local SMTP passwords from files. #3038

[ENHANCEMENT] Add Location support to time intervals. #2782

[ENHANCEMENT] UI: Add 'Link' button to alerts in list. #2880

[ENHANCEMENT] Add the source field to the PagerDuty configuration. #3106

[ENHANCEMENT] Add support for reading PagerDuty routing and service keys from files. #3107

[ENHANCEMENT] Log response details when notifications fail for Webhooks, Pushover and VictorOps. #3103

[ENHANCEMENT] UI: Allow to choose the first day of the week as Sunday or Monday. #3093

[ENHANCEMENT] Add support for reading VictorOps API key from file. #3111

[ENHANCEMENT] Support templating for Opsgenie's responder type. #3060

[BUGFIX] Fail configuration loading if api_key and api_key_file are defined at the same time. #2910

[BUGFIX] Fix the alertmanager_alerts metric to avoid counting resolved alerts as active. Also added a new alertmanager_marked_alerts metric that retain the old behavior. #2943

[BUGFIX] Trim contents of Slack API URLs when reading from files. #2929

[BUGFIX] amtool: Avoid panic when the label value matcher is empty. #2968

[BUGFIX] Fail configuration loading if api_url is empty for OpsGenie. #2910

[BUGFIX] Fix email template for resolved notifications. #3166

[BUGFIX] Use the HTML template engine when the parse mode is HTML for Telegram. #3183

0.25.0-rc.2 / 2022-12-19

[CHANGE] Change the default parse_mode value from MarkdownV2 to HTML for Telegram. #2981

[CHANGE] Make api_url field optional for Telegram. #2981

[CHANGE] Use CanonicalMIMEHeaderKey instead of TitleCasing for email headers. #3080

[CHANGE] Reduce the number of notification logs broadcasted between peers by expiring them after (2 * repeat interval). #2982

[FEATURE] Add proxy_url support for OAuth2 in HTTP client configuration. #3010

[FEATURE] Reload TLS certificate and key from disk when updated. #3168

[FEATURE] Add Discord integration. #2948

[FEATURE] Add Webex integration. #3132

[ENHANCEMENT] Add --web.systemd-socket flag to systemd socket activation listeners instead of port listeners (Linux only). #3140

[ENHANCEMENT] Add enable_http2 support in HTTP client configuration. #3010

[ENHANCEMENT] Add min_version support to select the minimum TLS version in HTTP client configuration. #3010

[ENHANCEMENT] Add max_version support to select the maximum TLS version in HTTP client configuration. #3168

[ENHANCEMENT] Emit warning logs when truncating messages in notifications. #3145

[ENHANCEMENT] Add --data.maintenance-interval flag to define the interval between the garbage collection and snapshotting to disk of the silences and the notification logs. #2849

[ENHANCEMENT] Support HEAD method for the /-/healty and /-/ready endpoints. #3039

... (truncated)

Changelog

Sourced from github.com/prometheus/alertmanager's changelog.

0.25.0-rc.0 / 2022-12-16

[CHANGE] Change the default parse_mode value from MarkdownV2 to HTML for Telegram. #2981

[CHANGE] Make api_url field optional for Telegram. #2981

[CHANGE] Use CanonicalMIMEHeaderKey instead of TitleCasing for email headers. #3080

[CHANGE] Reduce the number of notification logs broadcasted between peers by expiring them after (2 * repeat interval). #2982

[FEATURE] Add proxy_url support for OAuth2 in HTTP client configuration. #3010

[FEATURE] Reload TLS certificate and key from disk when updated. #3168

[FEATURE] Add Discord integration. #2948

[FEATURE] Add Webex integration. #3132

[ENHANCEMENT] Add --web.systemd-socket flag to systemd socket activation listeners instead of port listeners (Linux only). #3140

[ENHANCEMENT] Add enable_http2 support in HTTP client configuration. #3010

[ENHANCEMENT] Add min_version support to select the minimum TLS version in HTTP client configuration. #3010

[ENHANCEMENT] Add max_version support to select the maximum TLS version in HTTP client configuration. #3168

[ENHANCEMENT] Emit warning logs when truncating messages in notifications. #3145

[ENHANCEMENT] Add --data.maintenance-interval flag to define the interval between the garbage collection and snapshotting to disk of the silences and the notification logs. #2849

[ENHANCEMENT] Support HEAD method for the /-/healty and /-/ready endpoints. #3039

[ENHANCEMENT] Truncate messages with the … ellipsis character instead of the 3-dots string .... #3072

[ENHANCEMENT] Add support for reading global and local SMTP passwords from files. #3038

[ENHANCEMENT] Add Location support to time intervals. #2782

[ENHANCEMENT] UI: Add 'Link' button to alerts in list. #2880

[ENHANCEMENT] Add the source field to the PagerDuty configuration. #3106

[ENHANCEMENT] Add support for reading PagerDuty routing and service keys from files. #3107

[ENHANCEMENT] Log response details when notifications fail for Webhooks, Pushover and VictorOps. #3103

[ENHANCEMENT] UI: Allow to choose the first day of the week as Sunday or Monday. #3093

[ENHANCEMENT] Add support for reading VictorOps API key from file. #3111

[ENHANCEMENT] Support templating for Opsgenie's responder type. #3060

[BUGFIX] Fail configuration loading if api_key and api_key_file are defined at the same time. #2910

[BUGFIX] Fix the alertmanager_alerts metric to avoid counting resolved alerts as active. Also added a new alertmanager_marked_alerts metric that retain the old behavior. #2943

[BUGFIX] Trim contents of Slack API URLs when reading from files. #2929

[BUGFIX] amtool: Avoid panic when the label value matcher is empty. #2968

[BUGFIX] Fail configuration loading if api_url is empty for OpsGenie. #2910

[BUGFIX] Fix email template for resolved notifications. #3166

Commits

258fab7 Merge pull request #3187 from simonpasquier/cut-v0.25.0

4f7c85f Cut v0.25.0

ead47cd Merge pull request #3183 from simonpasquier/fix-3061

aa6a929 telegram: use HTML template with HTML parse mode

aace20a Merge pull request #3180 from simonpasquier/fix-build-all

9226eb0 Cut v0.25.0-rc.2

4175aef Run 'build_all' job for v0.y tags

2afee51 Merge pull request #3179 from simonpasquier/cut-v0.25.0-rc.1

54bd81d Cut v0.25.0-rc.1

1eb79d9 Merge pull request #3177 from simonpasquier/fix-remote-docker-version

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependencies go
opened by dependabot[bot] 0
Bump github.com/aws/aws-sdk-go from 1.44.159 to 1.44.171
Bumps github.com/aws/aws-sdk-go from 1.44.159 to 1.44.171.

Release notes

Sourced from github.com/aws/aws-sdk-go's releases.

Release v1.44.171 (2022-12-30)

Service Client Updates

service/cloudfront: Updates service API and documentation

Extend response headers policy to support removing headers from viewer responses

service/iotfleetwise: Updates service documentation

Release v1.44.170 (2022-12-29)

Service Client Updates

service/apigateway: Updates service documentation

Documentation updates for Amazon API Gateway

service/elasticmapreduce: Updates service API and documentation

Added GetClusterSessionCredentials API to allow Amazon SageMaker Studio to connect to EMR on EC2 clusters with runtime roles and AWS Lake Formation-based access control for Apache Spark, Apache Hive, and Presto queries.

service/secretsmanager: Updates service API and documentation

Added owning service filter, include planned deletion flag, and next rotation date response parameter in ListSecrets.

service/wisdom: Updates service API and documentation

Release v1.44.169 (2022-12-28)

Service Client Updates

service/elasticache: Updates service API and documentation

This release allows you to modify the encryption in transit setting, for existing Redis clusters. You can now change the TLS configuration of your Redis clusters without the need to re-build or re-provision the clusters or impact application availability.

service/network-firewall: Updates service API and documentation

service/rds: Updates service API, documentation, waiters, paginators, and examples

This release adds support for Custom Engine Version (CEV) on RDS Custom SQL Server.

service/route53-recovery-control-config: Updates service documentation and paginators

Release v1.44.168 (2022-12-27)

Service Client Updates

service/memorydb: Updates service API, documentation, and paginators

service/transfer: Updates service API

Add additional operations to throw ThrottlingExceptions

Release v1.44.167 (2022-12-23)

Service Client Updates

service/connect: Updates service API and documentation

service/connectparticipant: Updates service API and documentation

service/detective: Updates service API and documentation

service/fsx: Updates service API and documentation

service/inspector2: Updates service API

Release v1.44.166 (2022-12-22)

... (truncated)

Commits

eb531b5 Release v1.44.171 (2022-12-30) (#4677)

3961b07 Release v1.44.170 (2022-12-29) (#4675)

00f5d7d Release v1.44.169 (2022-12-28) (#4674)

698f054 Merge pull request #4597 from eddy-aws/main

3f9c4f2 add changelog file

5ce492c Release v1.44.168 (2022-12-27) (#4673)

811c54e Release v1.44.167 (2022-12-23) (#4671)

06491f5 Release v1.44.166 (2022-12-22) (#4670)

e845746 Release v1.44.165 (2022-12-21) (#4669)

bda5744 Release v1.44.164 (2022-12-20) (#4668)

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependencies go
opened by dependabot[bot] 0
Bump github.com/prometheus/common from 0.37.0 to 0.39.0 in /documentation/examples/remote_storage
Bumps github.com/prometheus/common from 0.37.0 to 0.39.0.

Release notes

Sourced from github.com/prometheus/common's releases.

v0.39.0

[ENHANCEMENT] Add support for proxy connect headers. #409

[ENHANCEMENT] Add platform info to labels. #403

v0.37.1

[BUGFIX] Update go.mod for CVE-2022-41717 #420

v0.38.0

[FEATURE] Implement Stringer on TLSVersion (#405)

[FEATURE] Check if TLS certificate and key file have been modified (#345)

[ENHANCEMENT] Add the ability to specify the maximum acceptable TLS version (#414)

[ENHANCEMENT] Make LoadHTTPConfigFile set directory and move from tests file (#415)

[ENHANCEMENT] Get Revision from debug.BuildInfo if not explicitly set (#374)

Commits

296ec92 Merge pull request #409 from prometheus/mem/proxy_header

18281a2 Merge pull request #424 from prometheus/repo_sync

4a0d730 Add support for proxy connect headers

017dec0 Update common Prometheus files

befeabf Merge pull request #422 from prometheus/superq/add_mod_check

1bc7f65 Add platform info to labels (#403)

82accf3 Add go mod version test

00e3fd7 Merge pull request #418 from roidelapluie/go119

045094f Update deps and test with go 1.19

ddb642f Merge pull request #421 from prometheus/superq/update_sigv4

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependencies go
opened by dependabot[bot] 0
Bump github.com/Azure/azure-sdk-for-go from 65.0.0+incompatible to 67.2.0+incompatible
Bumps github.com/Azure/azure-sdk-for-go from 65.0.0+incompatible to 67.2.0+incompatible.

Release notes

Sourced from github.com/Azure/azure-sdk-for-go's releases.

v67.2.0

Deprecated Packages

github.com/Azure/azure-sdk-for-go/services/preview/workloadmonitor/mgmt/2018-08-31-preview/workloadmonitor

github.com/Azure/azure-sdk-for-go/services/preview/workloadmonitor/mgmt/2020-01-13-preview/workloadmonitor

v67.1.0

Deprecated Packages

github.com/Azure/azure-sdk-for-go/services/preview/iotspaces/mgmt/2017-10-01-preview/iotspaces

v67.0.0

New Packages

github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2022-03-01/compute

github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2022-03-02/compute

github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2022-04-04/compute

github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2022-03-03/compute

github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2022-07-02/compute

github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2022-08-01/compute

github.com/Azure/azure-sdk-for-go/services/containerservice/mgmt/2022-04-01/containerservice

github.com/Azure/azure-sdk-for-go/services/containerservice/mgmt/2022-06-01/containerservice

github.com/Azure/azure-sdk-for-go/services/containerservice/mgmt/2022-07-01/containerservice

github.com/Azure/azure-sdk-for-go/services/cosmos-db/mgmt/2022-05-15/documentdb

github.com/Azure/azure-sdk-for-go/services/cosmos-db/mgmt/2022-08-15/documentdb

github.com/Azure/azure-sdk-for-go/services/keyvault/mgmt/2022-07-01/keyvault

github.com/Azure/azure-sdk-for-go/services/kubernetesconfiguration/mgmt/2022-07-01/kubernetesconfiguration

github.com/Azure/azure-sdk-for-go/services/network/mgmt/2022-01-01/network

github.com/Azure/azure-sdk-for-go/services/network/mgmt/2022-05-01/network

github.com/Azure/azure-sdk-for-go/services/operationalinsights/mgmt/2021-06-01/operationalinsights

github.com/Azure/azure-sdk-for-go/services/preview/keyvault/mgmt/2021-11-01-preview/keyvault

github.com/Azure/azure-sdk-for-go/services/preview/maintenance/mgmt/2021-09-01-preview/maintenance

github.com/Azure/azure-sdk-for-go/services/preview/maintenance/mgmt/2022-07-01-preview/maintenance

github.com/Azure/azure-sdk-for-go/services/preview/monitor/mgmt/2016-03-01-preview/monitorlegacy

github.com/Azure/azure-sdk-for-go/services/preview/monitor/mgmt/2021-05-01-preview/diagnostics

github.com/Azure/azure-sdk-for-go/services/preview/monitor/mgmt/2021-05-01-preview/metrics

github.com/Azure/azure-sdk-for-go/services/preview/monitor/mgmt/2022-06-01-preview/insights

github.com/Azure/azure-sdk-for-go/services/preview/monitor/mgmt/2022-10-01-preview/insights

github.com/Azure/azure-sdk-for-go/services/preview/msi/mgmt/2022-01-31-preview/msi

github.com/Azure/azure-sdk-for-go/services/preview/operationalinsights/mgmt/2022-02-01-preview/operationalinsights

github.com/Azure/azure-sdk-for-go/services/preview/resourcegraph/mgmt/2021-06-01-preview/resourcegraph

github.com/Azure/azure-sdk-for-go/services/preview/servicebus/mgmt/2022-01-01-preview/servicebus

github.com/Azure/azure-sdk-for-go/services/preview/solutions/mgmt/2018-09-01-preview/managedapplications

github.com/Azure/azure-sdk-for-go/services/preview/solutions/mgmt/2020-08-21-preview/managedapplications

github.com/Azure/azure-sdk-for-go/services/preview/solutions/mgmt/2021-02-01-preview/managedapplications

github.com/Azure/azure-sdk-for-go/services/privatedns/mgmt/2020-01-01/privatedns

github.com/Azure/azure-sdk-for-go/services/privatedns/mgmt/2020-06-01/privatedns

github.com/Azure/azure-sdk-for-go/services/resources/mgmt/2017-04-01/locks

github.com/Azure/azure-sdk-for-go/services/resources/mgmt/2020-05-01/locks

github.com/Azure/azure-sdk-for-go/services/resources/mgmt/2021-01-01/resources

github.com/Azure/azure-sdk-for-go/services/resources/mgmt/2021-04-01/resources

github.com/Azure/azure-sdk-for-go/services/servicebus/mgmt/2021-11-01/servicebus

... (truncated)

Commits

e76e45c deprecated services/preview/workloadmonitor/mgmt (#19701)

db4a684 rename v67.0.1 to v67.1.0 (#19542)

7ff7f08 Release v67.0.1 (#19370)

91112b0 fix CHANGELOG.md (#19342)

e9b651b Release v67.0.0 1665469788 (#19329)

a18b433 Deprecate mgmt. track1 packages and refresh securityinsight (#18399)

f43cf08 recover (#18316)

ac1ffaf recover monitor (#18295)

144d3f0 Create legacy branch for track1 and cleanup track2 content (#18265)

931f528 Enable API review gen in CI for Go (#18235)

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependencies go
opened by dependabot[bot] 0
Bump github.com/influxdata/influxdb from 1.10.0 to 1.11.0 in /documentation/examples/remote_storage
Bumps github.com/influxdata/influxdb from 1.10.0 to 1.11.0.

Commits

ac35088 feat: include crypto diagnostics in /debug/vars output (#23948)

e484c4d chore: upgrade Go to v1.19.3 (1.x) (#23941)

e68b64c chore: make "flux-testing" public (#23935)

fd7e4aa chore: fix trace message text (#23917)

5976e41 feat: upgrade flux to v0.188.0 (#23911)

be9a3d4 fix: :db/:rp -> :dbrp, fixed create bucket, update bucket (#23898) (#23900)

9e9f1be fix: remove dead iterator (#23888)

a2fca83 fix: don't write skipped shard messages to the line protocol output destinati...

b0e44a4 fix: listBuckets properly returns wrapped response (#23879) (#23884)

cc26b76 fix: remove breaking argument validation for _fieldKeys iterator (#23875)

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependencies go
opened by dependabot[bot] 0