You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/_index.md
+22-7Lines changed: 22 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,26 +8,41 @@ The main new features of the 1.0.0 release are:
8
8
9
9
-**Prometheus native histograms:** Support for the new Prometheus histogram type.
10
10
-**OpenTelemetry Exporter:** Push metrics in OTLP format to an OpenTelemetry endpoint.
11
-
-**Runtime configuration:** Configure metrics, exporters, and more at runtime using a properties file or system properties.
11
+
-**Runtime configuration:** Configure metrics, exporters, and more at runtime using a properties
12
+
file or system properties.
12
13
13
14
**Documentation and Examples**
14
15
15
-
In addition to this documentation page we created an [examples/](https://github.com/prometheus/client_java/tree/main/examples) directory with end-to-end scenarios (Docker compose) illustrating new features.
16
+
In addition to this documentation page we created an [examples/](https://github.com/prometheus/client_java/tree/main/examples) directory with end-to-end
17
+
scenarios (Docker compose) illustrating new features.
16
18
17
19
**Performance Benchmarks**
18
20
19
-
Initial performance benchmarks are looking great: All core metric types (including native histograms) allow concurrent updates, so if you instrument a performance critical Web service that utilizes all processor cores in parallel the metrics library will not introduce additional synchronization. See Javadoc comments in [benchmarks/](https://github.com/prometheus/client_java/tree/main/benchmarks) for benchmark results.
21
+
Initial performance benchmarks are looking great: All core metric types (including native
22
+
histograms) allow concurrent updates, so if you instrument a performance critical Web service
23
+
that utilizes all processor cores in parallel the metrics library will not introduce additional
24
+
synchronization. See Javadoc comments in
25
+
[benchmarks/](https://github.com/prometheus/client_java/tree/main/benchmarks) for benchmark results.
20
26
21
27
**More Info**
22
28
23
-
The Grafana Labs Blog has a post [Introducing the Prometheus Java Client 1.0.0](https://grafana.com/blog/2023/09/27/introducing-the-prometheus-java-client-1.0.0/) with a good overview of the release.
29
+
The Grafana Labs Blog has a post [Introducing the Prometheus Java Client 1.0.0](https://grafana.com/blog/2023/09/27/introducing-the-prometheus-java-client-1.0.0/) with a
30
+
good overview of the release.
24
31
25
-
There will also be a presentation at the [PromCon](https://promcon.io) conference on 29 Sep 2023. Tune in to the live stream on [https://promcon.io](https://promcon.io) or watch the recording on YouTube.
32
+
There will also be a presentation at the [PromCon](https://promcon.io) conference on 29 Sep 2023.
33
+
Tune in to the live stream on [https://promcon.io](https://promcon.io)
34
+
or watch the recording on YouTube.
26
35
27
36
**For users of the 0.16.0 version and older**
28
37
29
-
Updating to the 1.0.0 version is a breaking change. However, there's a `prometheus-metrics-simpleclient-bridge` module available that allows you to use your existing simpleclient 0.16.0 metrics with the new 1.0.0 `PrometheusRegistry`. So you don't need to upgrade your instrumentation code, you can keep using your existing metrics. See the [compatibility > simpleclient](https://prometheus.github.io/client_java/migration/simpleclient/) in the menu on the left.
38
+
Updating to the 1.0.0 version is a breaking change. However, there's a
39
+
`prometheus-metrics-simpleclient-bridge` module available that allows you to use your existing
40
+
simpleclient 0.16.0 metrics with the new 1.0.0 `PrometheusRegistry`.
41
+
So you don't need to upgrade your instrumentation code, you can keep using your existing metrics.
42
+
See the [compatibility > simpleclient](https://prometheus.github.io/client_java/migration/simpleclient/) in the menu on the left.
30
43
31
44
The pre 1.0.0 code is now maintained on the [simpleclient](https://github.com/prometheus/client_java/tree/simpleclient) feature branch.
32
45
33
-
Not all `simpleclient` modules from 0.16.0 are included in the initial 1.0.0 release. Over the next couple of weeks we will work on porting the remaining modules, starting with `pushgateway` and the Servlet filter.
46
+
Not all `simpleclient` modules from 0.16.0 are included in the initial 1.0.0 release.
47
+
Over the next couple of weeks we will work on porting the remaining modules,
48
+
starting with `pushgateway` and the Servlet filter.
There's one special feature about metric properties: You can set a property for one specific metric only by specifying the metric name. Example: Let's say you have a histogram named `latency_seconds`.
65
+
There's one special feature about metric properties: You can set a property for one specific
66
+
metric only by specifying the metric name. Example:
67
+
Let's say you have a histogram named `latency_seconds`.
@@ -129,12 +136,15 @@ This works for all Metrics properties.
129
136
(2) Format: `key1=value1,key2=value2`<br>
130
137
(3) Format: `key1=value1,key2=value2`
131
138
132
-
Many of these attributes can alternatively be configured via OpenTelemetry environment variables, like `OTEL_EXPORTER_OTLP_ENDPOINT`. The Prometheus metrics library has support for OpenTelemetry environment variables. See Javadoc for details.
139
+
Many of these attributes can alternatively be configured via OpenTelemetry environment variables,
140
+
like `OTEL_EXPORTER_OTLP_ENDPOINT`.
141
+
The Prometheus metrics library has support for OpenTelemetry environment variables.
Copy file name to clipboardExpand all lines: docs/content/exporters/httpserver.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,15 +3,17 @@ title: HTTPServer
3
3
weight: 3
4
4
---
5
5
6
-
The `HTTPServer` is a standalone server for exposing a metric endpoint. A minimal example application for `HTTPServer` can be found in the [examples](https://github.com/prometheus/client_java/tree/1.0.x/examples) directory.
6
+
The `HTTPServer` is a standalone server for exposing a metric endpoint. A minimal example
7
+
application for `HTTPServer` can be found in the [examples](https://github.com/prometheus/client_java/tree/1.0.x/examples) directory.
7
8
8
9
```java
9
10
HTTPServer server =HTTPServer.builder()
10
11
.port(9400)
11
12
.buildAndStart();
12
13
```
13
14
14
-
By default, `HTTPServer` binds to any IP address, you can change this with [hostname()](</client_java/api/io/prometheus/metrics/exporter/httpserver/HTTPServer.Builder.html#hostname(java.lang.String)>) or [inetAddress()](</client_java/api/io/prometheus/metrics/exporter/httpserver/HTTPServer.Builder.html#inetAddress(java.net.InetAddress)>).
15
+
By default, `HTTPServer` binds to any IP address, you can change this with
16
+
[hostname()](</client_java/api/io/prometheus/metrics/exporter/httpserver/HTTPServer.Builder.html#hostname(java.lang.String)>) or [inetAddress()](</client_java/api/io/prometheus/metrics/exporter/httpserver/HTTPServer.Builder.html#inetAddress(java.net.InetAddress)>).
However, this requires that the JVM can validate the server certificate.
110
110
111
-
If you want to skip certificate verification, you need to provide your own [HttpConnectionFactory](/client_java/api/io/prometheus/metrics/exporter/pushgateway/HttpConnectionFactory.html).
111
+
If you want to skip certificate verification, you need to provide your own
The `PushGatewayTestApp` in `integration-tests/it-pushgateway` has a complete example of this.
113
114
114
115
## Configuration Properties
115
116
116
-
The [PushGateway](/client_java/api/io/prometheus/metrics/exporter/pushgateway/PushGateway.html) supports a couple of properties that can be configured at runtime. See [config](../config/config.md).
117
+
The [PushGateway](/client_java/api/io/prometheus/metrics/exporter/pushgateway/PushGateway.html) supports a couple of properties that can be configured at runtime.
0 commit comments