Grafana® - Capabilities and Limitations

This page provides the technical capabilities and limitations of the Managed Databases (also called Cloud Databases) for Grafana® offer.¹

We continuously improve our offers. You can follow and submit ideas to add to our roadmap.

Capabilities and limitations

Supported regions

To view Cloud Databases availability, please see our regions and availability webpage.

Entire database instances have to be in the same region.

Grafana® versions

The Cloud Databases offer supports the following Grafana® versions:

• Grafana® 11.2

Please refer to our Cloud Databases - 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.

Grafana® clients

You can use your browser to access your Grafana® cluster.

Plans

The only plan available is Essential.

Here is an overview of the Essential plan capabilities:

The Essential plan offers an automatic backup retention of 2 days. It supports public or private networks (vRack).

Nodes and replicas

• Essential: the cluster is delivered with one node.

License type

Grafana® software is under the GNU Affero General Public License, a liberal open-source license. More information can be found at https://raw.githubusercontent.com/grafana/grafana/main/LICENSE.

Hardware resources

Here are the node types you can choose from:

Essential plans

Node template upgrade

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.

Features

Network

Grafana® 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.

Private network considerations

Here are some considerations to take into account when using a 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 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 cannot create private network services on a shared network.

Authorized IPs

Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorize incoming traffic. Until then, your service will be unreachable.

Advanced parameters

You can further customize your Grafana® by using advanced parameters. See our Grafana® - Advanced Parameters References guide for more information on the supported parameters.

Backups

Your services are automatically backed up hourly with a one-day retention.

See our Cloud Databases - Automated Backups guide for more information.

Logs and metrics

Logs and metrics are available through the Control Panel and the API. Additionally, cross-service integration can be configured to leverage your logs and metrics in other Cloud Database services. You could then view your Grafana® logs in OpenSearch. See our Cloud Databases - Cross Service Integration guide for more information.

• 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.

Users and roles

The creation of users must be done through the Grafana® 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 Grafana® web interface.

Go further

For more information and tutorials, please see our other Managed Databases & Analytics or Platform as a Service guides. You can also explore the guides for other OVHcloud products and services.

[1]: The Grafana Labs Marks are trademarks of Grafana Labs, and are used with Grafana Labs’ permission. We are not affiliated with, endorsed or sponsored by Grafana Labs or its affiliates.