Manage Addon Services
This section will guide you to manage the addon services on your node.
The following addon services are being offered for your node,
Webhook
The Webhook addon service is an innovative feature on our platform that allows you to subscribe to specific entities within a subgraph. This functionality ensures you receive data in near real-time, directly to your system, whenever any data related to your subscribed entities is added or modified.
You will need a subscription for the Webhook addon to enable it on a node.
The Webhook addon will be associated with one node on which you enable the service.
You have the flexibility to create multiple webhooks across various entities within any subgraph hosted on the node.
Enabling the Webhook service
Enabling the Webhook service will consume one Webhook addon from your subscription.
There are two ways to enable the addon, the first is to enable it while deploying the node, and the other is to enable it after the node is deployed from the node dashboard page.
Method 1: While deploying node
Enable the checkbox against Webhooks on the Addon Services tab while you deploy your node.
Method 2: After the node is deployed
Step 1: Visit the dashboard for the node you wish to configure Webhooks for. Then, navigate to the Addon Services section and expand it. Now, click on the Enable button to initiate the service.
Step 2: On the modal asking confirmation to enable the service, click on the Yes button.
This will initiate the process to enable the service on the node. While the webhooks are being enabled, you will see that it is under process.
Once the service is enabled you will be notified via in-app notification and see this on the dashboard.
Disabling the Webhook service
Disabling the Webhook service will delete all the webhooks on all the subgraphs created within that particular node. This process is irreversible, so proceed with caution.
Disabling the Webhook service will free up a Webhook addon in your subscription.
Step 1: Visit the dashboard for the node you wish to disable Webhooks for. Then, navigate to the Addon Services section and expand it. Now, click on the Disable button to remove the service.
Step 2: On the modal asking for confirmation to disable the service, click on the Yes button.
This will initiate the process to disable the service on the node. While the webhooks are being disabled, you will see that it is under process.
Once the service is disabled you will be notified via in-app notification and see this on the dashboard.
Index Data Pruning
The Index Data Pruning addon service introduces a cutting-edge functionality to our platform, enabling users to retain only the latest data for their subgraph entities by setting desired history blocks. This streamlining significantly accelerates the performance of GraphQL queries, offering a more efficient and responsive experience.
You will need a subscription for the Index Data Pruning addon to enable it on a node.
It will be associated with one node on which you enable the service.
Enabling the Index Data Pruning service
Enabling the Index Data Pruning service will consume one Index Data Pruning addon from your subscription.
There are two ways to enable the addon, the first is to enable it while deploying the node, and the other is to enable it after the node is deployed from the node dashboard page.
Method 1: While deploying node
Enable the checkbox against Index Data Pruning on the Addon Services tab while you deploy your node.
Method 2: After the node is deployed
Step 1: Visit the dashboard for the node you wish to configure Index Data Pruning for. Then, navigate to the Addon Services section and expand it. Now, click on the Enable button to initiate the service.
Step 2: On the modal asking confirmation to enable the service, click on the Yes button.
This will enable the service on the node.
Disabling the Index Data Pruning service
Before you proceed to disable the Index Data Pruning service, it's crucial to verify that there are no subgraphs actively being pruned. If any subgraph is undergoing pruning, please deconfigure the pruning process within that subgraph first.
Disabling the Index Data Pruning service will free up a Index Data Pruning addon in your subscription.
Step 1: Visit the dashboard for the node you wish to disable Index Data Pruning for. Then, navigate to the Addon Services section and expand it. Now, click on the Disable button to remove the service.
Step 2: On the modal asking for confirmation to disable the service, click on the Yes button.
This will disable the service on the node.
Ledger Data Pruning
The Ledger Data Pruning addon service introduces a cutting-edge functionality to our platform, enabling users to retain only the latest chain data by setting desired history blocks.
You will need a subscription for the Ledger Data Pruning addon to enable it on a node.
It will be associated with one node on which you enable the service.
Enabling the Ledger Data Pruning service
Enabling the Ledger Data Pruning service will consume one Ledger Data Pruning addon from your subscription.
There are two ways to enable the addon, the first is to enable it while deploying the node, and the other is to enable it after the node is deployed from the node dashboard page.
Method 1: While deploying node
Enable the checkbox against Ledger Data Pruning on the Addon Services tab while you deploy your node.
Method 2: After the node is deployed
Step 1: Visit the dashboard for the node you wish to configure Ledger Data Pruning for. Then, navigate to the Addon Services section and expand it. Now, click on the Enable button to initiate the service.
Step 2: On the modal asking confirmation to enable the service, click on the Yes button.
This will enable the service on the node.
Disabling the Ledger Data Pruning service
Disabling the Ledger Data Pruning service will free up a Ledger Data Pruning addon in your subscription.
Step 1: Visit the dashboard for the node you wish to disable Ledger Data Pruning for. Then, navigate to the Addon Services section and expand it. Now, click on the Disable button to remove the service.
Step 2: On the modal asking for confirmation to disable the service, click on the Yes button.
This will disable the service on the node.
Last updated