If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:KPI
| BoxMatrix >> Lexicon >> Computer-Terms >> KPI | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Computer | FRITZ | I18N | Telephony | Smarthome | Internet | Protocols | Multimedia | Formats | Hardware | Software | Research |
Term
| Term: | KPI | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Short for: | Key Performance Indicator | ||||||
| Location: | Lexicon >> Computer-Terms | ||||||
| Weblinks: | Wikipedia.int - Wikipedia.de | ||||||
| Description: | Performance monitoring in computer systems and networks | ||||||
Goto: FRITZ!OS - SMW-Browser
Details
KPI is a generic term, which is also used for performance metering and monitoring data in computer systems and networks.
The data is gathered by sensors, as it is done for Monitoring and forwarded to some data collection service.
From there it could be forwarded by some means to a centralized interpreting service for further analysis.
This all sounds similar to Monitoring using SNTP or UPnP / TR-064, yes it is, but the information gathered is more in depth.
KPI is not limited to Graphing samples of sensor values over time but can have arbitary data structure and complexity.
Of course subsets of KPI data could be used for Graphing.
FRITZ!OS
FRITZ!OS started to collect KPI data in fw 6.83. The data is sent from numerous sensors and collected by ctlmgr.
To trigger KPI submission ctlmgr fires the KPI_PRE_INFORM_NOTIFY event in the AVMIPC-Datastore. All sensor processes
are subscribed to this event and send their sensor data as JSON attachments to ctlmgr using the me_KPI.ctl endpoint.
Sensors which are subscribed to KPI_PRE_INFORM_NOTIFY:
- psetd using kpi using avmipc_send_kpi - fw 6.83+ - System sensors (mermory, uptime, etc)
- ctlmgr (directly) - fw 7.01+? - Arbitary FRITZ!OS sensors
- ctlmgr using libctlusb.so - fw 7.01+? - Partition monitoring (WebDAV, Internal-Storage)
- kpid using avm_kpi_test.ko - fw 7.08+ - Kernel sensors
- voipkpid using libvoipkpi.so - fw 7.08+ - VoIP quality
- aha (directly) - fw 7.12+? - Smarthome sensor data
- ctlmgr using libdect.so - fw 7.12+? - DECT quality
- ctlmgr using libdslremotemgmt.so - fw 7.12+? - DSL quality
- ctlmgr using libfiberremotemgmt.so - fw 7.29+? - Fiber quality
- mobiled (directly) - fw 7.39+? - Mobile quality
DOCSIS quality does not seem to use KPI, since it is monitored by SNMP.
Not subscribed, triggered by services:
- libwebkpi.so collecting from libwebkpiclient.so - fw 7.39+ - Performance of HTTP / HTTPS online services for ARGO
Not subscribed, trigger is subject to research:
- telefon using avmipc_send_kpi - Telephony quality
- meshd using libmeshd.so - Mesh capabilities
Firmware versions marked with a ? are the minimum findings in Supportdata-Probes, which are always incomplete.
There is no user interface to KPI, but some occurences in supportdata:
kpid -p # from supportdata.basis aicmd meshd kpi kpi show # from supportdata.meshd voipkpid -n 20 # from supportdata
Unused known commandline interfaces:
aha -c"kpi list all" # unused, does not work (any more?) aicmd meshd kpi kpi send # unused
To research:
