An open and scalable architecture
We have developed an open and scalable architecture, totally independent of software editors and manufacturers, allowing users to integrate any type of components (physical or virtual) or data in an industrialised collect workflow.
Our positioning consists in collecting the many available raw data in your technical platforms and repositories. We have developed generic collectors whose roles are to retrieve available data files on the LAN or to execute commands/scripts to remotely interrogate technical repositories where all such data are stored.
These collectors allow the entry of all types of data in the collect workflow, without having to deploy agents on all components included in the perimeter.
The generic collectors are provided with fully customisable graphical interfaces to adjust to any type of collect, which allows to configure new components without having to integrate command lines. Each parameter becomes a text field entry or a check box in the collect server interface.
The following example illustrated the execution if the command mibbrowser\snmpwalk -c public SANSW012 .22.214.171.124.4.1.1588 on a SAN switch.
The supported collect modes to interrogate repositories in standard are
- Execution of command lines via APIs or system (shell, powershell, wmi, snmp, smi-s)
- Execution of batchs or scripts (all system scripts are supported)
The collect modes supported to retrieve files are as a standard
- CIFS or NFS shares on the LAN
- ftp, ssh, sftp
Standard supported data sources are: text, csv, excel, xml, emails (with or without attachments) or other formats of structured text files.
The HMI data collect, is an interface installed on the data collect server which manages all of the operations:
- Configuration and collect planning
- Consolidation transfer of data
- Operations monitoring
- Stop/ relaunch of services
This interface relies on a « crontab » type scheduling engine, in charge of the planning of the jobs. Each planned operation can also be executed in command line mode; it can therefore be integrated in an external scheduler.
The sampling frequency directly depends on the type of collect and KPI to be produced. For capacity planning reports the frequency will either be weekly or monthly, for operational reports it will be on a daily basis.