Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-5977

Structure for cfstats output (JSON, YAML, or XML)

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 3.6
    • Legacy/Tools

    Description

      nodetool cfstats should take a --format arg that structures the output in JSON, YAML, or XML. This would be useful for piping into another script that can easily parse this and act on it. It would also help those of us who use things like MCollective gather aggregate stats across clusters/nodes.

      Thoughts? I can submit a patch.

      Attachments

        1. CASSANDRA-5977-trunk.patch
          40 kB
          Shogo Hoshii
        2. CASSANDRA-5977-trunk.patch
          32 kB
          Shogo Hoshii
        3. sample_result.zip
          12 kB
          Shogo Hoshii
        4. sample_result.zip
          13 kB
          Shogo Hoshii
        5. tablestats_sample_result.json
          43 kB
          Shogo Hoshii
        6. tablestats_sample_result.txt
          36 kB
          Shogo Hoshii
        7. tablestats_sample_result.yaml
          50 kB
          Shogo Hoshii
        8. trunk-tablestats.patch
          23 kB
          Shogo Hoshii
        9. trunk-tablestats.patch
          25 kB
          Shogo Hoshii

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            shoshii Shogo Hoshii Assign to me
            alyssa.c.kwan Alyssa Kwan
            Shogo Hoshii
            Yuki Morishita
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment