Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-2690

Improve the command usage of audit parser tool

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 0.4.0
    • 0.5.0
    • Tools

    Description

      I did the test for ozone-0.4, but found audit parser tool is not so friendly to use for user. I input -h option to get help usage, then only this few messages:

      Usage: ozone auditparser [-hV] [--verbose] [-D=<String=String>]... <database>
                               [COMMAND]
      Shell parser for Ozone Audit Logs
            <database>   Existing or new .db file
            --verbose    More verbose output. Show the stack trace of the errors.
        -D, --set=<String=String>
      
        -h, --help       Show this help message and exit.
        -V, --version    Print version information and exit.
      Commands:
        load, l      Load ozone audit log files
        template, t  Execute template query
        query, q     Execute custom query
      

      Although it shows me 3 options we can use, but I still not know the complete command to execute, like how to load audit to db, which available template I can use?

      Then I have to get detailed usage from tool doc then come back to execute command, it's not effective to use. It will be better to add some necessary usage (table structure, available templates, ...)info in command usage.

      Attachments

        1. ozone_auditparser.png
          163 kB
          Yi-Sheng Lien
        2. audiparserLoad.png
          48 kB
          Yi-Sheng Lien
        3. auditparserQuery.png
          51 kB
          Yi-Sheng Lien
        4. auditparserTemplate.png
          70 kB
          Yi-Sheng Lien

        Issue Links

          Activity

            People

              cxorm Yi-Sheng Lien
              linyiqun Yiqun Lin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m