Ericsson KGET Parser
Paste a KGET configuration dump and explore the managed-object tree, filter attributes, and export to JSON — all in your browser.
KGET (Configuration Get) is Ericsson's plain-text snapshot of a node's entire Managed Object (MO) tree. Every RAN engineer who works with Ericsson ENM, OSS-RC, or AMOS has stared at a KGET dump trying to find one attribute in 50 MB of indented text. This free online KGET parser turns that dump into an interactive, searchable tree: expand a ManagedElement down to each NRCellDU, SectorCarrier, or EUtranCellFDD, filter attributes by name, and export any subtree as JSON. Everything runs in your browser — your config never leaves the page, so it's safe to use with production data. Typical users are Ericsson RAN engineers, integration engineers, network auditors, and anyone debugging a gNodeB MO inconsistency who'd rather click through a tree than grep a file.
KGET Input
Paste the full output of an Ericsson KGET / AMOS 'get .' command. Parsing happens entirely in your browser.
Frequently Asked Questions
What is an Ericsson KGET dump?
KGET is the Ericsson configuration export format produced by AMOS, ENM CLI, or OSS-RC commands like "get ." It is a plain-text representation of every Managed Object (MO) on a node — eNodeB, gNodeB, RBS, or BSC — including all attributes and their current values.
Is the parsed data ever uploaded to a server?
No. Parsing runs entirely in JavaScript inside your browser. Your configuration text is never sent over the network, never logged, and never stored — you can verify this in your browser devtools network tab.
How large a KGET can I paste?
Modern browsers handle multi-megabyte strings comfortably. The parser streams lines and builds a tree in one pass, so 10–50 MB KGETs work on a typical laptop. Very large dumps may take a second or two to render.
Can I export the tree?
Yes. Click "Export JSON" to download the parsed tree as structured JSON that you can feed into Python, Node, or jq for further automation.
How It Works
The parser treats KGET output as an indentation-based hierarchy. Each non-indented line that matches the Name=Instance pattern is a managed object; lines indented below it are the object's attributes. Nested objects are detected by a deeper indent level.
- Attributes are parsed as
name type valuetriples. - Reference, Struct, and Sequence attributes keep their raw text value.
- Use the filter box to show only MOs whose class or attributes match a substring.
- Export JSON to feed the parsed tree into your own scripts.
Master this in our 5G/6G Academy courses
Go beyond the calculator — learn the 3GPP specs, real-world planning trade-offs, and hands-on labs from TELCOMA Global engineers.
Calculator gave you the answer? Learn the theory in 7 days, free.
$19.99/mo (global) · ₹999/mo (India). Full Pro access — 150+ hands-on exercises, 20+ troubleshooting Scenarios, 17 certifications, TelcoMentor AI coach. No credit card.
- No credit card
- Cancel anytime
- Full Pro access
- TELCOMA since 2009