title | excerpt | updated |
---|---|---|
Dashboards - Capacités et limitations (EN) |
Discover the capabilities and limitations of Public Cloud Databases for Dashboards |
2025-02-19 |
This page provides the technical capabilities and limitations of the Public Cloud Databases for Dashboards offer.
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at https://github.com/orgs/ovh/projects/16/views/5.
The Public Cloud Databases offer is available in the following regions:
BHS
(Beauharnois, Canada)DE
(Frankfurt, Germany)GRA
(Gravelines, France)SBG
(Strasbourg, France)SGP
(Singapore, Singapore)UK
(London, United Kingdom)WAW
(Warsaw, Poland)
Dashboards nodes have to be in the same region. Multi-AZ is currently not supported.
The Public Cloud Databases offer supports the following Dashboards versions:
- Grafana® open source 10
Please refer to the DBMS lifecycle policy guide for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow the Grafana® Release Cycle on their official page: https://grafana.com/.
You can use your browser to access your Dashboards service.
The only plan available is Essential.
Here is an overview of the Essential plan capabilities:
Plan | Number of nodes by default | Additional nodes |
---|---|---|
Essential | 1 | No |
The Essential plan offers an automatic backup retention of 2 days. It supports public or private networks (vRack).
- Essential: the cluster is delivered with 1 node.
Grafana® open source software is under the GNU Affero General Public License, a liberal open-source license. More information on https://raw.githubusercontent.com/grafana/grafana/main/LICENSE.
For information on node types and pricing, please refer to the price page.
You can upgrade the node template of your cluster to scale your hardware resources up. This operation causes no interruption of service but be aware that you will not be able to downgrade the node template afterwards.
Dashboards clusters are reachable through a random port, attributed during cluster creation. Once your cluster is in RUNNING status, the Service URI will display the port to use.
Public as well as private networking (vRack) can be used for all the offers.
Ingress and Egress traffic are included in the service plans and unmetered.
The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
Here are some considerations to take into account when using private network:
- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
- OpenStack subnets routes announcement will not be applied to your services.
- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
You can further customise your Dashboards by using advanced parameters. See the Advanced parameters references documentation for more information on the supported parameters.
Your services are automatically backed up hourly with a one day retention.
See the Automated Backups guide for more information.
Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. For setup instructions, see the Public Cloud Databases - How to setup logs forwarding guide.
- Logs retention: 1000 lines of logs
- Metrics retention: 1 calendar month
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
Creation of users must be done through the Dashboards Web interface.
Only one user is created by default and its name is admin
. You must reset its password to connect for the first time to the Dashboards web interface.
We would love to help answer questions and appreciate any feedback you may have.
If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.
Are you on Discord? Connect to our channel at https://discord.gg/ovhcloud and interact directly with the team that builds our databases service!