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: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,11 @@
2
2
3
3
All notable changes to this project will be documented in this file.
4
4
5
+
# Unreleased
6
+
7
+
- New feature ([#1153](https://github.com/open-telemetry/weaver/issues/1153)) - Live-check now has a `/health` endpoint that can be used in long-running scenarios to confirm readiness and liveness of the live-check server. ([#1193](https://github.com/open-telemetry/weaver/pull/1193) by @jerbly)
8
+
- New feature ([#1100](https://github.com/open-telemetry/weaver/issues/1100)) - Set `--output=http` to have live-check send its report as the response to `/stop`. ([#1193](https://github.com/open-telemetry/weaver/pull/1193) by @jerbly)
9
+
5
10
# [0.21.2] - 2026-02-03
6
11
7
12
- New Experimental feature: `weaver serve` command to serve a REST API and web UI. ([#1076](https://github.com/open-telemetry/weaver/pull/1076) by @jerbly)
Copy file name to clipboardExpand all lines: crates/weaver_live_check/README.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,7 +100,7 @@ As mentioned, a list of `PolicyFinding` is returned in the report for each sampl
100
100
"level": "violation",
101
101
"id": "missing_attribute",
102
102
"message": "Attribute `hello` does not exist in the registry.",
103
-
"context": {"attribute_name": "hello"},
103
+
"context": {"attribute_name": "hello"},
104
104
"signal_name": "http.client.request.duration",
105
105
"signal_type": "metric"
106
106
}
@@ -157,9 +157,11 @@ To override the default Otel jq preprocessor provide a path to the jq file throu
157
157
158
158
## Output
159
159
160
-
The output follows existing Weaver paradigms providing overridable jinja template based processing.
160
+
The output follows existing Weaver paradigms providing overridable jinja template based processing alongside builtin standard formats.
161
161
162
-
Out-of-the-box the output is streamed (when available) to templates providing `ansi` (default) or `json` output via the `--format` option. To override streaming and only produce a report when the input is closed, use `--no-stream`. Streaming is automatically disabled if your `--output` is a path to a directory; by default, output is printed to stdout.
162
+
By default the output is streamed (when available) to an `ansi` template. Use the `--format` option to pick one of the builtin standard formats: `json`, `jsonl` and `yaml` or a template name. To override streaming and only produce a report when the input is closed, use `--no-stream`. Streaming is automatically disabled if your `--output` is a path to a directory; by default, output is printed to stdout.
163
+
164
+
Set `--output=http` to have the report sent as the response to the `/stop` endpoint on the admin port.
163
165
164
166
To provide your own custom templates use the `--templates` option.
165
167
@@ -228,7 +230,7 @@ This could be parsed for a more sophisticated way to determine pass/fail in CI f
228
230
229
231
## OTLP Log Record Emission
230
232
231
-
In addition to the templated output formats (ANSI, JSON), live check can emit policy findings as OTLP log records. This enables real-time monitoring and analysis of semantic convention validation results through OpenTelemetry observability backends.
233
+
In addition to the output formats, live check can emit policy findings as OTLP log records. This enables real-time monitoring and analysis of semantic convention validation results through OpenTelemetry observability backends.
232
234
233
235
### Enabling OTLP Emission
234
236
@@ -257,16 +259,19 @@ Each policy finding is emitted as an OTLP log record with the following structur
257
259
**Body**: The finding message (e.g., "Required attribute 'server.address' is not present.")
258
260
259
261
**Severity**:
262
+
260
263
-`Error` (17) for `violation` level findings
261
264
-`Warn` (13) for `improvement` level findings
262
265
-`Info` (9) for `information` level findings
263
266
264
267
**Event Name**: `weaver.live_check.finding`
265
268
266
269
**Resource Attributes**:
270
+
267
271
-`service.name`: set by OTEL_SERVICE_NAME or OTEL_RESOURCE_ATTRIBUTES environment variables, defaulting to `weaver`
268
272
269
273
**Log Attributes**:
274
+
270
275
-`weaver.finding.id`: Finding type identifier (e.g., "required_attribute_not_present")
271
276
-`weaver.finding.level`: Finding level as string ("violation", "improvement", "information")
272
277
-`weaver.finding.context.<key>`: Key-value pairs provided in the context. Each pair is recorded as a single attribute.
0 commit comments