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

The kubectl get events -w logs' first column should be LASTSEEN #27060

Closed
dkaplan-pivotal opened this issue Jun 8, 2016 · 2 comments
Closed

The kubectl get events -w logs' first column should be LASTSEEN #27060

dkaplan-pivotal opened this issue Jun 8, 2016 · 2 comments
Assignees
@therc

Comments

@dkaplan-pivotal
Copy link

Hello Kubernetes,

The order of the columns when you get events confused me. I was thinking,

In our Kubernetes environments, the event logs (ie: kubectl get events -w) aren't always ordered chronologically. For example, line 1 will be from 30 minutes ago, line 2 will be 5 seconds ago, line 3 will be 20 minutes ago then line 4 will be 1 second ago. I'm not sure if this is a problem with our Kubernetes install or Kubernetes itself.

Turns out it's just a visual problem where these events are sorted correctly (by LASTSEEN), but the first column is FIRSTSEEN. I think the first column should be LASTSEEN because that's the order the events are listed.
@justinsb
Copy link
Member

justinsb commented Jun 8, 2016

This also confused me when I first saw it - I think this ordering would be more intuitive and help users discover the aggregation feature logically, instead of first having to grapple with why events are "out of order"

@therc
Copy link
Member

therc commented Jun 13, 2016

Should the order be always LASTSEEN,FIRSTSEEN or just when using -w?
I have an ugly PR for the latter, but perhaps we should just go for the former.

@therc therc mentioned this issue Jun 16, 2016
Merged
therc pushed a commit to Clarifai/kubernetes that referenced this issue Jun 16, 2016
swap FIRSTSEEN/LASTSEEN columns in kubectl get event
bf873df 
Not having LASTSEEN as the first column can confuse users into thinking
that events are not delivered in order.

Fixes kubernetes#27060
k8s-github-robot pushed a commit that referenced this issue Jun 21, 2016
Merge pull request #27549 from Clarifai/eventorder
1fd4047 
Automatic merge from submit-queue

swap FIRSTSEEN/LASTSEEN columns in `kubectl get event -w`

```release-note
Show LASTSEEN, the sorting key, as the first column in `kubectl get event` output
```
Not having LASTSEEN as the first column can confuse users into thinking
that events are not delivered in order.

Fixes #27060
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@therc therc

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@justinsb @dkaplan-pivotal @therc