Flow of

Monitoring
Types of Data used for
Monitoring:

• tbXMS uses two types of data for

monitoring:

• Performance data
• Service Availability data
 tbXMS support
three SNMP
versions:
SNMP version • SNMP v1 ( no security
between end device )
support • SNMP v2c( secured via
community name )
• SNMP v3( secured with
encryption)
 SNMP relies on a client-server application model
SNMP(Simpl
e Network
Management SNMP is not normally enabled by default on
devices
Protocol) :
SNMP works by sending messages, called
protocol data units (PDUs), to devices within
your network that “speak” SNMP. These
messages are called SNMP Get-Requests.
 SNMP Manager

SNMP Agent
Components
of SNMP Managed Device
Monitoring
Management Information Base (MIB)

Object Identifier (OID)

 tbXMS uses port-based
monitoring to monitor services.
Service
Availability tbXMS by default provide the
data: support of services

Custom service can also be

defined as per requirement
 Monitor:

Collectively
which collects
data from • It has three main sub-
network devices components:
1. Poller
2. Collector
3. Threshold
Poller
• A Poller is a piece of software that sends
a periodic request to an agent for
management data.
• The Poller works by using SNMP to query
MIBS and uses standard OIDs to collect
service performance test information
includes all types of data
• By default, following are the polling
interval in tbXMS:
• Service Availability Poller: 5
minutes
• Performance Poller : 15 minutes
• Poller interval values can be changeable
as per requirement
 • It is a component used to obtain data from a device and monitor a
device.

• tbXMS supports various types of collectors:

• SNMP collector: Collects performance metrics through SNMP

Collector protocol. It calculate metric values for the data that is collected
by SNMP collector. SNMP metric data such as response times,
latency, jitter, packet loss, and device health metrics. The SNMP
Collector generates poll requests on all discovered SNMP
devices.
• JMX collector: Collects performance data via Java Management
Extensions
• HTTP collector: Collects performance data via HTTP and HTTPS
 • Certain limits are defined for various metrics of data which
are being compared with all the data collected and send to
Threshold: Event and Alarm threshold
Alarm and Event
Translator:
• Alarm Translator: It is a component in tbXMS
system which process and manages alarms

• Event Translator : It is a component in tbXMS

helps to process events generated by
monitoring system
• events are simply ‘raw data’ independent of the
context of that data being good or bad.

This will further send data to Postgresql

database
 Data Storage:

• There are three types of databases

used to store the data taken from
monitoring system

• RRD Database
• Postgresql Database
• File Based Database
 • It is a circular database that

RRD
stores time series data.
• It aims to handle time series data
such as network-bandwidth,
temperature, CPU Load etc.

Database: • The database collects data for a

fixed period of time, and
information that is older than
the threshold gets removed
 • PostgreSQL is a powerful, open source object-
Postgresql relational database system that uses and
extends the SQL language combined with
Database: many features that safely store and scale the
most complicated data workloads.

• Postgres stores data in files in its data

directory

• It stores events and node information

receives from event and alarm translator
File Based
Storage:
• A database is stored as a file or a set
of files

• It is used to organize and maintain

data files

• It stores user data and user

preferences along with reports and
stores log, binaries and libraries, web
application data in the form of XML in
configuration files
API(Application Program Interface)
API is defined as a software code that helps two different software’s to
communicate and exchange data with each other
• There are four API used in tbXMS:
• RRD API: It addresses performance related data
• Karaf SSH API: It shares the availability of node in real time
• Log4j API: Log4j is a fast, reliable and flexible logging framework
which is written in java. It is an open-source logging API for java.
Logging means way to indicate the state of the system at runtime.
• XML API: Configuration features such as adding a node, discovery
adding a service etc.
 • MongoDB: Local Database to store
the response fetch from RRD API,
tbDashboard: Karaf SSH API and Log4j API.
• Node.js: backend process (script)

tbXMS user • CLI based

• GUI based
interface: