The KE config file can be found at etc/config.json
, it is what is used to generatr the gauges/alerts/ect dispalyed when the DD runs.
{
"views" : {
"0": {
"name":"single config",
"enabled" : 1,
"default" : 1,
"theme" : "Stock",
"background":"bg.jpg",
"pids": ["0x0C", "0x0F"],
"dynamic": {},
"alerts": [],
"gauges": [
{
"module": "Radial",
"path": "/Stock/",
"themeConfig": "120",
"pid": "0x0C"
}
]
}
}
}
In the example above we define a top level key views
. A view
is a collection of gauges and alerts. Views
can also have Dynamic
values.
In our example view
it can be seen that we have a simple id # as the first key, that is the id of the view
.
"name":"single config"
: This is the name of the view, this will be used later on when the web application is available to edit the views using a GUI.
"enabled" : 1
: Must be set to true if this view should be processed.
"default" : 1
: Signifies the view that should be shown by default ( Before dynamic checks )
"theme" : "Stock"
: The DD GUI code does not limit the guages displayed to one theme, but it has been decided that the initial version of the web application will have this limitation. That is why this key is present but it doesn't change how the code runs.
"background":"bg.jpg"
: The background image shown for the view.
"pids": ["0x0C", "0x0F"]
: All the PIDs that will be monitored by this view, remeber more PIDs = slower performance. These values should correlate with the constants entries.