Add automatic @timestamp field generation for Elasticsearch documents #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documents sent from Kafka to Elasticsearch lack timestamp fields, preventing time-based queries and visualizations.
Changes
TimestampFilter: Adds@timestampfield (ISO 8601 format) to documents lacking oneAddTimestampboolean inElasticSearchConf(defaults totrue)@timestampfields are left untouchedUsage
Documents without
@timestampwill now receive2006-01-02T15:04:05.000Zformatted timestamps in UTC.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.