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

Define an event.age field #700

Open
PhaedrusTheGreek opened this issue Dec 18, 2019 · 1 comment
Open

Define an event.age field #700

PhaedrusTheGreek opened this issue Dec 18, 2019 · 1 comment
Labels
discuss enhancement New feature or request

Comments

@PhaedrusTheGreek
Copy link

It's often necessary to track the lag/delay between @timestamp and event.ingested. When this is done , it's stored in milliseconds . I have been using the event.age field as it seems appropriate, and it could be defined as : "Difference in seconds between ingested time and source event time" : float

This value is often calculated using the Logstash age filter or simply Time.now.to_f - event.timestamp.to_f

@rsk0
Copy link

rsk0 commented Aug 20, 2023

Having a field for how long a log record takes to travel through a logs pipeline would be valuable!

(It's something my team's implemented, but not well.)

A few more ways to phrase this concept in case it helps: {delivery,transit} x {speed,time,duration}. Explicated for your convenient review:

  • delivery speed
  • delivery time
  • delivery duration
  • transit speed
  • transit time
  • transit duration

I think the terms 'delivery' and 'duration' do the best jobs of conveying the concepts at hand.

I've been at a bit of a loss for how to categorize this information. See this other issue, #2258, regarding organization possibilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants