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
[chore] Update documentation in query_service.proto (#149)
## Which problem is this PR solving?
- Towards jaegertracing/jaeger#6629
## Description of the changes
- Cleans up `query_service.proto` to improve the documentation so that
it can be re-used for the remote storage API v2
## How was this change tested?
- CI
## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
- for `jaeger`: `make lint test`
- for `jaeger-ui`: `npm run lint` and `npm run test`
---------
Signed-off-by: Mahad Zaryab <[email protected]>
Copy file name to clipboardexpand all lines: swagger/api_v3/query_service.swagger.json
+20-16
Original file line number
Diff line number
Diff line change
@@ -85,57 +85,59 @@
85
85
"parameters": [
86
86
{
87
87
"name": "query.service_name",
88
+
"description": "service_name filters spans generated by a specific service.",
88
89
"in": "query",
89
90
"required": false,
90
91
"type": "string"
91
92
},
92
93
{
93
94
"name": "query.operation_name",
95
+
"description": "operation_name filters spans by a specific operation / span name.",
94
96
"in": "query",
95
97
"required": false,
96
98
"type": "string"
97
99
},
98
100
{
99
101
"name": "query.start_time_min",
100
-
"description": "Span min start time in. REST API uses RFC-3339ns format. Required.",
102
+
"description": "start_time_min is the start of the time interval (inclusive) for the query.\nOnly traces with spans that started on or after this time will be returned.\n\nThe HTTP API uses RFC-3339ns format.\n\nThis field is required.",
101
103
"in": "query",
102
104
"required": false,
103
105
"type": "string",
104
106
"format": "date-time"
105
107
},
106
108
{
107
109
"name": "query.start_time_max",
108
-
"description": "Span max start time. REST API uses RFC-3339ns format. Required.",
110
+
"description": "start_time_max is the end of the time interval (exclusive) for the query.\nOnly traces with spans that started before this time will be returned.\n\nThe HTTP API uses RFC-3339ns format.\n\nThis field is required.",
109
111
"in": "query",
110
112
"required": false,
111
113
"type": "string",
112
114
"format": "date-time"
113
115
},
114
116
{
115
117
"name": "query.duration_min",
116
-
"description": "Span min duration. REST API uses Golang's time format e.g.10s.",
118
+
"description": "duration_min is the minimum duration of a span in the trace.\nOnly traces with spans that lasted at least this long will be returned.\n\nThe HTTP API uses Golang's time format (e.g., \"10s\").",
117
119
"in": "query",
118
120
"required": false,
119
121
"type": "string"
120
122
},
121
123
{
122
124
"name": "query.duration_max",
123
-
"description": "Span max duration. REST API uses Golang's time format e.g.10s.",
125
+
"description": "duration_max is the maximum duration of a span in the trace.\nOnly traces with spans that lasted at most this long will be returned.\n\nThe HTTP API uses Golang's time format (e.g., \"10s\").",
124
126
"in": "query",
125
127
"required": false,
126
128
"type": "string"
127
129
},
128
130
{
129
131
"name": "query.search_depth",
130
-
"description": "Maximum depth of search. Depending on the backend storage\nimplementtaion this could be like a regular LIMIT clause in SQL,\nbut not all implementations support such accuracy and for those\nthe larger depth value simply means more traces returned.",
132
+
"description": "search_depth defines the maximum search depth. Depending on the backend storage implementation,\nthis may behave like an SQL `LIMIT` clause. However, some implementations might not support\nprecise limits, and a larger value generally results in more traces being returned.",
131
133
"in": "query",
132
134
"required": false,
133
135
"type": "integer",
134
136
"format": "int32"
135
137
},
136
138
{
137
139
"name": "query.raw_traces",
138
-
"description": "Optional. If set to true, the response will not include any\nenrichments to the trace, such as clock skew adjustment.\nInstead, the trace will be returned exactly as stored.",
140
+
"description": "If set to true, the response will exclude any enrichments to the trace, such as clock skew adjustments.\nThe trace will be returned exactly as stored.\n\nThis field is optional.",
139
141
"in": "query",
140
142
"required": false,
141
143
"type": "boolean"
@@ -334,47 +336,49 @@
334
336
"type": "object",
335
337
"properties": {
336
338
"service_name": {
337
-
"type": "string"
339
+
"type": "string",
340
+
"description": "service_name filters spans generated by a specific service."
338
341
},
339
342
"operation_name": {
340
-
"type": "string"
343
+
"type": "string",
344
+
"description": "operation_name filters spans by a specific operation / span name."
341
345
},
342
346
"attributes": {
343
347
"type": "object",
344
348
"additionalProperties": {
345
349
"type": "string"
346
350
},
347
-
"description": "Attributes are matched against Span and Resource attributes.\nAt least one span in a trace must match all specified attributes."
351
+
"description": "attributes contains key-value pairs where the key is the attribute name\nand the value is its string representation. Attributes are matched against\nspan and resource attributes. At least one span must match all specified attributes."
348
352
},
349
353
"start_time_min": {
350
354
"type": "string",
351
355
"format": "date-time",
352
-
"description": "Span min start time in. REST API uses RFC-3339ns format. Required."
356
+
"description": "start_time_min is the start of the time interval (inclusive) for the query.\nOnly traces with spans that started on or after this time will be returned.\n\nThe HTTP API uses RFC-3339ns format.\n\nThis field is required."
353
357
},
354
358
"start_time_max": {
355
359
"type": "string",
356
360
"format": "date-time",
357
-
"description": "Span max start time. REST API uses RFC-3339ns format. Required."
361
+
"description": "start_time_max is the end of the time interval (exclusive) for the query.\nOnly traces with spans that started before this time will be returned.\n\nThe HTTP API uses RFC-3339ns format.\n\nThis field is required."
358
362
},
359
363
"duration_min": {
360
364
"type": "string",
361
-
"description": "Span min duration. REST API uses Golang's time format e.g.10s."
365
+
"description": "duration_min is the minimum duration of a span in the trace.\nOnly traces with spans that lasted at least this long will be returned.\n\nThe HTTP API uses Golang's time format (e.g., \"10s\")."
362
366
},
363
367
"duration_max": {
364
368
"type": "string",
365
-
"description": "Span max duration. REST API uses Golang's time format e.g.10s."
369
+
"description": "duration_max is the maximum duration of a span in the trace.\nOnly traces with spans that lasted at most this long will be returned.\n\nThe HTTP API uses Golang's time format (e.g., \"10s\")."
366
370
},
367
371
"search_depth": {
368
372
"type": "integer",
369
373
"format": "int32",
370
-
"description": "Maximum depth of search. Depending on the backend storage\nimplementtaion this could be like a regular LIMIT clause in SQL,\nbut not all implementations support such accuracy and for those\nthe larger depth value simply means more traces returned."
374
+
"description": "search_depth defines the maximum search depth. Depending on the backend storage implementation,\nthis may behave like an SQL `LIMIT` clause. However, some implementations might not support\nprecise limits, and a larger value generally results in more traces being returned."
371
375
},
372
376
"raw_traces": {
373
377
"type": "boolean",
374
-
"description": "Optional. If set to true, the response will not include any\nenrichments to the trace, such as clock skew adjustment.\nInstead, the trace will be returned exactly as stored."
378
+
"description": "If set to true, the response will exclude any enrichments to the trace, such as clock skew adjustments.\nThe trace will be returned exactly as stored.\n\nThis field is optional."
375
379
}
376
380
},
377
-
"description": "Query parameters to find traces. Except for num_traces, all fields should be treated\nas forming a conjunction, e.g., \"service_name='X' AND operation_name='Y' AND ...\".\nAll fields are matched against individual spans, not at the trace level.\nThe returned results contain traces where at least one span matches the conditions.\nWhen num_traces results in fewer traces returned, there is no required ordering.\n\nNote: num_traces should restrict the number of traces returned, but not all backends\ninterpret it this way. For instance, in Cassandra this limits the number of _spans_\nthat match the conditions, and the resulting number of traces can be less.\n\nNote: some storage implementations do not guarantee the correct implementation of all parameters."
381
+
"description": "Query parameters to find traces.\n\nAll fields form a conjunction (e.g., \"service_name='X' AND operation_name='Y' AND ...\"),\nexcept for `search_depth` and `raw_traces`.\n\nFields are matched against individual spans, not the trace level. The results include\ntraces with at least one matching span.\n\nThe results have no guaranteed ordering."
0 commit comments