FAQ and troubleshooting¶
Short answers to common questions, plus fixes for the issues people hit most often.
Frequently asked questions¶
Which clouds and regions are supported?¶
OpenWatch targets sovereign European clouds built on OpenStack. Today it supports Infomaniak Public Cloud, in regions dc3-a and dc4-a. Support for more providers is on the roadmap. See Connect your cloud.
Does OpenWatch ever change anything in my cloud?¶
Not unless you ask it to. OpenWatch reads your usage and rating data (compute, storage, network, images, load balancers, and the rating API) to build every dashboard, and it never changes anything on its own. Some optimisation features can act on your cloud, but only when you explicitly trigger and confirm them: deleting an orphan resource, or applying and reverting a rightsizing resize or volume retype. If you connect OpenWatch with read-only credentials, those optional actions simply fail and everything else keeps working.
CHF or EUR: how is the currency handled?¶
You choose CHF or EUR from the currency selector. Conversion is applied on top of the cached figures, so switching currency is instant and does not trigger a new fetch from your cloud.
Why does the dashboard sometimes say the data is refreshing?¶
The dashboard reads from a cache that is refreshed in the background, which is what keeps it fast. When you connect a new project, or just after a forced refresh, the cache may be empty or stale. In that case OpenWatch shows a refreshing state and loads the numbers as soon as the background job completes. The page refreshes itself shortly after.
How fresh is the data?¶
Costs and resources are refreshed on a schedule in the background (hourly by default, controlled by DATA_REFRESH_INTERVAL on self-hosted deployments). Cost alerts are evaluated every few minutes (ALERT_CHECK_INTERVAL, default 5 minutes). You can also force a refresh from the dashboard at any time.
Can I export the metrics?¶
Yes. See Prometheus metrics for a per-organisation, token-authenticated metrics endpoint you can scrape.
Where do I get help?¶
Check the relevant page in this documentation first. For the hosted service, contact support through openwatch.cloud. For self-hosted deployments, consult the project repository.
Troubleshooting¶
I cannot connect an OpenStack project¶
Use the Test connection button when adding the project and check, in order:
- Auth URL is correct (for Infomaniak,
https://api.pub1.infomaniak.cloud/identity/v3). - Region matches where your project actually runs (
dc3-aordc4-a). A region mismatch is a common cause of empty results. - User domain and project domain are set correctly (often
Default). - Username and password are valid OpenStack credentials, not your Infomaniak web login.
See Connect your cloud for the full field-by-field guide.
I connected a project but see no costs yet¶
The first fetch runs in the background. Give it a moment and reload; the dashboard shows a refreshing state until the cache is warm. If it stays empty, re-check the region and run Test connection again.
I lost access to my two-factor authentication device¶
Use one of the recovery codes you saved when enabling two-factor authentication. Each code works once. If you have run out, an organisation administrator or the site super-admin can help you recover access. See Securing your account.
I did not receive the verification or invitation email¶
Check your spam folder first. On self-hosted deployments, email requires SMTP to be configured (see Configuration); if it is not set up, verification and invitation emails will not be sent.
The Flower service will not start (self-hosted)¶
Flower requires FLOWER_PASSWORD to be set in your .env. Without it, the compose stack refuses to start the Flower service. See Configuration.