Navigation Menu

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

Log review interface. #479

Open
aethelwulffe opened this issue Mar 8, 2017 · 10 comments
Open

Log review interface. #479

aethelwulffe opened this issue Mar 8, 2017 · 10 comments

Comments

@aethelwulffe
Copy link
Contributor

The Administration->Logs feature, which lets you do searches in the logs by user etc... should not do anything except display the interface when you navigate to it. Currently, it executes queries, sometimes crashing marginal systems with a lot of data in the logs without the user ever having selected any search criteria. Often times, this is due simply to accidentally selecting the wrong item, getting logs and having to wait until the system starts responding again.

@navendu29
Copy link

Can I work on this Usability feature ?

@aethelwulffe
Copy link
Contributor Author

Yes you may, of course. To assign you, I will need to add you to the collaborator list.

@aethelwulffe
Copy link
Contributor Author

Are you a GSOC hopeful, or do you just want to be added to the standard team invitation?

@navendu29
Copy link

Yes, I intend to apply for GSOC .

@aethelwulffe
Copy link
Contributor Author

Then you may accept the invitation I sent you to that team, and welcome aboard!

@navendu29
Copy link

Thank you for the invitation.

@navendu29
Copy link

What type of interface do u want?
Should the interface only contain the log information from the log tabel ?

@aethelwulffe
Copy link
Contributor Author

Ha! I don't want an interface. The community does. That means you get to decide and design it, in light of it's common usage case....
So, what is this log table used for?

  • It is used to track activity by users, sort of a "blame" track that can be used to identify a series of events.
  • A source for extracting every query that has been made and use that do things like recreate the data after someone has deleted it. On this piece, it would be nice if the log.comment section kept the queries clean and accessible instead of prepending them with other strings.
  • It can be used to find where some types of upgrade or imports have happened for troubleshooting purposes.
    Now, in regard to the above, and the fact that at the moment the log interface has a very small footprint, it would be nice if it got improved without turning it into a huge project unto itself, with a whole bunch of assets that only it uses. While the criteria selection and display are a bit clunky, the main issue is about the fact that the page takes forever to load because it tries to do things right when you click on the menu item...sometimes taking up massive resources and freezing the server...which is the main objective of the issue.

@navendu29
Copy link

I am getting a trouble in implementing this feature. I think i need to study more regarding this for which i would need some time so , if anyone else wants to work on this feature he/she may proceed .

@tmccormi
Copy link

A pull request is coming from @growlingflea that is the baseline. It's an Activity Log viewer we created for Dr Bob Hoyt. Uses DataTables.

Looks like this

  1. Default TODAY
    defaultactivitytoday

  2. Filtered Search
    filteredactivitylog

  3. Summary
    summaryactivitylog

  4. Details
    activitylog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants