Plugin for Dell Powerstore storage array

BertrandJO commented 3 years ago

Hi,

Last year, Dell launched a new storage array family, Powerstore and we have to monitor one of them (500T).

There is an embedded API Rest, documentation can be found here : https://downloads.dell.com/manuals/common/pwrstr-apirefg_en-us.pdf.

No snmp available, only trap sending.

Do you have customers who have the same monitoring need ?

Best Regards,

BJO

garnier-quentin commented 3 years ago

If it's a new product, i will come (if the product is working ;) If you provide curls example and results, we could do something.

BertrandJO commented 3 years ago

ok, I will try to send you such examples soon.

garnier-quentin commented 3 years ago

I need the login system. Otherwise:

alert (GET /alert)
appliance (GET /appliance)
cluster (GET /cluster)
filesystem (GET /file_system)
hardware (GET /hardware)
nas server (GET /nas_server)
physical_switch (GET /physical_switch)
volume (GET /volume)

BertrandJO commented 3 years ago

Hi Quentin,

Here is an example :

wget --no-check-certificate -qO- -X GET --header="Content-type: application/json" --header="Accept: application/json" --header="Authorization: Basic USER:PASS" https://X.X.X.X/api/rest/appliance [{"id":"A1"}]

wget --no-check-certificate -qO- -X GET --header="Content-type: application/json" --header="Accept: application/json" --header="Authorization: Basic USER:PASS" /api/rest/appliance/A1?select=id,name,service_tag {"id":"A1","name":"XXX-X-XXXXX","service_tag":"XXXXXXX"}

I will send you the whole list tomorrow.

Regards,

Bertrand.

On 2021-09-13 15:31, qgarnier wrote:

I need the login system. Otherwise:

alert (GET /alert)

appliance (GET /appliance)

cluster (GET /cluster)

filesystem (GET /file_system)

hardware (GET /hardware)

nas server (GET /nas_server)

physical_switch (GET /physical_switch)

volume (GET /volume)

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/centreon/centreon-plugins/issues/3086#issuecomment-918194605 [2] https://github.com/notifications/unsubscribe-auth/AHLZQSZCF2XVXSDZELRJJATUBX4L3ANCNFSM5DUQZTYQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

garnier-quentin commented 3 years ago

Ok it's a basic auth.

BertrandJO commented 3 years ago

Hi,

Here some examples for the requested get list (attached files) :

* alert (GET /alert) -> OK
* appliance (GET /appliance) -> OK
* cluster (GET /cluster) -> OK
* filesystem (GET /file_system) -> NOK
* hardware (GET /hardware) -> OK
* nas server (GET /nas_server) -> NOK
* physical_switch (GET /physical_switch) -> NOK
* volume (GET /volume) -> OK

I can not give you informations about the NAS part as we are only using storage containers through VASA vcenter API.

In the next days, I will send you examples for this part, our configurations are not fully completed.

I also join the openapi.json, hope this help.

Regards,

On 2021-09-13 17:18, qgarnier wrote:

Ok it's a basic auth.

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/centreon/centreon-plugins/issues/3086#issuecomment-918300266 [2] https://github.com/notifications/unsubscribe-auth/AHLZQSZJ6BBT52G2LJLDQI3UBYI45ANCNFSM5DUQZTYQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub wget --no-check-certificate -qO- -X GET --header="Content-type: application/json" --header="Accept: application/json" --header="Authorization: Basic $credentials" "https://X.X.X.X/api/rest/alert?select=id,name,severity,state,resource_name,generated_timestamp"

[{"id":"0","name":"XXX-X-XXXXXX-CLUSTER","master_appliance_id":"A1","state":"Configured"}]

wget --no-check-certificate -qO- -X GET --header="Content-type: application/json" --header="Accept: application/json" --header="Authorization: Basic $credentials" "https://X.X.X.X/api/rest/hardware?select=id,name,extra_details"

[{"id":"26018c5b69264a868e49119eec95b0a9","name":"Drive_0_0_1","extra_details":{"firmware_version":"GPJ99E5Q","drive_type":"NVMe_SSD","size":3840755982336,"encryption_status":"Supported_Locked_Cluster_PIN","fips_status":"FIPS_Compliance_Level_1"}}, {"id":"2a202181824248beb20ae2a7e53d6fc9","name":"Drive_0_0_4","extra_details":{"firmware_version":"GPJ99E5Q","drive_type":"NVMe_SSD","size":3840755982336,"encryption_status":"Supported_Locked_Cluster_PIN","fips_status":"FIPS_Compliance_Level_1"}}, {"id":"5fb410bc89ba44fc832130bde1b89d9f","name":"Drive_0_0_0","extra_details":{"firmware_version":"GPJ99E5Q","drive_type":"NVMe_SSD","size":3840755982336,"encryption_status":"Supported_Locked_Cluster_PIN","fips_status":"FIPS_Compliance_Level_1"}}, {"id":"927667aa1c0d488b86a83bc2fed4b2b2","name":"Drive_0_0_5","extra_details":{"firmware_version":"GPJ99E5Q","drive_type":"NVMe_SSD","size":3840755982336,"encryption_status":"Supported_Locked_Cluster_PIN","fips_status":"FIPS_Compliance_Level_1"}}, {"id":"ee5a571762134bddbbdff6a4694de377","name":"Drive_0_0_3","extra_details":{"firmware_version":"GPJ99E5Q","drive_type":"NVMe_SSD","size":3840755982336,"encryption_status":"Supported_Locked_Cluster_PIN","fips_status":"FIPS_Compliance_Level_1"}}, {"id":"fa2b244c1ae9439a8b53f9552c289f2f","name":"Drive_0_0_2","extra_details":{"firmware_version":"GPJ99E5Q","drive_type":"NVMe_SSD","size":3840755982336,"encryption_status":"Supported_Locked_Cluster_PIN","fips_status":"FIPS_Compliance_Level_1"}}] { "swagger" : "2.0", "info" : { "title" : "PowerStore REST API", "description" : "Storage cluster REST API definition. ( For \"Try It Out\", use the cluster management IP address to load this swaggerui interface. )", "version" : "2.0.0.0", "license" : { "name" : "End User License Agreement", "url" : "/locales/en-US/eula.txt" } }, "host" : "172.22.3.22", "tags" : [ { "description" : "Use these resource types to manage events and alerts in the system.", "name" : "alert" }, { "description" : "Manage appliances", "name" : "appliance" }, { "description" : "Use this resource type to query audit log information.", "name" : "audit_event" }, { "description" : "Use this resource types to manage the configuration of bonds. Bonds are implemented in pairs on each storage processor of the appliance.", "name" : "bond" }, { "description" : "CHAP is enabled (or not) identically cluster-wide for all iSCSI targets. For both single and mutual CHAP authentication modes, the common username and password for all targets on the cluster are set here. For mutual mode, each initiator also has a CHAP username and password set. Changing the cluster CHAP mode disrupts all iSCSI connections, and will disable connections that are not completely and correctly configured. For example, an initiator without a valid CHAP username and password will lose connectivity to the target if mutual model is enable here. Both the settings here, and the settings on the initiators can be modified while CHAP mode is in disabled mode.", "name" : "chap_config" }, { "description" : "Manage clusters", "name" : "cluster" }, { "description" : "Use this resource type to list initiators currently connected to the cluster that are not associated with a host.", "name" : "discovered_initiator" }, { "description" : "Manage DNS and NTP settings for the cluster.", "name" : "dns" }, { "description" : "Use these resource types to configure outgoing SMTP and email notifications.", "name" : "email_notify_destination" }, { "description" : "This is the REST API for cluster-wide retrieval and configuration of Ethernet front-end ports.\n", "name" : "eth_port" }, { "description" : "Use these resource types to manage events and alerts in the system.", "name" : "event" }, { "description" : "Use this resource type to retrieve information about Fibre Channel (FC) front-end ports and to set their connection speeds.\n", "name" : "fc_port" }, { "description" : "Information about File network interfaces in the storage system. These interfaces control access to Windows (CIFS) and UNIX/Linux (NFS) file storage.", "name" : "file_interface" }, { "description" : "Use this resource type to manage NDMP services. NDMP is a standard for backing up file servers on a network. NDMP allows centralized applications to back up file servers that run on various platforms and platform versions. NDMP reduces network congestion by isolating control path traffic from data path traffic, which permits centrally managed and monitored local backup operations. Storage systems support NDMP v2-v4 over the network. Direct-attach NDMP is not supported. This means that the tape drives need to be connected to a media server, and the NAS server communicates with the media server over the network. NDMP has an advantage when using multiprotocol file systems because it backs up the Windows ACLs as well as the UNIX security information.", "name" : "file_ndmp" }, { "description" : "Use this resource type to manage NAS file systems.", "name" : "file_system" }, { "description" : "Use these resource types to manage the virus checker service of a NAS server. A virus checker instance is created each time the anti-virus service is enabled on a NAS server. A configuration file (named viruschecker.conf) needs to be uploaded before enabling the anti-virus service.\nThe cluster supports third-party anti-virus servers that perform virus scans and reports back to the storage system. For example, when an SMB client creates, moves, or modifies a file, the NAS server invokes the anti-virus server to scan the file for known viruses. During the scan any access to this file is blocked. If the file does not contain a virus, it is written to the file system. If the file is infected, corrective action (fixed, removed or placed in quarantine) is taken as defined by the anti-virus server. You can optionally set up the service to scan the file on read access based on last access of the file compared to last update of the third-party anti-virus date.\n", "name" : "file_virus_checker" }, { "description" : "This provides the hardware component inventory of the system.", "name" : "hardware" }, { "description" : "Use this resource type to manage hosts that access the cluster.\nOnly External type hosts can be managed directly, Internal type hosts are managed automatically by the system and cannot be created, deleted, modified, nor can their storage associations.", "name" : "host" }, { "description" : "Use this resource type to manage host groups.\nA host group is a mechanism to provision hosts and volumes to be consistent across the Cyclone cluster. Operations that can be performed include, creating or deleting a host group, modifying host group (i.e. adding or removing hosts from a host group).", "name" : "host_group" }, { "description" : "Storage cluster REST API definition.", "name" : "host_volume_mapping" }, { "description" : "Virtual volume mapping details.", "name" : "host_virtual_volume_mapping" }, { "description" : "Use these resource types to manage import host initiators. Once import host is configured, host initiators can be queried and corresponding mapped volumes can be imported.", "name" : "import_host_initiator" }, { "description" : "Use these resource types to manage import host systems. Import host enables communication with multipathing software on the host system to perform import operations. While configuring the import_host_system if the host is not present a new Host will be created. If Host is already present, the same Host will be updated with the import_host_system details. Also, import_host_system supports FC and ISCSI connections between Host and source arrays. So for a single import_host_system which supports both FC and ISCSI; there would be two Hosts entries for representing the FC and iSCSI connections.", "name" : "import_host_system" }, { "description" : "Use these resource types to manage import host volumes. Host volumes are source storage volumes that are mapped to the host systems for application access. Once import host is configured, host volumes can be queried and then corresponding volumes can be imported.", "name" : "import_host_volume" }, { "description" : "Use these resource types to discover the Peer Storage Group (PS Group) volumes that can be imported to PowerStore.", "name" : "import_psgroup" }, { "description" : "Use these resource types to discover the Peer Storage Group (PS Group) volumes that can be imported to PowerStore.", "name" : "import_psgroup_volume" }, { "description" : "Use the import_session resource type to initiate and manage the migration of volumes and consistency groups from a heritage Dell EMC storage system to a PowerStore storage system. The import is non-disruptive to hosts that access the volume during the import. The import process runs as a background job. Clients should poll the job status until the import completes. Note: In these descriptions, LUNs are referred to as volumes and storage arrays are referred to as storage systems.", "name" : "import_session" }, { "description" : "Use these resource types to discover the Storage Center (SC) volumes and consistency groups that can be imported to PowerStore.", "name" : "import_storage_center" }, { "description" : "Use these resource types to discover the Storage Center (SC) volumes and consistency groups that can be imported to PowerStore.", "name" : "import_storage_center_consistency_group" }, { "description" : "Use these resource types to discover the Storage Center (SC) volumes that can be imported to PowerStore.", "name" : "import_storage_center_volume" }, { "description" : "Use this resource type to discover the Unity system that is a source storage system for import", "name" : "import_unity" }, { "description" : "Use this resource type to discover the Unity consistency groups that can be imported to PowerStore.", "name" : "import_unity_consistency_group" }, { "description" : "Use this resource type to discover the Unity volumes that can be imported to PowerStore.", "name" : "import_unity_volume" }, { "description" : "Use these resource types to discover the VNX storage system that can be imported to PowerStore.", "name" : "import_vnx_array" }, { "description" : "Use this resource type to show the VNX consistency groups that can be imported to PowerStore.", "name" : "import_vnx_consistency_group" }, { "description" : "Use this resource type to show the VNX volumes and that can be imported to PowerStore.", "name" : "import_vnx_volume" }, { "description" : "Use these resource types to discover the XtremIO volumes and consistency groups that can be imported to PowerStore.", "name" : "import_xtremio" }, { "description" : "Use these resource types to discover the XtremIO volumes and consistency groups that can be imported to PowerStore.", "name" : "import_xtremio_consistency_group" }, { "description" : "Use these resource types to discover the XtremIO volumes and consistency groups that can be imported to PowerStore.", "name" : "import_xtremio_volume" }, { "description" : "Use these resource types to scale and reconfigure the IP networks in a cluster.", "name" : "ip_pool_address" }, { "description" : "Use these resource types to manage the cluster-wide configuration of virtual IP ports, bonds, and virtual Ethernet ports.\n", "name" : "ip_port" }, { "description" : "Use this resource type for tracking an operation's progress and status.", "name" : "job" }, { "description" : "Use this resource to generate and download an encryption keystore archive file.", "name" : "keystore_archive" }, { "description" : "Use this resource type to view and manage the software license for the cluster. \n\nLicenses are normally automatically retrieved when the system is configured. If the system cannot reach the DellEMC Software Licensing Central, it will retry daily during the 30-day trial period. After the trial period, the system will continue to operate but no new provisioning operations will be allowed. \n\n\nWhen an appliance is added to the cluster, the process starts over, and the cluster license will need to be updated, either automatically, or manually if network connectivity to the Software Licensing Central is not available.\n\nIf the system lacks network connectivity to reach the Software Licensing Central, an alert will be raised that indicates when the trial period will expire. For sites that do not allow connection to the Software Licensing Central, there is an alternate mechanism to license the cluster:\n1. Get the license activation file from the system.\n2. Log on to the DellEMC Software Licensing Central as a customer and provide the activation file. You will receive a license file back.\n3. Upload the license file to the system.\n \n", "name" : "license" }, { "description" : "Use this resource type to manage local user accounts.", "name" : "local_user" }, { "description" : "Use this resource type to manage LDAP accounts that map to LDAP users or groups in LDAP server to administrative roles on the PowerStore array.", "name" : "ldap_account" }, { "description" : "Use this resource type to manage ldap configuration.", "name" : "ldap_domain" }, { "description" : "Use these resource types to manage sessions, roles, and system security configurations.", "name" : "login_session" }, { "description" : "Use these resource types to manage sessions, roles, and system security configurations.", "name" : "logout" }, { "description" : "Use this resource type to manage the maintenance window configuration for each appliance. The maintenance window allows you to set a time period during which alerts do not generate any notifications. After the specified interval (1-48 hours), the maintenance window will get automatically disabled and any alerts that are still outstanding will generate notifications. Specifically, anything that would have generated a notification but didn't do so because of the maintenance window and that remains outstanding after the window closes, will result in a notification when the window is disabled.", "name" : "maintenance_window" }, { "name" : "metrics", "description" : "REST APIs Use these resource types to query historical metric data." }, { "description" : "The system produces migration recommendations periodically or upon request, based on capacity usage and recent performance. A recommendation can then be implemented using the create_migration_sessions action, performing any necessary rescans on attached hosts, and then using start_migration_sessions.", "name" : "migration_recommendation" }, { "description" : "Manage migration sessions.", "name" : "migration_session" }, { "description" : "Use these resource types to manage NAS servers. NAS servers are software components used to transfer data and provide the connection ports for hosts to access file-based storage resources. NAS servers are independent from each other.", "name" : "nas_server" }, { "description" : "Use these resource types to scale and reconfigure the IP networks in a cluster.", "name" : "network" }, { "description" : "Use this resource type to manage NFS servers. One NFS server may be configured per NAS server. At least one NFS share must be created from an NFS server before an NFS client can connect to the storage resources. NFS servers can support the NFSv3 and NFSv4 protocols. The default protocol is NFSv3. It is enabled when the NFS server is created and remains active until the NFS server is deleted.", "name" : "nfs_server" }, { "description" : "Use this resource type to retrieve information about nodes in a cluster.\n", "name" : "node" }, { "description" : "Manage DNS and NTP settings for the cluster.", "name" : "ntp" }, { "description" : "Information about performance rules that can be use in performance policies applied to volumes and volume groups.", "name" : "performance_rule" }, { "description" : "Manage physical switches settings for the cluster.", "name" : "physical_switch" }, { "description" : "Use this resource type to manage protection policies and to view information about performance policies.\n\nNote: Performance policies are predefined for high, low, and medium performance. They cannot be added to or changed.", "name" : "policy" }, { "description" : "Manage remote support contact.", "name" : "remote_support_contact" }, { "description" : "Information about remote storage systems that connect to the local PowerStore system. The system uses the configuration to access and communicate with the remote system for management and data transfer communications. \nFor example, to use remote replication, create a configuration that specifies the remote system to use as the destination for the replication session.\n\nThe PowerStore local system can establish a remote system relationship with different types of remote storage systems for replication remote protection and import use-cases. Refer to the RemoteSystemTypeEnum specification for a list of system types supported. \nNOTE\nBefore creating a remote system relationship with PowerStore remote systems, first establish a Certificate Based Trust between the local and remote PowerStore systems using the verify and exchange operations on the x509_certificate resource type.\n", "name" : "remote_system" }, { "description" : "Use this resource type to manage the replication rules that are used in protection policies.", "name" : "replication_rule" }, { "description" : "Use this resource type to manage replication sessions for storage resources in the system. Replication sessions operate on volume and volume_group resource types. Replication sessions are created and deleted through protection policies on the storage resources.\n\n\n\nIn addition to copying data, the replication session synchronizes configuration changes on source resource and replicates user and scheduled snapshots to destination system. \n\n\n\nReplication sessions provide disaster recovery failover, reprotect and failback capabilities. As a result:\n The downtime-associated cost of a system failure is minimized.\n The recovery process from a disaster is facilitated.\n\n\n\nReplication sessions also provides pause and resume capabilities, to allow for production or disaster recovery-side maintenance requirements.\n\n\n\nDestination storage resources are in replication destination mode, which disables any write access to the destination resource. Any operations such as resizing the volume, restoring the snapshot, or changing membership for a volume group on the resource are not allowed.\n\n\n\nOn the source end, volumes can be expanded, and volume group membership changes are allowed during any states of a replication session. \n\n\n", "name" : "replication_session" }, { "description" : "Use these resource types to manage sessions, roles, and system security configurations.", "name" : "role" }, { "description" : "Use this resource type to retrieve information about SAS ports.\n", "name" : "sas_port" }, { "description" : "system security configuration", "name" : "security_config" }, { "description" : "Manage the service configuration for each appliance. \n * 'SSH Access' - Manage the ability for the service user to remotely connect to the nodes in an appliance using SSH.", "name" : "service_config" }, { "description" : "Use this resource type to manage the service user account.\nThe system includes the default service_user account with the username 'service'. The service user account cannot authenticate through the REST, CLI, or graphical user interfaces. You cannot create more service user accounts or delete the default service user account. During the intial configuration, along with the default admin user account, a password change for the service user account is also required.\n\n\n Only the default service_user account can log in via SSH. Ensure that SSH is enabled on the system for the service_user to log in. SSH can be enabled or disabled using the service_config modify operation.", "name" : "service_user" }, { "description" : "Use these resource types to manage Server Message Block (SMB) servers. SMB is a protocol for sharing files and communications abstractions such as named pipes and mail slots between computers. Most usage of SMB involves computers running Microsoft Windows, but it is commonly supported on other types of systems as well. SMB was formerly known as Common Internet File System (CIFS). \nAn SMB server must be created on a NAS server before SMB shares can be created on the file systems on that NAS server. An SMB server can be created as a standalone server or as a server that belongs to an Active Directory domain (often a Window domain). In that case, DNS must be enabled on the NAS server. The credentials of an administrator of the domain are required to join that domain. An NTP server must be defined also, to prevent authentication errors caused by unsynchronized clocks. Each NAS server supports a maximum of one SMB server.\n", "name" : "smb_server" }, { "description" : "SMB Shares use the SMB protocol to provide an access point for configured Windows hosts to access file system storage. The system uses Active Directory to authenticate user and user group access to the Share.", "name" : "smb_share" }, { "description" : "Manage SNMP server destinations for SNMP alert notifications. All defined SNMP servers receive notifications for any alerts at or above their defined alert_severity level.", "name" : "snmp_server" }, { "description" : "Use these resource types to configure outgoing SMTP and email notifications.", "name" : "smtp_config" }, { "description" : "Use this resource type to manage snapshot rules that are used in protection policies.", "name" : "snapshot_rule" }, { "description" : "Software upgrade functionality. Only one upgrade can be active at a time.", "name" : "software_installed" }, { "description" : "Software upgrade functionality. Only one upgrade can be active at a time.", "name" : "software_package" }, { "description" : "Manage storage containers. A storage container is a logical grouping of related storage objects in a cluster. A storage container corresponds to a vVol datastore in vCenter and is used to group related vVols and track the amount of space that is used/free.", "name" : "storage_container" }, { "description" : "Use this resource type to manage vCenter instances. Registered vCenter enables discovering of virtual machines, managing virtual machine snapshots, automatic mounting of storage container and other functionality that requires communication with vCenter. In Unified+ deployments, the one vCenter instance residing in the PowerStore cluster will be prepopulated here and cannot be deleted, nor may any other vCenters be added. For Unified deployments, one external vCenter may be configured if desired.", "name" : "vcenter" }, { "description" : "Use these resource types to manage the cluster-wide configuration of virtual IP ports, bonds, and virtual Ethernet ports.\n", "name" : "veth_port" }, { "description" : "Use this resource type to retrieve cached information from vCenter about virtual machines (VMs) that use storage from the cluster or to create a snapshot of a VM.", "name" : "virtual_machine" }, { "description" : "Information about virtual volumes, which are managed through vCenter.", "name" : "virtual_volume" }, { "description" : "Use these resource types to manage volumes, including snapshots and clones of volumes.", "name" : "volume" }, { "description" : "Use this resource type for storage cluster REST API definition.", "name" : "volume_group" }, { "description" : "Use this resource type to manage SSL/TLS certificates. The X509 Certificate service is part of the credential store services. An X509 Certificate in this service represents a certificate chain, composed of the certificate of each individual member in ordered sequence. If the X509 Certificate is used as a server certificate or client certificate, it also includes the private key.", "name" : "x509_certificate" }, { "description" : "NFS Exports use the NFS protocol to provide an access point for configured Linux/Unix hosts or IP subnets to access file_systems or file_snapshots.\n", "name" : "nfs_export" }, { "description" : "Use this resource type to manage tree quota settings in the storage system. A tree quota instance represents a quota limit applied to a specific directory tree in a file system.", "name" : "file_tree_quota" }, { "description" : "User quota settings in the storage system. A user quota instance represents a quota limit applied to a user within a quota tree or a filesystem.", "name" : "file_user_quota" }, { "description" : "Use these resources to configure the Domain Name System (DNS) settings for a NAS server. One DNS settings object may be configured per NAS server. A DNS is a hierarchical system responsible for converting domain names to their corresponding IP addresses. A NAS server\'s DNS settings should allow DNS resolution of all names within an SMB server\'s domain in order for the SMB protocol to operate normally within an Active Directory domain. The DNS default port is 53.", "name" : "file_dns" }, { "description" : "Use this resource type to configure one File Transfer Protocol (FTP) server per NAS server. One FTP server can be configured per NAS server to have both secure and unsecure services running. By default when an FTP server is created, the unsecure service will be running. FTP is a standard network protocol used to transfer files from one host to another host over a TCP-based network, such as the Internet. For secure transmission that encrypts the username, password, and content, FTP is secured with SSH (SFTP). SFTP listens on port 22.\nYou can activate an FTP server and SFTP server independently on each NAS server. The FTP and SFTP clients are authenticated using credentials defined on a Unix name server (such as an NIS server or an LDAP server) or a Windows domain. Windows user names need to be entered using the @.*' or 'domain\\username' formats. Each secure and unsecure service must have a home directory defined in the name server that must be accessible on the NAS server. FTP also allows clients to connect as anonymous users. \n", "name" : "file_ftp" }, { "description" : "Use this resource type to manage static IP routes, including creating,\nmodifying, and deleting these routes.\n\n\nA route determines where to send a packet, next so it can reach its final destination.\nA static route is set explicitly and does not automatically adapt to the changing\nnetwork infrastructure. A route is defined by an interface, destination IP address\nrange and an IP address of a corresponding gateway.\n\n\nNote*: IP routes connect an interface (IP address) to the larger network through\ngateways. Without routes and gateway specified, the interface is no longer accessible\noutside of its immediate subnet. As a result, network shares and exports associated\nwith the interface are no longer available to clients outside their immediate subnet.\n", "name" : "file_interface_route" }, { "description" : "Use these resources to manage the Kerberos service for a NAS server. One Kerberos service object may be configured per NAS Server. Kerberos is a distributed authentication service designed to provide strong authentication with secret-key cryptography. It works on the basis of \"tickets\" that allow nodes communicating over a non-secure network to prove their identity in a secure manner. When configured to act as a secure NFS server, the NAS Server uses the RPCSEC_GSS security framework and Kerberos authentication protocol to verify users and services. You can configure a secure NFS environment for a multiprotocol NAS Server or one that supports Unix-only shares. In this environment, user access to NFS file systems is granted based on Kerberos principal names.", "name" : "file_kerberos" }, { "description" : "Use these resources to manage the Lightweight Directory Access Protocol (LDAP) settings for the NAS Server. You can configure one LDAP settings object per NAS Server. LDAP is an application protocol for querying and modifying directory services running on TCP/IP networks. LDAP provides central management for network authentication and authorization operations by helping to centralize user and group management across the network. A NAS Server can use LDAP as a Unix Directory Service to map users, retrieve netgroups, and build a Unix credential. When an initial LDAP configuration is applied, the system checks for the type of LDAP server. It can be an Active Directory schema or an RFC 2307 schema.", "name" : "file_ldap" }, { "description" : "Use these resources to manage the Network Information Service (NIS) settings object for a NAS Server. One NIS settings object may be configured per NAS server. NIS consists of a directory service protocol for maintaining and distributing system configuration information, such as user and group information, hostnames, and such. The port for NIS Service is 111.", "name" : "file_nis" }, { "description" : "Use this resource type to manage remote syslog server(s).", "name" : "remote_syslog_server" } ], "x-categories" : { "Compute" : { "description" : "Manage host configurations, virtual machines and VMware integration", "tags" : [ "host", "host_group", "host_volume_mapping", "host_virtual_volume_mapping", "discovered_initiator", "vcenter", "virtual_machine" ] }, "Migration" : { "description" : "Manage data import and data migration from remote systems", "tags" : [ "import_host_initiator", "import_host_system", "import_host_volume", "import_psgroup", "import_psgroup_volume", "import_session", "import_storage_center", "import_storage_center_consistency_group", "import_storage_center_volume", "import_unity", "import_unity_consistency_group", "import_unity_volume", "import_vnx_array", "import_vnx_consistency_group", "import_vnx_volume", "import_xtremio", "import_xtremio_consistency_group", "import_xtremio_volume", "migration_recommendation", "migration_session" ] }, "Monitoring" : { "description" : "View event logs and alerts", "tags" : [ "alert", "event", "job", "metrics", "remote_syslog_server" ] }, "Protection" : { "description" : "Manage replication and data protection rules", "tags" : [ "policy", "remote_system", "replication_rule", "replication_session", "snapshot_rule" ] }, "Settings" : { "description" : "Configure general settings on the system including:\n Networking\n Licensing\n Updates\n", "tags" : [ "license", "logout", "software_installed", "software_package", "email_notify_destination", "chap_config", "local_user", "ldap_account", "ldap_domain", "login_session", "keystore_archive", "role", "security_config", "x509_certificate", "audit_event", "ip_pool_address", "ip_port", "network", "ntp", "dns", "smtp_config", "physical_switch", "snmp_server" ] }, "Storage" : { "description" : "Storage configuration of the system:\n Create delete storage resources\n Configure NAS servers\n", "tags" : [ "storage_container", "virtual_volume", "volume", "nas_server", "nfs_server", "smb_server", "file_interface", "file_ndmp", "file_virus_checker", "performance_rule", "file_system", "smb_share", "volume_group", "file_tree_quota", "file_user_quota", "file_dns", "file_ftp", "file_interface_route", "file_kerberos", "file_ldap", "file_nis", "nfs_export" ] }, "Support" : { "description" : "Manage service user credentials, perform service actions on the system", "tags" : [ "service_config", "service_user", "maintenance_window", "remote_support_contact" ] }, "System and Hardware" : { "description" : "Manage hardware, view component health status, change cluster configuration", "tags" : [ "appliance", "cluster", "node", "hardware", "eth_port", "fc_port", "sas_port", "veth_port", "bond" ] } }, "schemes" : [ "https" ], "basePath" : "/api/rest", "produces" : [ "application/json" ], "consumes" : [ "application/json" ], "paths" : { "/appliance" : { "get" : { "tags" : [ "appliance" ], "summary" : "Collection Query", "description" : "Query the appliances in a cluster.", "responses" : { "200" : { "description" : "Success", "schema" : { "type" : "array", "items" : { "$ref" : "#/definitions/appliance_instance" } } }, "206" : { "description" : "Partial content of appliance instance objects", "schema" : { "type" : "array", "items" : { "$ref" : "#/definitions/appliance_instance" } } }

garnier-quentin commented 3 years ago

Some curl are missing:

volume (GET /volume)

For the hardware, you didn't provide usefull fields. I need to get (i think): status_led_state. Could you provide me all fields ? I could check what it's useful for monitoring.

BertrandJO commented 3 years ago

For the volume part :

wget --no-check-certificate -qO- -X GET --header="Content-type: application/json" --header="Accept: application/json" --header="Authorization: Basic $credentials" "https://X.X.X.X/api/rest/volume" [{"id":"e82c3678-7d86-44bb-bead-2a47f90f0b29"}

wget --no-check-certificate -qO- -X GET --header="Content-type: application/json" --header="Accept: application/json" --header="Authorization: Basic $credentials" "https://X.X.X.X/api/rest/volume/e82c3678-7d86-44bb-bead-2a47f90f0b29?select=*" {"id":"e82c3678-7d86-44bb-bead-2a47f90f0b29","name":"test-monitoring","description":"","type":"Primary","wwn":"naa.68ccf09800a023ab731d36e77d150207","nsid":2,"nguid":"nguid.a023ab731d36e77d8ccf096800150207","appliance_id":"A1","state":"Ready","size":107374182400,"node_affinity":"System_Select_At_Attach","creation_timestamp":"2021-09-20T08:14:14.74783+00:00","protection_policy_id":null,"performance_policy_id":"default_low","is_replication_destination":false,"migration_session_id":null,"protection_data":{"family_id": "e82c3678-7d86-44bb-bead-2a47f90f0b29", "parent_id": null, "source_id": null, "creator_type": "User", "copy_signature": null, "source_timestamp": null, "creator_type_l10n": "User", "is_app_consistent": false, "created_by_rule_id": null, "created_by_rule_name": null, "expiration_timestamp": null},"location_history":null,"type_l10n":"Primary","state_l10n":"Ready","node_affinity_l10n":"System Select At Attach"}

For hardware details :

wget --no-check-certificate -qO- -X GET --header="Content-type: application/json" --header="Accept: application/json" --header="Authorization: Basic $credentials" "https://X.X.X.X/api/rest/hardware?select=*"

One interesting check would be for storage containers :

wget --no-check-certificate -qO- -X GET --header="Content-type: application/json" --header="Accept: application/json" --header="Authorization: Basic $credentials" "https://X.X.X.X/api/rest/storage_container" [{"id":"064e2869-eb64-4005-9d32-3551b6d3adfc"}]

I will send you more informations on this part.

Note : credentials="$(echo -n "$username:$password" | base64)"

Regards,

On 2021-09-17 15:07, qgarnier wrote:

Some curl are missing:

volume (GET /volume)

For the hardware, you didn't provide usefull fields. I need to get (i think): status_led_state. Could you provide me all fields ? I could check what it's useful for monitoring.

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/centreon/centreon-plugins/issues/3086#issuecomment-921782673 [2] https://github.com/notifications/unsubscribe-auth/AHLZQS5KHZZONS5H6SZW4DTUCM4S3ANCNFSM5DUQZTYQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

garnier-quentin commented 3 years ago

For the hardware, we have the lifecycle_state. We can do a hardware and alerts modes.

garnier-quentin commented 3 years ago

Could you test with following branch ? https://github.com/centreon/centreon-plugins/archive/refs/heads/add-plugin-dell-powerstore.zip

$ perl centreon_plugins.pl --plugin=storage::dell::powerstore::restapi::plugin.pm --mode=alerts --hostname=xxxxx --api-username=xxxxx --api-password=xxxxx --verbose
$ perl centreon_plugins.pl --plugin=storage::dell::powerstore::restapi::plugin.pm --mode=hardware --hostname=xxxxx --api-username=xxxxx --api-password=xxxxx --verbose

BertrandJO commented 3 years ago

Here are the results :

$ ./centreon_plugins.pl --plugin=storage::dell::powerstore::restapi::plugin.pm --mode=alerts --hostname=X.X.X.X --api-username=xxxxx --api-password=xxxxxxx --verbose --ssl-opt="SSL_verify_mode => SSL_VERIFY_NONE" OK: 0 alerts detected | 'alerts.severity.none.count'=0;;;0; 'alerts.severity.info.count'=0;;;0; 'alerts.severity.minor.count'=0;;;0; 'alerts.severity.major.count'=0;;;0; 'alerts.severity.critical.count'=0;;;0; 'alerts.problems.current.count'=0;;;0;

-> no current alert so the result is fine, i will try to catch an alert

$ ./centreon_plugins.pl --plugin=storage::dell::powerstore::restapi::plugin.pm --mode=hardware --hostname=X.X.X.X --api-username=xxxxx --api-password=xxxxxxx --verbose --ssl-opt="SSL_verify_mode => SSL_VERIFY_NONE" OK: All 73 components are ok [2/2 battery, 24/24 dimm, 8/8 disk, 1/1 enclosure, 12/12 fan, 6/6 iomodule, 2/2 node, 2/2 psu, 16/16 sfp]. | 'hardware.battery.count'=2;;;; 'hardware.dimm.count'=24;;;; 'hardware.disk.count'=8;;;; 'hardware.enclosure.count'=1;;;; 'hardware.fan.count'=12;;;; 'hardware.iomodule.count'=6;;;; 'hardware.node.count'=2;;;; 'hardware.psu.count'=2;;;; 'hardware.sfp.count'=16;;;; checking appliance checking battery battery 'BaseEnclosure-NodeB-InternalBatteryBackupModule1' status is 'Healthy' [instance: c87eba8238874205908de51cd2c131ff] battery 'BaseEnclosure-NodeA-InternalBatteryBackupModule0' status is 'Healthy' [instance: e65fbb89282543e2961354ca1bffe54b] checking dimm dimm 'BaseEnclosure-NodeB-DIMM10' status is 'Empty' [instance: 02049bb0ed2047d99695c0b8bf9bf5b6] dimm 'BaseEnclosure-NodeB-DIMM0' status is 'Healthy' [instance: 0257dba263b04d3096994e0d2d06e6ea] dimm 'BaseEnclosure-NodeB-DIMM3' status is 'Empty' [instance: 1e6bb720561443b8a6399d3b685ef034] dimm 'BaseEnclosure-NodeB-DIMM7' status is 'Healthy' [instance: 297b6a96cae944a8ba3098a833a1b5de] dimm 'BaseEnclosure-NodeA-DIMM2' status is 'Healthy' [instance: 36ad6a429fa34044b2ba5262d7ad23c5] dimm 'BaseEnclosure-NodeB-DIMM6' status is 'Empty' [instance: 3c7c845a3acf485ca7e615bc6d9ed0ab] dimm 'BaseEnclosure-NodeA-DIMM0' status is 'Healthy' [instance: 519b2f9508104292b72eafe9a47ab7db] dimm 'BaseEnclosure-NodeB-DIMM9' status is 'Healthy' [instance: 5224f9f2a4fd4c7f8ea36bee1f3ef7ce] dimm 'BaseEnclosure-NodeA-DIMM8' status is 'Empty' [instance: 5649a7f0b5f24f768bda25504257235b] dimm 'BaseEnclosure-NodeB-DIMM11' status is 'Healthy' [instance: 5b049ca52dbf4b51a6c6a74c1a33f9af] dimm 'BaseEnclosure-NodeA-DIMM3' status is 'Empty' [instance: 645315bf3a4d49cd91d9f033f5b73611] dimm 'BaseEnclosure-NodeA-DIMM1' status is 'Empty' [instance: 6aa2b85572cf4d8a914754446db7cbba] dimm 'BaseEnclosure-NodeA-DIMM4' status is 'Healthy' [instance: 7b1ebbb869b34a6aa715666c27d6800c] dimm 'BaseEnclosure-NodeA-DIMM10' status is 'Empty' [instance: 7bcb6b85d1b142ab8dc3c2851b231a5f] dimm 'BaseEnclosure-NodeA-DIMM5' status is 'Empty' [instance: 7f7665cbe8cf480994386de9052ee863] dimm 'BaseEnclosure-NodeA-DIMM11' status is 'Healthy' [instance: a3e0f113a2e84b2091930f4069db51e0] dimm 'BaseEnclosure-NodeA-DIMM7' status is 'Healthy' [instance: b7e0cef9e0be445a9861b4e3466a1d61] dimm 'BaseEnclosure-NodeB-DIMM4' status is 'Healthy' [instance: c4617e5152bb47669d2d4f40a6ebe5cd] dimm 'BaseEnclosure-NodeB-DIMM2' status is 'Healthy' [instance: c9df410a5d24457886cdb66cc00df284] dimm 'BaseEnclosure-NodeB-DIMM1' status is 'Empty' [instance: d851fe7492b64b12816cfe6cb200209d] dimm 'BaseEnclosure-NodeB-DIMM8' status is 'Empty' [instance: dbf0f208608147bb91fd35b34b38315e] dimm 'BaseEnclosure-NodeA-DIMM6' status is 'Empty' [instance: e53bd0f178ef4e07bbe6c883391f30a4] dimm 'BaseEnclosure-NodeB-DIMM5' status is 'Empty' [instance: ef876acc647540f7b79ea45adc846eac] dimm 'BaseEnclosure-NodeA-DIMM9' status is 'Healthy' [instance: fe220f57d7f340aa967e5222b27114b2] checking disk disk 'Drive_0_0_1' status is 'Healthy' [instance: 26018c5b69264a868e49119eec95b0a9] disk 'Drive_0_0_4' status is 'Healthy' [instance: 2a202181824248beb20ae2a7e53d6fc9] disk 'Drive_0_0_0' status is 'Healthy' [instance: 5fb410bc89ba44fc832130bde1b89d9f] disk 'Drive_0_0_5' status is 'Healthy' [instance: 927667aa1c0d488b86a83bc2fed4b2b2] disk 'Drive_0_0_3' status is 'Healthy' [instance: ee5a571762134bddbbdff6a4694de377] disk 'Drive_0_0_2' status is 'Healthy' [instance: fa2b244c1ae9439a8b53f9552c289f2f] disk 'BaseEnclosure-NodeA-InternalM.2BootModule0' status is 'Healthy' [instance: 0c5ac7335d8a4463b4b84f5d20c4418e] disk 'BaseEnclosure-NodeB-InternalM.2BootModule0' status is 'Healthy' [instance: dabaf4eb335e472eba62814122b6d696] checking enclosure enclosure 'BaseEnclosure' status is 'Healthy' [instance: 3f58a1202a1e46498a8e08d1a06ed204] checking fan fan 'BaseEnclosure-NodeB-FanModule0' status is 'Healthy' [instance: 1da21553498043a498f4df937ecd88c2] fan 'BaseEnclosure-NodeA-FanModule0' status is 'Healthy' [instance: 242e97ba241f4c6e8f5cfd276092eef6] fan 'BaseEnclosure-NodeA-FanModule1' status is 'Healthy' [instance: 3329bd4912c746748ad2c711e3e071be] fan 'BaseEnclosure-NodeA-FanModule4' status is 'Healthy' [instance: 352ccab6baa844278697624179c395cf] fan 'BaseEnclosure-NodeB-FanModule5' status is 'Healthy' [instance: 3d091cf34dd0473b8720ff8779289cd9] fan 'BaseEnclosure-NodeA-FanModule3' status is 'Healthy' [instance: 57983c279e5940358f97605182cf1b1f] fan 'BaseEnclosure-NodeB-FanModule2' status is 'Healthy' [instance: 743387c9878944cdbae889bbf31ffb14] fan 'BaseEnclosure-NodeB-FanModule1' status is 'Healthy' [instance: 827520167b19416982a3e9638e046fa0] fan 'BaseEnclosure-NodeA-FanModule5' status is 'Healthy' [instance: 86f8164bd2324aa6b6e7fa41653689c2] fan 'BaseEnclosure-NodeB-FanModule4' status is 'Healthy' [instance: 8f364020f8fe43ef803b6f8bfe7abcd5] fan 'BaseEnclosure-NodeA-FanModule2' status is 'Healthy' [instance: c41c5a99937e4953a180c65756f303f6] fan 'BaseEnclosure-NodeB-FanModule3' status is 'Healthy' [instance: ceed37685ede40ccabbb92896e1435af] checking node node 'BaseEnclosure-NodeB' status is 'Healthy' [instance: 091b25c8d2f248db93357a7b44216a54] node 'BaseEnclosure-NodeA' status is 'Healthy' [instance: 4f6fd04a8ff04a81bf06f609a953e45b] checking iomodule iomodule 'BaseEnclosure-NodeB-4PortCard' status is 'Healthy' [instance: 21bb5433f3794a649f4f8cc3571b4cbe] iomodule 'BaseEnclosure-NodeA-4PortCard' status is 'Healthy' [instance: 89c3f0a9e4c946e4a1633beecbf69aa1] iomodule 'BaseEnclosure-NodeB-IoModule1' status is 'Healthy' [instance: 96c2aa72699042d1a9681b480d9e58e6] iomodule 'BaseEnclosure-NodeA-IoModule1' status is 'Healthy' [instance: a198275b4ec048a1b99a6717f6fec8e1] iomodule 'BaseEnclosure-NodeB-IoModule0' status is 'Empty' [instance: bd51a101cd7e45d6888a011b25f1a107] iomodule 'BaseEnclosure-NodeA-IoModule0' status is 'Empty' [instance: c6f80bd41bee4e0f8fa8f8f39f6e934b] checking psu psu 'BaseEnclosure-NodeA-PSU0' status is 'Healthy' [instance: 0bc7370c7a7643b1a68bbb3ed62a869f] psu 'BaseEnclosure-NodeB-PSU0' status is 'Healthy' [instance: 572970d6d2a7482799200ce22ebc6245] checking sfp sfp 'BaseEnclosure-NodeB-4PortCard-SFP0' status is 'Empty' [instance: 03542fd43f7a46988de280375c01eb3c] sfp 'BaseEnclosure-NodeA-4PortCard-SFP0' status is 'Empty' [instance: 063f0cf8ca9a4d79b4cb1dd019a68c67] sfp 'BaseEnclosure-NodeA-IoModule1-SFP2' status is 'Healthy' [instance: 25ef1c818b7a481eb9e1ac80dde25074] sfp 'BaseEnclosure-NodeB-IoModule1-SFP2' status is 'Healthy' [instance: 2b488c10837043ec8a67f6d715b115e4] sfp 'BaseEnclosure-NodeB-IoModule1-SFP3' status is 'Healthy' [instance: 5cee903c232c45c2965102d8d3358ae9] sfp 'BaseEnclosure-NodeB-4PortCard-SFP3' status is 'Empty' [instance: 69fdea33ee2c4dd9a662f9d9f0e4e3d5] sfp 'BaseEnclosure-NodeA-IoModule1-SFP3' status is 'Healthy' [instance: 940c4f6bd8134e28ae7feca574d9bdb4] sfp 'BaseEnclosure-NodeB-4PortCard-SFP1' status is 'Empty' [instance: 9519416237bf4d50b2be4ecf6ffd8a08] sfp 'BaseEnclosure-NodeB-IoModule1-SFP0' status is 'Healthy' [instance: 9f5dabb7dbe04d7481f7ece093403d93] sfp 'BaseEnclosure-NodeA-IoModule1-SFP0' status is 'Healthy' [instance: af7980b528fc408dbe3c0e394fad9736] sfp 'BaseEnclosure-NodeA-4PortCard-SFP2' status is 'Empty' [instance: c51a39ea4d3c4cb295a74878c150eb60] sfp 'BaseEnclosure-NodeB-IoModule1-SFP1' status is 'Healthy' [instance: cca32afd9107494995c3ee6e91b82905] sfp 'BaseEnclosure-NodeB-4PortCard-SFP2' status is 'Empty' [instance: dcbd32046f0e40899beb0b5f7fce117b] sfp 'BaseEnclosure-NodeA-4PortCard-SFP1' status is 'Empty' [instance: e4f2d30005dd476da81c42bed95f73e2] sfp 'BaseEnclosure-NodeA-4PortCard-SFP3' status is 'Empty' [instance: e99b6ee1a934406cb73c4edb7fad0b47] sfp 'BaseEnclosure-NodeA-IoModule1-SFP1' status is 'Healthy' [instance: fa7871c3abcc45e5bd96d7acd649b857]

On 2021-09-30 09:42, qgarnier wrote:

Could you test with following branch ? https://github.com/centreon/centreon-plugins/archive/refs/heads/add-plugin-dell-powerstore.zip

$ perl centreon_plugins.pl --plugin=storage::dell::powerstore::restapi::plugin.pm --mode=alerts --hostname=xxxxx --api-username=xxxxx --api-password=xxxxx --verbose $ perl centreon_plugins.pl --plugin=storage::dell::powerstore::restapi::plugin.pm --mode=hardware --hostname=xxxxx --api-username=xxxxx --api-password=xxxxx --verbose

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/centreon/centreon-plugins/issues/3086#issuecomment-930949265 [2] https://github.com/notifications/unsubscribe-auth/AHLZQS7K5VJ73Z2DOLJ5YX3UEQIE7ANCNFSM5DUQZTYQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

garnier-quentin commented 3 years ago

It seems ok for me.

BertrandJO commented 3 years ago

For me too. Thanks

On 2021-09-30 12:12, qgarnier wrote:

It seems ok for me.

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/centreon/centreon-plugins/issues/3086#issuecomment-931185339 [2] https://github.com/notifications/unsubscribe-auth/AHLZQSZ3M5HUAVSJBZVJOETUEQZXZANCNFSM5DUQZTYQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

centreon / centreon-plugins