JOC - JobScheduler Operations Center
  1. JOC - JobScheduler Operations Center
  2. JOC-512

Advanced Search in Audit Log view should ignore the profile parameter "Max. number of Audit Log entries"

    Details

      Description

      Current Situation

      • In the Audit Log view, when a user uses the "Advanced Search" function, then the profile parameter Max. number of Audit Log entries has no effect, but when using the normal search functions it does.

      Desired Behavior

      • The profile parameter Max. number of Audit Log entries should not be used to limit the results in the Audit Log view independently from the current filter or "Advanced Search" operation.

      Maintainer Notes
      The profile parameter is applied to all sub-views that offer an Audit Log, e.g. with the Job Chains, Orders and Jobs views. Sub-views do not include a search function but display Audit Log entries related to the current object, e.g. the job chain.

      1. JOC-512-Profile.png
        119 kB
      2. JOC-512-RESULTS.png
        178 kB

        Issue Links

          Activity

          Hide
          XEOPS Datenbank Admin added a comment -

          This sentence is incomplete: "The profile parameter Max. number of Audit Log entries should have the similar effect as when the user uses"

          Please note: We do NOT want the profile parameter Max. number of Audit Log entries to be applied when the user uses the Advanced Search. Currently, this is the only method we have to search the entire audit log because the profile parameter Max. number of Audit Log entries is hindering us from using the regular search.

          It seems that this profile parameter Max. number of Audit Log entries has only one benefit: to make the search faster by limiting the number of records it searches through. It would be better if the performance were just good enough to not even need such a parameter. Using the Advanced Search isn't slow and it searches through the entire audit log history, so I don't understand why using the normal search is slow when I increase the profile parameter Max. number of Audit Log entries. Maybe there is a bug somewhere?

          Show
          XEOPS Datenbank Admin added a comment - This sentence is incomplete: "The profile parameter Max. number of Audit Log entries should have the similar effect as when the user uses" Please note: We do NOT want the profile parameter Max. number of Audit Log entries to be applied when the user uses the Advanced Search. Currently, this is the only method we have to search the entire audit log because the profile parameter Max. number of Audit Log entries is hindering us from using the regular search. It seems that this profile parameter Max. number of Audit Log entries has only one benefit: to make the search faster by limiting the number of records it searches through. It would be better if the performance were just good enough to not even need such a parameter. Using the Advanced Search isn't slow and it searches through the entire audit log history, so I don't understand why using the normal search is slow when I increase the profile parameter Max. number of Audit Log entries. Maybe there is a bug somewhere?
          Hide
          XEOPS Datenbank Admin added a comment -

          We agree with the updated description. Stand: 13.09.2018.

          Show
          XEOPS Datenbank Admin added a comment - We agree with the updated description. Stand: 13.09.2018.
          Hide
          Uwe Risse added a comment -

          "Currently, this is the only method we have to search the entire audit log because the profile parameter Max. number of Audit Log entries is hindering us from using the regular search."

          This maybe is a misunderstanding on your site. When you mean with "regular search" the search in resultset option then this search is not a database search. The database search in in Advanced Search is umlimitted. Only the resultset is limited. You can set the limit to a very high value in you profile. Then execute the Advanced Search will result with the (limited) list of entries. We think that lets say resulting 10.000.000 records makes no sense for a GUI like JOC Cockpit. But if you want, you can set this value in the profile.

          The initial result is already limited by the today filter. That means when you open the view, you only see records from today. This is usually much less than the given limit in the profile.

          I see only one use case that might not be covered with the actual options. This is when you have a high number of audit log entries each day. Then the "very high" limit + the todays filter in the initial view might return to many entries. For this use case the solution is to introduce a new profile setting especially for the initial view.

          You also commented

          "It seems that this profile parameter Max. number of Audit Log entries has only one benefit: to make the search faster by limiting the number of records it searches through."

          Please note that not the number of records it searches through is limited. Always the whole database with all records is search without limits. Only the resultset is limited.

          You also commented

          so I don't understand why using the normal search is slow when I increase the profile parameter Max. number of Audit Log entries. Maybe there is a bug somewhere?
          When you mean with "normal search" the "search in resultset option" then let me explain that this option takes a given resultset and then filter this by the given value. This is not a database search. It is performed in the browser. Therefor it may be slower with a huge number of records in the resultset that must be filtered. There is no bug in the "search in resultset" option

          One more point is the "Maintainer Note" in JITL-512

          "The profile parameter is applied to all sub-views that offer an Audit Log, e.g. with the Job Chains, Orders and Jobs views. Sub-views do not include a search function but display Audit Log entries related to the current object, e.g. the job chain."

          This is wrong. The profile setting Max. number of Audit Log entries has no effect in the sub-views. Therefore I added the desired behavior that in the case that "Max. number of Audit Log entries" is smaller than "Max. number of Audit Log entries per object" then the value for Max. number of Audit Log entries should be used in the sub-Views. But this is a senseless use case and this aspect is not very important.

          Show
          Uwe Risse added a comment - "Currently, this is the only method we have to search the entire audit log because the profile parameter Max. number of Audit Log entries is hindering us from using the regular search." This maybe is a misunderstanding on your site. When you mean with "regular search" the search in resultset option then this search is not a database search. The database search in in Advanced Search is umlimitted. Only the resultset is limited. You can set the limit to a very high value in you profile. Then execute the Advanced Search will result with the (limited) list of entries. We think that lets say resulting 10.000.000 records makes no sense for a GUI like JOC Cockpit. But if you want, you can set this value in the profile. The initial result is already limited by the today filter. That means when you open the view, you only see records from today. This is usually much less than the given limit in the profile. I see only one use case that might not be covered with the actual options. This is when you have a high number of audit log entries each day. Then the "very high" limit + the todays filter in the initial view might return to many entries. For this use case the solution is to introduce a new profile setting especially for the initial view. You also commented "It seems that this profile parameter Max. number of Audit Log entries has only one benefit: to make the search faster by limiting the number of records it searches through." Please note that not the number of records it searches through is limited. Always the whole database with all records is search without limits. Only the resultset is limited. You also commented so I don't understand why using the normal search is slow when I increase the profile parameter Max. number of Audit Log entries. Maybe there is a bug somewhere? When you mean with "normal search" the "search in resultset option" then let me explain that this option takes a given resultset and then filter this by the given value. This is not a database search. It is performed in the browser. Therefor it may be slower with a huge number of records in the resultset that must be filtered. There is no bug in the "search in resultset" option One more point is the "Maintainer Note" in JITL-512 "The profile parameter is applied to all sub-views that offer an Audit Log, e.g. with the Job Chains, Orders and Jobs views. Sub-views do not include a search function but display Audit Log entries related to the current object, e.g. the job chain." This is wrong. The profile setting Max. number of Audit Log entries has no effect in the sub-views. Therefore I added the desired behavior that in the case that "Max. number of Audit Log entries" is smaller than "Max. number of Audit Log entries per object" then the value for Max. number of Audit Log entries should be used in the sub-Views. But this is a senseless use case and this aspect is not very important.

            People

            • Assignee:
              Sourabh Agrawal
              Reporter:
              Mahendra Patidar
              Approver:
              Mahendra Patidar
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: