MSSQL-Datacollector-Sheet
- Introduction
- Compatibility
- Requirements in the CIO Cockpit
- Configuration notes for the data collection management
- System access
- KPI scope of the data collection
Introduction
The integration of hardware/software - hereinafter referred to as "system" - into the CIO Cockpit not only requires the registration of the systems themselves but also the configuration of the data collection. Data collection is set up centrally via the Data Collection Management (DCM).
Compatibility
Supported system versions
MSSQL is supported on Microsoft SQL Server 2012 onwards on host operating systems Windows Server 2012 onwards.
Requirements in the CIO Cockpit
To set up the data collection, you must first create the system administration area for software in the CIO Cockpit web frontend (Configuration -> Databases) (see FAQs).
Then, the system can be selected in the DCM (Data Collectors & Assets -> Add Data Collector System -> Use existing element) when setting up the data collection.
Configuration notes for the data collection management
Field name | Required content |
---|---|
Hostname | FQDN of the host where the MSSQL instance is running (e.g. veeam42.company.local) |
Username | Username and domain for the login (e.g. mydomain\svc-cockpit) |
Password | Password for the login |
Mssql Instance Name | Name of the Veeam database instance |
Cockpit Reference | The entry for the system in the CIO Cockpit (is set automatically) |
Description | A short description of the created asset (free text field) |
System access
Users and authorizations
- To access the MSSQL instance via powershell, the host must be configured as described in Configuration of Windows hHosts via Domain controller
- Then the MSSQL instance itself must be configured, see Configuration of MSSQL based Assets.
- To include storage data, the
Windows host datacollector must also be configured for the host (both VM and physical server) running the MSSQL instance. - If the operating system is running on a virtual machine managed by a VCenter,
the parameter "disk.EnableUUID" has to be set to "true". Guidance:
- Shut down virtual machine
- Edit settings
- VM options
- Advanced: Edit configuration
- If the entry "disk.EnableUUID" exists, it must be set to "true". If it does not exist, it must be generated with the value "true".
- Save
- Boot VM
Network and firewall
The system is accessed via Powershell. The following settings are required for the Data Collector to communicate with the system:
Source | Destination | Port(default) | Protocol | Direction |
---|---|---|---|---|
datacollector-vm | Host-Betriebssystem der MSSQL-Instanz | 5985 (HTTP) / 5986 (HTTPS) | TCP | Outbound |
KPI scope of the data collection
KPI | Details |
---|---|
ramAllocation | The amount of RAM allocated to the MSSQL instance on the host (VM or hardware) |
cpuAllocation | The number of CPUs assigned to the instance on the host (VM or hardware) |
software InstanceID | The CIO Cockpit ID of the software instance (currently not visible in the frontend) |
List of components | List of databases (see below) |
timestamp | Time stamp with microsecond accuracy of the host OS on which the data collector is running (UTC) |
List of components
KPI | Details |
---|---|
name | Name of the database |
List of storage usages | Data for use of fixed storage by the database (see below) |
List of storage usages
KPI | Details |
---|---|
osPath | The complete path of the file |
sizeUsed | The storage space occupied by the file |