.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, Intel Corporation and others.
+collectd plugins description
+============================
+The SFQM collectd plugins enable the ability to monitor DPDK interfaces by
+exposing stats and the relevant events to higher level telemetry and fault
+management applications. The following sections will discuss the SFQM features
+in detail.
+
Measuring Telco Traffic and Performance KPIs
-============================================
+--------------------------------------------
This section will discuss the SFQM features that enable Measuring Telco Traffic
and Performance KPIs.
value pairs, improving the overall performance of the API.
Monitoring DPDK interfaces
-===========================
+--------------------------
With the features SFQM enabled in DPDK to enable measuring Telco traffic and
performance KPIs, we can now retrieve NIC statistics including error stats and
relay them to a DPDK user. The next step is to enable monitoring of the DPDK
has been enabling a number of plugins for collectd.
collectd
----------
+~~~~~~~~
collectd is a daemon which collects system performance statistics periodically
and provides a variety of mechanisms to publish the collected metrics. It
supports more than 90 different input and output plugins. Input plugins retrieve
the data they receive to an end point. collectd also has infrastructure to
support thresholding and notification.
-Statistics and Notifications
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+collectd statistics and Notifications
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Within collectd notifications and performance data are dispatched in the same
way. There are producer plugins (plugins that create notifications/metrics),
and consumer plugins (plugins that receive notifications/metrics and do
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+ .. http://creativecommons.org/licenses/by/4.0
+ .. (c) <optionally add copywriters name>
+
+====================
+SFQM user guide
+====================
+
+.. The feature user guide should provide an OPNFV user with enough information to
+ .. use the features provided by the feature project in the supported scenarios.
+ .. This guide should walk a user through the usage of the features once a scenario
+ .. has been deployed and is active according to the installation guide provided
+ .. by the installer project.
+
+.. toctree::
+ :maxdepth: 3
+
+ collectd.userguide.rst
+ keepalive.userguide.rst
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, Intel Corporation and others.
-DPDK Keep Alive Overview
-=========================
+DPDK Keep Alive description
+===========================
SFQM aims to enable fault detection within DPDK, the very first feature to
meet this goal is the DPDK Keep Alive Sample app that is part of DPDK 2.2.
heartbeat mechanism.
DPDK Keep Alive Sample App Internals
-====================================
+------------------------------------
This section provides some explanation of the The Keep-Alive/'Liveliness'
conceptual scheme as well as the DPDK Keep Alive App. The initialization and
run-time paths are very similar to those of the L2 forwarding application (see
to monitor the Keep Alive Monitor Agent Core.
DPDK Keep Alive Sample App Code Internals
-=========================================
+-----------------------------------------
The following section provides some explanation of the code aspects that are
specific to the Keep Alive sample application.