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

Graph Timestamp does not match PCAP Timestamp #1507

Closed
jsthomason opened this issue Mar 16, 2021 · 2 comments
Closed

Graph Timestamp does not match PCAP Timestamp #1507

jsthomason opened this issue Mar 16, 2021 · 2 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@jsthomason
Copy link

Before opening a new issue, please make sure you've reviewed the troubleshooting guide:
https://github.com/brimsec/brim/wiki/Troubleshooting

Describe the bug
Graph Timestamp does not match PCAP timestamps nor System TZ

To Reproduce
My system time is US/Pacific, while the .pcap is US/Eastern; PCAP time is correct; Range selector is correct; Graph time appears to stay at UTC.

Expected behavior
Graph timestamps should match PCAP timestamps.

Screenshots

Desktop Info
[Please complete the following information]

  • OS: Ubuntu 18.04
  • Brim Version 0.24.0
@jsthomason jsthomason added the bug Something isn't working label Mar 16, 2021
@philrz
Copy link
Contributor

philrz commented Mar 16, 2021

@jsthomason: Thanks for reporting this. The app doesn't currently try to make any automatic adjustments based on the system time, since we know some users like to do everything in UTC, which is how it behaves by default. I'm not sure if you spotted it, but there is an option in the Preferences menu to set the timezone. This will adjust the times shown for the displayed events and when you hover your mouse over the graph. Unfortunately the values on the X axis itself are not adjusted, and we have an open issue #1057 tracking that. Since that sounds like it may be the nugget of what you experienced, my recommendation would be to keep an eye on that issue. I'll add comments there about your bumping into this and mention it to the team to help boost the priority. I'll wait to hear from you before closing this one.

@philrz
Copy link
Contributor

philrz commented Apr 2, 2021

Hello again @jsthomason. Since I've not seen another update from you in a couple weeks, I'm going to go ahead and close this one as a duplicate of #1057. Please do keep an eye on that one and feel free to comment more over there if you'd like. Thanks for your help improving Brim!

@philrz philrz closed this as completed Apr 2, 2021
@philrz philrz added the duplicate This issue or pull request already exists label Apr 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants