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

Feature Request: Searching on the Transaction Log #987

Closed
daemonsy opened this Issue Feb 13, 2014 · 8 comments

Comments

Projects
None yet
4 participants
@daemonsy

daemonsy commented Feb 13, 2014

Hi guys,

The Logs page is a very useful resource for information, e.g. finding the IP / User-agent of the requester.

But it's currently not searchable. We had a problem when wanted to debug a duplicate payment and had to click the "Load More" at least 50 - 80 times before reaching that transaction (all filters to narrow things down applied).

(After so many clicks, I was glad that the saved offline HTML preserves these links. )

@jkwade

This comment has been minimized.

Show comment
Hide comment
@jkwade

jkwade Feb 13, 2014

+1000

In addition, there are at least three other things we can do to make the searching and discoverability of errors/logs better:
0. Add search to the Logs view

  1. Include a list of Log activity to the bottom of each resource view (most importantly Debits)
  2. Add resource state filtering to the Activity page (i.e. succeeded vs failed)
  3. Add date/time filtering to the Logs page (same as what's available on the Activity page)

/cc @dmdj03 @kyungmin

jkwade commented Feb 13, 2014

+1000

In addition, there are at least three other things we can do to make the searching and discoverability of errors/logs better:
0. Add search to the Logs view

  1. Include a list of Log activity to the bottom of each resource view (most importantly Debits)
  2. Add resource state filtering to the Activity page (i.e. succeeded vs failed)
  3. Add date/time filtering to the Logs page (same as what's available on the Activity page)

/cc @dmdj03 @kyungmin

@dmdj03

This comment has been minimized.

Show comment
Hide comment
@dmdj03

dmdj03 Feb 24, 2014

@daemonsy you can actually search by OHM# in the search box. What pieces of information do you have when trying to locate a specific log? We constrain the list by endpoint and request status currently. Will adding a date filter solve your problem? How granular does it need to be to meet your needs? By day? By hour?

dmdj03 commented Feb 24, 2014

@daemonsy you can actually search by OHM# in the search box. What pieces of information do you have when trying to locate a specific log? We constrain the list by endpoint and request status currently. Will adding a date filter solve your problem? How granular does it need to be to meet your needs? By day? By hour?

@daemonsy

This comment has been minimized.

Show comment
Hide comment
@daemonsy

daemonsy Feb 25, 2014

Hey @dmdj03, when you say search by OHM#, how do you retrieve the OHM#?

The example of what happened to us:

We wanted to see transactions that happened between X datetime to Y datetime, based on the timestamps on our own backend. We wanted to get the user agent that created the transaction and it that could only be accessed from the log. Hence we needed to find the corresponding request in the log. Adding a date filter would solve the problem we faced indirectly. Might be a great thing if there's links in each transaction pointing to requests related to them.

daemonsy commented Feb 25, 2014

Hey @dmdj03, when you say search by OHM#, how do you retrieve the OHM#?

The example of what happened to us:

We wanted to see transactions that happened between X datetime to Y datetime, based on the timestamps on our own backend. We wanted to get the user agent that created the transaction and it that could only be accessed from the log. Hence we needed to find the corresponding request in the log. Adding a date filter would solve the problem we faced indirectly. Might be a great thing if there's links in each transaction pointing to requests related to them.

@mjallday

This comment has been minimized.

Show comment
Hide comment
@mjallday

mjallday Feb 25, 2014

Contributor

Might be a great thing if there's links in each transaction pointing to requests related to them.

Yes! This is the correct way to solve this.

Contributor

mjallday commented Feb 25, 2014

Might be a great thing if there's links in each transaction pointing to requests related to them.

Yes! This is the correct way to solve this.

@dmdj03

This comment has been minimized.

Show comment
Hide comment
@dmdj03

dmdj03 Feb 26, 2014

@daemonsy definitely agree that we should add related logs to the transactions.
screen shot 2014-02-26 at 2 05 19 pm

We can also beef up the date filter on the logs page by adding a time of day filtering component. What do you think?

screen shot 2014-02-26 at 2 03 19 pm
screen shot 2014-02-26 at 2 03 33 pm
screen shot 2014-02-26 at 2 03 50 pm
screen shot 2014-02-26 at 2 04 01 pm
screen shot 2014-02-26 at 2 04 14 pm

dmdj03 commented Feb 26, 2014

@daemonsy definitely agree that we should add related logs to the transactions.
screen shot 2014-02-26 at 2 05 19 pm

We can also beef up the date filter on the logs page by adding a time of day filtering component. What do you think?

screen shot 2014-02-26 at 2 03 19 pm
screen shot 2014-02-26 at 2 03 33 pm
screen shot 2014-02-26 at 2 03 50 pm
screen shot 2014-02-26 at 2 04 01 pm
screen shot 2014-02-26 at 2 04 14 pm

@daemonsy

This comment has been minimized.

Show comment
Hide comment
@daemonsy

daemonsy Feb 27, 2014

Wow this looks really nice. I think both of them are great additions! 😍

daemonsy commented Feb 27, 2014

Wow this looks really nice. I think both of them are great additions! 😍

@mjallday

This comment has been minimized.

Show comment
Hide comment
@mjallday

mjallday Feb 27, 2014

Contributor

@dmdj03 can you create a separate issue for the txn filtering? I believe it will get built before the log stuff since it's not blocked by backend changes.

Contributor

mjallday commented Feb 27, 2014

@dmdj03 can you create a separate issue for the txn filtering? I believe it will get built before the log stuff since it's not blocked by backend changes.

@dmdj03

This comment has been minimized.

Show comment
Hide comment

dmdj03 commented Feb 28, 2014

@mahmoudimus mahmoudimus referenced this issue Apr 9, 2014

Merged

Add date time picker in log index page #1130

2 of 2 tasks complete

@dmdj03 dmdj03 closed this May 5, 2014

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