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.

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

Fix a typo in custom time spec doc #1172

Merged
Merged
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion ingesters/customtime/customtime.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ Exactly one named capture group in the Extraction-Regex must be defined. If no

#### Pre-extractions With Named Time Formats

Incoming data may also contain timestamps in formats that have already been defined in [timegrinder](https://pkg.go.dev/github.com/gravwell/gravwell/v3/timegrinder#Format but that cannot be reliably extracted without first performing a pre-extraction. This is often the case with embedded `unix`, `unixmilli`, and `unixnano` timestamps. The Pre-extraction `Extraction-Regex` can be combined with a named format so that timestamp formats that are already defined in [Timegrinder](https://pkg.go.dev/github.com/gravwell/gravwell/v3/timegrinder#Format). For example, consider the following entry:
Incoming data may also contain timestamps in formats that have already been defined in [timegrinder](https://pkg.go.dev/github.com/gravwell/gravwell/v3/timegrinder#Format) but that cannot be reliably extracted without first performing a pre-extraction. This is often the case with embedded `unix`, `unixmilli`, and `unixnano` timestamps. The Pre-extraction `Extraction-Regex` can be combined with a named format so that timestamp formats that are already defined in [Timegrinder](https://pkg.go.dev/github.com/gravwell/gravwell/v3/timegrinder#Format). For example, consider the following entry:

```
[task completed] tss:1701200161 tse:1701200161.1234 value:1700000000
Expand Down