Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[release-v2.2] Docs: Fix invalid query #2861

Merged
merged 1 commit into from
Aug 29, 2023
Merged

[release-v2.2] Docs: Fix invalid query #2861

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/sources/tempo/traceql/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ For example, to find all traces where an `http.status_code` attribute in a span
This works for `http.status_code` values that are strings as well using lexographic ordering:

```
{ span.http.status_code >= "400"}
{ span.http.status_code >= "400" }
```

Find all traces where the `http.method` attribute is either `GET` or `DELETE`:
Expand Down Expand Up @@ -250,7 +250,7 @@ TraceQL supports a grouping pipeline operator that can be used to group by arbit
find someting like a single service with more than 1 error:

```
{ error = true } | by(resource.service.name) | count() > 1
{ status = error } | by(resource.service.name) | count() > 1
```

## Arithmetic
Expand Down