You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we have a few nodes that are marked in different rooms. The problem is that we only want the subscription to include nodes that we want, not all nodes (including the test ones) as part of the paid subscription of ND. There is no option or way to separate them, and the Netdata subscription automatically includes them in the plan and increases the cost without asking.
Description
It would be nice to have an option for the ND subscription to apply only to the nodes within a specific room/node, rather than counting and including all nodes
Importance
must have
Value proposition
Cost management
Proper subscription management for personal, client, and testing nodes under one account
Proposed implementation
Currently, the ND logic includes all nodes under an account in the subscription. It might be better to change this logic slightly: Based on the node ID, if included in the subscription, then trigger YES for the subscription features; if not, just react as a non-subscribed user.
The text was updated successfully, but these errors were encountered:
Problem
Currently, we have a few nodes that are marked in different rooms. The problem is that we only want the subscription to include nodes that we want, not all nodes (including the test ones) as part of the paid subscription of ND. There is no option or way to separate them, and the Netdata subscription automatically includes them in the plan and increases the cost without asking.
Description
It would be nice to have an option for the ND subscription to apply only to the nodes within a specific room/node, rather than counting and including all nodes
Importance
must have
Value proposition
Proposed implementation
Currently, the ND logic includes all nodes under an account in the subscription. It might be better to change this logic slightly: Based on the node ID, if included in the subscription, then trigger YES for the subscription features; if not, just react as a non-subscribed user.
The text was updated successfully, but these errors were encountered: