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: CLAUDE.md
+14-10Lines changed: 14 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,22 +12,19 @@ model/
12
12
registry_manifest.yaml # Registry manifest with OTel semconv dependency
13
13
<namespace> # Different folders, organize by functional area
14
14
tests/
15
-
valid/ # JSON5 test data expected to pass validation
16
-
invalid/ # JSON5 test data expected to fail validation
15
+
valid/ # JSON test data expected to pass validation
16
+
invalid/ # JSON test data expected to fail validation
17
17
```
18
18
19
19
## Validation
20
20
21
-
Validate the registry model using dockerized Weaver:
21
+
All validation and testing runs via Docker through the `Makefile`.
22
22
23
23
```sh
24
-
docker run --rm -v "$(pwd)/model:/model" fa4f1c6954ec registry check -r /model
25
-
```
26
-
27
-
Or if Weaver is installed locally:
28
-
29
-
```sh
30
-
weaver registry check -r ./model
24
+
make check # validate the registry model
25
+
make test# run all live-check tests
26
+
make test-valid # run only valid test cases
27
+
make test-invalid # run only invalid test cases
31
28
```
32
29
33
30
## Metric documentation workflow
@@ -45,6 +42,13 @@ The metric definitions were produced by:
45
42
- Deprecated Prometheus aliases (e.g., `dash0_spans_total`) get their own metric group entry with `deprecated: { reason: renamed, renamed_to: <otel_name> }`.
46
43
- Every metric **must** have a `unit` field compliant with [UCUM](https://ucum.org/).
47
44
45
+
## Test data maintenance
46
+
47
+
When adding, removing, or renaming test files under `tests/valid/` or `tests/invalid/`, update `tests/README.md`:
48
+
49
+
- Each test file must have a row in the README table for its domain section.
50
+
- The description should explain what the test exercises and why it is expected to pass or fail.
51
+
48
52
## Prose rules
49
53
50
54
Follow these rules when writing or editing prose in this project.
This directory contains [Weaver live-check](https://github.com/open-telemetry/weaver) sample payloads used to validate the registry model.
4
+
5
+
-`valid/` — Samples that **must pass** validation.
6
+
-`invalid/` — Samples that **must fail** validation.
7
+
8
+
## deployment
9
+
10
+
### Valid
11
+
12
+
| File | Description |
13
+
|------|-------------|
14
+
|`valid/deployment/full-deployment-event.json`| A `dash0.deployment` event with all supported resource and event attributes populated. |
15
+
|`valid/deployment/minimal-deployment-event.json`| A `dash0.deployment` event with only the required resource attribute (`service.name`). All optional attributes are omitted to test the baseline case. |
16
+
17
+
### Invalid
18
+
19
+
| File | Description |
20
+
|------|-------------|
21
+
|`invalid/deployment/wrong-type-service-name.json`| A `dash0.deployment` event where `service.name` has the wrong type (`int` instead of `string`). Verifies that type mismatches are rejected. |
0 commit comments