Cloud services

1. In the Microsoft Entra admin center (entra.microsoft.com), open Entra ID → App registrations → New registration, name it DumbMonit, keep a single tenant and register it.

2. On the Overview page, copy the Application (client) ID and the Directory (tenant) ID.

3. Open API permissions → Add a permission → Microsoft Graph → Application permissions, add the permissions listed below, then click Grant admin consent.

4. Open Certificates & secrets → New client secret and copy its Value (not the Secret ID): it is shown once and it expires, so note the date.

5. In DumbMonit, enter graph.microsoft.com as address, paste the client ID and the secret value, and fill in the Tenant ID option.

Ojo. Admin consent gives the application tenant-wide read access to the data above. Use a dedicated app registration with only these permissions, and renew its client secret before it expires.

1. In the Microsoft Entra admin center (entra.microsoft.com), open Entra ID → App registrations → New registration, name it DumbMonit, keep a single tenant and register it.

2. On the Overview page, copy the Application (client) ID and the Directory (tenant) ID.

3. Open API permissions → Add a permission → Microsoft Graph → Application permissions, add the permissions listed below, then click Grant admin consent.

4. Open Certificates & secrets → New client secret and copy its Value (not the Secret ID): it is shown once and it expires, so note the date.

5. In DumbMonit, enter graph.microsoft.com as address, paste the client ID and the secret value, and fill in the Tenant ID option.

Ojo. Admin consent gives the application tenant-wide read access to the data above. Use a dedicated app registration with only these permissions, and renew its client secret before it expires: DumbMonit watches its own secret like any other.

1. In the Azure portal, open Microsoft Entra ID > App registrations > New registration, name it DumbMonit, keep single tenant, then Register.

2. On the Overview page, copy the Application (client) ID and the Directory (tenant) ID.

3. Open Certificates & secrets > New client secret, choose a lifetime, then copy the secret Value: it is shown once.

4. Open Subscriptions > your subscription > Access control (IAM) > Add > Add role assignment, pick the Reader role, select the DumbMonit application, then Review + assign.

5. Copy the Subscription ID from the subscription Overview page.

6. In DumbMonit, enter management.azure.com as address, paste the client ID and secret, and fill the Tenant ID and Subscription ID options.

Ojo. A stopped or deallocated virtual machine is reported by Azure as unavailable on the user's request: it is counted apart and raises no alert. Azure Monitor alerts need the Microsoft.AlertsManagement resource provider registered on the subscription; without it only Resource Health is monitored.

1. In the AWS console, open IAM, Policies, Create policy, JSON tab, paste this read-only policy and name it DumbMonitReadOnly.

   {"Version":"2012-10-17","Statement":[{"Effect":"Allow","Action":["cloudwatch:DescribeAlarms","cloudwatch:ListMetrics","cloudwatch:GetMetricData"],"Resource":"*"}]}

2. Open IAM, Users, Create user: name it dumbmonit, leave console access off, and attach the DumbMonitReadOnly policy.

3. Open the user, Security credentials, Create access key, choose Application running outside AWS. Copy the access key ID and the secret access key: the secret is shown once.

4. Optional, to use a role instead: attach the policy to a role that trusts the user, give the user only sts:AssumeRole on that role, and copy the role ARN into the Role ARN option.

5. In DumbMonit, enter monitoring.<region>.amazonaws.com as the address, paste the key and its secret, and set the same region in the Region option.

Ojo. Use a dedicated IAM user with only these read permissions, never a key that can change resources. AWS bills GetMetricData per metric requested (USD 0.01 per 1,000): a long check interval keeps the cost low on large accounts.

1. In the Cloudflare dashboard, open My Profile > API Tokens > Create Token > Create Custom Token, and name it DumbMonit.

2. Add the read-only permissions listed below, and nothing else. The first one is required; the others switch on one part each.

3. Under Account Resources and Zone Resources, choose the account and the zones to monitor (All zones is fine).

4. Click Continue to summary > Create Token, then copy the token: it is shown once.

5. In DumbMonit, use this address and paste the token as API token. Leave Account ID empty unless the token covers several accounts.

   api.cloudflare.com

Ojo. A part whose permission is missing (or that the plan does not include) is skipped and its readable metric is 0; it does not make the monitor fail. Only the zones the token can see are watched.

1. In the Hetzner Cloud Console, open the project to monitor, then Security > API tokens > Generate API token.

2. Name it DumbMonit and choose the Read permission (not Read & Write).

3. Click Generate API token, then copy the token: it is shown once.

4. In DumbMonit, use this address and paste the token as API token. One monitor reads one project.

   api.hetzner.cloud

Ojo. A server that is powered off is reported as not running, on purpose or not: mute the rule for it if that is expected. The API allows 3600 requests per hour and project, so server metrics are read for 10 servers by default.

1. Open the OVHcloud token page of your region and sign in with your OVHcloud account. The link pre-selects the two read rights.

   https://eu.api.ovh.com/createToken/?GET=/vps*&GET=/dedicated/server*

2. Name the script DumbMonit, set Validity to Unlimited, and keep only the two GET rights listed below, then click Create keys.

3. Copy the Application Key, the Application Secret and the Consumer Key: they are shown once.

4. In DumbMonit, enter eu.api.ovh.com as address (ca.api.ovh.com for OVHcloud Canada) and paste the Application Key as Application key.

5. In the second field, type the Application Secret, a colon, then the Consumer Key.

   application_secret:consumer_key

Ojo. The OVHcloud API publishes no calendar of planned maintenance: DumbMonit sees an intervention only once it has started, as a running task. A VPS you stopped yourself counts as down. A dedicated server is reported in error only if OVHcloud monitoring is enabled on it. Either right may be omitted to watch only the other family.

1. Open the Infomaniak Manager token page and sign in.

   https://manager.infomaniak.com/v3/ng/profile/user/token/list

2. Click Create a token and name it DumbMonit.

3. Choose the scopes listed below, and set the validity you want (no expiry avoids renewing it).

4. Click Create the token, then copy it: it is shown once.

5. In DumbMonit, enter api.infomaniak.com as address and paste the token. Fill the Account ID option if the token has no Accounts scope.

Ojo. The Infomaniak API gives no finer state than the expiry date, the lock and the maintenance flags of each product: it does not tell whether a site or a mailbox is up. Use an HTTP monitor for that.