Skip to content

[RFE] include xml stats in extraction #15

@DumpySquare

Description

@DumpySquare

We have been talking for some time about including stats in the extraction process. These stats, like iHealth, could give valuable insight to the system and applications being parsed.

This information could be used for migrations, upgrades and troubleshooting

qkview file locations to look at including and parsing

  • /stat_module.xml
  • /afm_module.xml
  • /apm_module.xml
  • /asm_module.xml
  • /ilx_module.xml
  • /mcp_module.xml
  • /mcp_module.xml
  • /gtm_module.xml
  • /arv_module.xml

** actually, we should probably just parse every .xml file in the base directory and see what we can get from there **

{
  qkModule: {
    index: {},
    afm: {},
    apm: {},
    asm: {},
    avr: {},
    gtm: {},
    ilx: {},
    ...,
  }
}

parsing xml to json

https://stackoverflow.com/questions/52281389/convert-xml-to-json-with-nodejs/57724779

Command to search qkview files

tar xaf some_viprion.qkview --to-command 'egrep -Hn --label="$TAR_FILENAME" "Ltm::Virtual Server:" || true'

tar xaf coreltm01_2.20.2021.qkview --to-command 'egrep -Hn --label="$TAR_FILENAME" "bigiq.benlab.io_t443_vs" || true' >> bigiqVsSearch.txt

@sergitopereira, I know you have already started some of this, but wanted to get it documented so we can track the details together. Do you have any input on where you were getting some of these details from qkviews? I've reworked the unPacker function to extract more config files like certs/keys/gtm/defaults. This is probably a good opportunity to start extracting the necessary files for stats.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions