-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #7 from infrasonar/Collector-updates
Collector updates
- Loading branch information
Showing
7 changed files
with
96 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
![NetApp-Probe](../../../images/probe_readynas.png){ width="150" align=right} | ||
|
||
# Netgear - ReadyNAS | ||
|
||
!!! danger "Preview" | ||
|
||
The ReadyNAS probe is a preview release.<br> | ||
Contact [InfraSonar support](../../introduction/support.md) if you want to get involved in testing our preview release. | ||
|
||
|
||
## Introduction | ||
|
||
InfraSonar monitors ReadyNAS storage systems using [snmp](index.md). | ||
|
||
## Features | ||
|
||
### TODO | ||
|
||
:material-check: System information<br> | ||
:material-check: Disk status<br> | ||
:material-check: RAID status<br> | ||
:material-check: Services<br> | ||
:material-check: IO | ||
|
||
## Deployment | ||
|
||
The ReadyNAS probe can easily be deployed using our [appliance manager](./../appliance/appliance_manager.md). | ||
|
||
## Credentials | ||
|
||
As the ReadyNAS probe uses SNMP the SNMP section in our [credentials documentation](../appliance/credentials.md) is applicable for this probe. | ||
The probe configuration uses the `readynas` section as default in the InfraSonar credentials file. | ||
|
||
## Additional information | ||
|
||
:material-github: [ReadyNAS probe source code](https://github.com/infrasonar/readynas-probe) | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
![Ping](../../images/service_mx.png){ width="150" align=right} | ||
|
||
# MX | ||
|
||
## Introduction | ||
|
||
The MX-service is a service which validates your email configuration. | ||
|
||
## Features | ||
|
||
We verify the following email DNS records: | ||
|
||
- **MX**: A mail exchanger record specifies the mail server responsible for accepting email messages on behalf of a domain name. It is a resource record in the Domain Name System. It is possible to configure several MX records, typically pointing to an array of mail servers for load balancing and redundancy. | ||
- **SPF**: Sender Policy Framework (SPF) is an email authentication method which ensures the sending mail server is authorized to originate mail from the email sender's domain. Additional information can be found [here](https://www.spf-record.com/) | ||
- **DMARC**: Domain-based Message Authentication, Reporting and Conformance (DMARC) is an email authentication protocol. It is designed to give email domain owners the ability to protect their domain from unauthorized use, commonly known as email spoofing. Additional information can be found [here](https://dmarc.org/) | ||
- **DKIM**: DomainKeys Identified Mail (DKIM) is an email authentication method designed to detect forged sender addresses in email (email spoofing), a technique often used in phishing and email spam. | ||
- **MTA_STS**: SMTP MTA Strict Transport Security (RFC 8461) aims to address the problem of active adversary by defining a protocol for mail servers to declare their ability to use secure channels in specific files on the server and specific DNS TXT records. [:material-wikipedia:](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) | ||
- **BIMI**: Brand Indicators for Message Identification or BIMI (pronounced: Bih-mee) is an emerging email specification that enables the use of brand-controlled logos within supporting email clients. BIMI leverages the work an organization has put into deploying DMARC protection, by bringing brand logos to the customer’s inbox. For the brand’s logo to be displayed, the email must pass DMARC authentication checks, ensuring that the organization’s domain has not been impersonated. | ||
You can find the implementation guide [here](https://bimigroup.org/implementation-guide/). | ||
|
||
## Probe configuration | ||
|
||
Property | Description | ||
---------|------------------------ | ||
Domain | The email domain the service should verify. | ||
Selector | The DKIM selector used by the organization. | ||
|
||
## Check specifics | ||
|
||
The DKIM check fails with a *check error* if you did not configure the selector. If you have not enabled DKIM yet you should disable this check to clear the check error. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
![TCP](../../images/probe_tcp.png){ width="150" align=right} | ||
|
||
# TCP | ||
|
||
## Introduction | ||
|
||
The TCP-service is the [service](./index.md) variant of our [tcp-probe](../probes/tcp.md). | ||
|
||
## Features | ||
|
||
- Check certificates | ||
|
||
## Service configuration | ||
|
||
| Property | Description | | ||
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | ||
| Address | The address that the probe should check. | | ||
| Certificate Ports | List of ports to perform certificates check on. | | ||
|
||
## Checks | ||
|
||
### Certificates | ||
|
||
Gathers certificates and ciphers present on the specified TCP port. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters