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

chore: Merge next-patch into next-minor #1277

Merged
merged 3 commits into from
Nov 16, 2024
Merged

chore: Merge next-patch into next-minor #1277

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
93cfa33
fixing timestamp examples
kris-watts-gravwell Nov 16, 2024
2bfdff1
Merge pull request #1276 from kris-watts-gravwell/next-patch
david-fritz-gravwell Nov 16, 2024
26a2c5c
Merge next-minor into merge/next-patch_to_next-minor
github-actions[bot] Nov 16, 2024
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 search/search.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -262,7 +262,7 @@ It is also possible to use concrete timestamps. Any timestamp supported by [time
For example:

```gravwell
start="2006-01-02T15:04:05Z07:00" end="2006-01-02T23:04:05Z07:00" tag=default json foo table
start="2006-01-02T15:04:05Z" end="2006-01-02T23:04:05Z" tag=default json foo table
```

The example above uses RFC3339 timestamps to specify a concrete time range.
Expand All @@ -278,7 +278,7 @@ In the example above, the `end=` constraint is omitted, which sets the end of th
Additionally, relative and concrete timestamps can be combined. For example, to search from January 2nd, 2006, up to an hour ago:

```gravwell
start="2006-01-02T15:04:05Z07:00" end=-1h tag=default json foo table
start="2006-01-02T15:04:05Z" end=-1h tag=default json foo table
```

```{note}
Expand Down