Skip to Navigation
Cloud: Product Features
OLAP ETL
RavenDB Cloud provides OLAP ETL capabilities, allowing you to integrate your operational data with analytical data warehouses.
Usage of this feature is described here.
PowerBi
RavenDB Cloud supports direct integration with Power BI, a leading business analytics tool. This feature allows you to seamlessly connect your RavenDB data with Power BI for advanced visualization and reporting, enabling real-time insights and data-driven decision-making.
Usage of this feature is described here.
Configuration
Required
Power Bi IPs must be configured after enabling PowerBi feature.
Product Restart
Your product will be restarted automatically node by node to apply settings needed for feature to work properly.
To access Power Bi Configuration View click Configure Button in Power Bi feature row. Here you can edit your IP addresses that will have access to RavenDB Power Bi port.
Power Bi Configuration View
Power Bi IPs entries are CIDR ranges that define networks from which the connection is allowed.
Queue ETL
The Queue ETL feature enables you to export data from RavenDB to various queue systems, such as RabbitMQ or Kafka. This is particularly useful for scenarios where you need to process data asynchronously or distribute it to other microservices and applications.
Usage of this feature is described here.
Queue Sink
Queue Sink allows RavenDB Cloud to directly receive data from queues, making it easier to ingest data into your database from external systems or services. This feature is ideal for integrating with event-driven architectures where data is processed and ingested in real time.
Usage of this feature is described here.
Availability
This feature is available only for RavenDB 6.0 and newer.
Data Archival
RavenDB Cloud offers the ability to archive selected documents. Archived documents are compressed and can be handled differently by RavenDB functions (e.g. Indexing can exclude archived documents from indexes and Data Subscriptions can avoid sending archived docs to workers), helping to keep the database smaller and quicker and its contents more relevant.
Usage of this feature is described here.
Availability
This feature is available only for RavenDB 6.0 and newer.
Monitoring
RavenDB Cloud allows you to monitor your RavenDB Cloud instances via SNMP protocol. SNMP is a widely used network management protocol that allows for the collection and organization of information about managed devices on IP networks.
Configuration
Click Configure Button in Monitoring feature row in order to configure this feature. You will see Monitoring Configuration View. You can edit SNMP Monitoring IPs in the first section. The second section displays SNMPv3 Monitoring credentials.
Monitoring Configuration View
SNMP Monitoring IPs
Required
SNMP Monitoring IPs must be configured after enabling Monitoring feature.
Product Restart
Your product will be restarted automatically (node by node) to apply settings needed for feature to work properly.
This section allows you to specify IPs that will have access to your product using the SNMP protocol.
Edit SNMP Monitoring IPs
SNMPv3 Monitoring credentials
SNMPv3 is the most secure version of SNMP, providing enhanced security features over its predecessors. When setting up SNMPv3 monitoring for your RavenDB Cloud instances, you need to configure specific credentials that ensure secure communication between the SNMP agent on your end and the RavenDB.
Credentials required to connect to RavenDB Monitoring Endpoints are provided in this section. We also provide sample command you can use to test connection.
SNMP Monitoring IPs entries are CIDR ranges that define networks from which the connection is allowed.
Autoscaling
RavenDB Cloud allows you to autoscale your RavenDB Cloud instances based on the CPU usage.
Configuration
Click Configure Button in Autoscaling feature row in order to configure this feature. You will see Autoscaling Configuration View. It's separated into downscaling parameters and upscaling parameters.
| Parameter | Description |
|---|---|
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling. |
| Upscaling Grace Period | The time delay before upscaling begins after a high resource threshold is exceeded, allowing the system to avoid immediate scaling. |
| High Cpu Threshold | The average CPU usage percentage from last High CPU Threshold Duration that triggers the upscaling process. |
| High Cpu Threshold Duration | The duration for which the average CPU usage must exceed the threshold before triggering upscaling. |
| Upscaling Step | Determines by how many instances upscaling should take place in one go. For example with step set to 2 it will scale up from Dev10 to Dev30. |
| Lowest Type | The minimum virtual machine size (inclusive) available for downscaling. |
| Downscaling Grace Period | The time delay before downscaling begins after a low resource threshold is exceeded, allowing the system to avoid immediate scaling. |
| Low Cpu Threshold | The average CPU usage percentage from last Low CPU Threshold Duration that triggers the downscaling process. |
| Low Cpu Threshold Duration | The duration for which the average CPU usage must exceed the threshold before triggering downscaling. |
| Downscaling Step | Determines by how many instances downscaling should take place in one go. For example with step set to 2 it will scale down from Dev30 to Dev10. |
Autoscaling Configuration
You can edit Autoscaling parameters by clicking on Edit button.
Autoscaling Edit Configuration