mirror of
https://github.com/netdata/netdata.git
synced 2025-04-06 14:35:32 +00:00
Update Netdata subscription plans documentation (#17571)
* update the plans doc to reflect plans available * update role base access model * view plan n billing updates * change wording * admin wording * update centralized cloud alerts reference doc * remove misleading plan indication * check links, and format files and tables * Update plans.md * Apply suggestions from code review * simplify language in edited docs, make them simpler to grasp * edits from product * Update alerts-configuration-manager.md * Apply suggestions from code review Co-authored-by: Hugo Valente <82235632+hugovalente-pm@users.noreply.github.com> --------- Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud> Co-authored-by: Shyam Sreevalsan <shyam@netdata.cloud> Co-authored-by: Hugo Valente <82235632+hugovalente-pm@users.noreply.github.com>
This commit is contained in:
Fotis Voutsas
GitHub
parent
3a1f3e3d7e
commit
ea98d9a9e7
9 changed files with 291 additions and 543 deletions
|
|
@ -1,71 +1,45 @@
|
|||
# Creating Alerts with Netdata Alerts Configuration Manager
|
||||
|
||||
The Netdata Alerts Configuration Manager enables users with [Business subscriptions](https://www.netdata.cloud/pricing/) to create alerts from the Netdata Dashboard with an intuitive user interface.
|
||||
The Netdata Alerts Configuration Manager enables subscribers to easily set up alerts directly from the Netdata Dashboard. More details on subscriptions can be found [here](https://www.netdata.cloud/pricing/).
|
||||
|
||||
## Using Alerts Configuration Manager
|
||||
|
||||
1. Go to the **Metrics** tab and navigate to the chart you want to configure an alert for.
|
||||
|
||||
2. Click the **Alert icon** on the top right corner of the chart.
|
||||
<!---->
|
||||
|
||||
3. The Alert Configuration Manager will open up with the default thresholds. You can modify the configuration as required and the alert definition on the right will be updated dynamically.
|
||||
<!---->
|
||||
|
||||
4. If you want more fine-grained control or access to more advanced settings, enable **Show advanced**
|
||||
<!---->
|
||||
|
||||
5. Copy the alert definition that is generated in the code box and add it to an existing [health configuration file](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#edit-health-configuration-files) or a new custom file under `<path to netdata install>/etc/netdata/health.d/` on a Parent Agent or a Standalone Child Agent.
|
||||
<!---->
|
||||
|
||||
6. Reload Netdata Alert Health checks `<path to netdata install>/usr/sbin/netdatacli reload-health` and the new alert is now configured.
|
||||
## Using the Alerts Configuration Manager
|
||||
|
||||
1. Navigate to the **Metrics** tab and select the chart you want to configure for alerts.
|
||||
2. Click the **Alert icon** in the top right corner of the chart.
|
||||
3. The Alert Configuration Manager will open, showing the default thresholds. Modify these thresholds as needed, the alert definition on the right will update automatically.
|
||||
4. For additional settings, toggle **Show advanced**.
|
||||
5. After configuring the alert, copy the generated alert definition from the code box. Paste this into an existing or new custom health configuration file located at `<path to netdata install>/etc/netdata/health.d/` on a Parent Agent or a Standalone Child Agent. The guide to edit health configuration files is available [here](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#edit-health-configuration-files).
|
||||
6. To activate the new alert, run the command `<path to netdata install>/usr/sbin/netdatacli reload-health`.
|
||||
|
||||
## Alerts Configuration Manager Sections
|
||||
|
||||
- **Alert Detection Method**
|
||||
<!---->
|
||||
An alert is triggered whenever a metric crosses a threshold:
|
||||
- Based on a standard `threshold`
|
||||
- Based on metric `variance`
|
||||
- Based on the `anomaly rate` of the metric
|
||||
|
||||
### Alert Detection Method
|
||||
|
||||
- **Metrics Lookup, Filtering and Formula Section**
|
||||
<!---->
|
||||
An alert is triggered whenever a metric crosses a threshold:
|
||||
|
||||
- **Metrics Lookup**: This is the **Evaluate** line of fields in the modal and it defines the parameters for the database lookup that is needed to get the value that will be compared against the alert definition. It corresponds to the [`lookup`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-lookup) line of the Alert configuration file. The Alerts Configuration Manager provides a default selection for the lookup and can be modified to suit your requirements. The parameters that can be modified are:
|
||||
- METHOD (`avg`, `sum`, `min`, `max`, `cv`, `stddev`)
|
||||
- COMPUTATION (sum of all dimensions or individually for each dimension)
|
||||
- DIMENSIONS (All dimensions, or a selection of dimensions)
|
||||
- DURATION (the period in time to run the lookup)
|
||||
- OPTIONS (`absolute`, `unaligned`, `percentage`, `min2max`)
|
||||
- **Standard Threshold**: Triggered when a metric crosses a predefined value.
|
||||
- **Metric Variance**: Triggered based on the variance of the metric.
|
||||
- **Anomaly Rate**: Triggered based on the anomaly rate of the metric.
|
||||
|
||||
- **Alert Filtering**: This functionality can be accessed through the **Show advanced** checkbox and it allows for filtering the alert health checks to be run only for specific components of the infrastructure. It helps in achieving a fine-grained configuration for any given alert.
|
||||
- `HOSTS` / `NODES` - By default all hosts are selected. You can pick nodes from the dropdown list, or enter a wildcard matching a list of hosts that you want the alert health check to run on. This field corresponds to the [`hosts`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-hosts) line of the Alert configuration file.
|
||||
- `INSTANCES` - All instances are selected by default. You can pick instances from the dropdown list, or enter a wildcard matching a list of instances that you want the alert health check to run on. This field corresponds to the [`charts`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-charts) line of the Alert configuration file.
|
||||
- `CHART LABELS` - All chart labels are selected by default. You can pick a chart label from the dropdown list or enter a wildcard matching a list of chart labels that you want the alert health check to run on. This field corresponds to the [`chart labels`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-chart-labels) line of the Alert configuration file.
|
||||
- `OS` - All Operating Systems are selected by default. You can choose which OS(s) an alert health check should run on. This field corresponds to the [`os`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-os) line of the Alert configuration file.
|
||||
### Metrics Lookup, Filtering and Formula Section
|
||||
|
||||
- **Formula / Calculation**: This field is available through the **Show advanced** checkbox and it is used to define a formula to be run on top of the `lookup` value. The result of the lookup is available in the `$this` variable, and after the formula is run, the result is also stored in `$this` and can be accessed while setting the alert thresholds. This field corresponds to the [`calc`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-calc) line of the Alert configuration file.
|
||||
You can read more about the different options in the [Alerts reference documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md)
|
||||
|
||||
- **Alerting conditions**
|
||||
<!---->
|
||||
- **Warning and Critical Thresholds**: These fields are used to set the thresholds for the `Warning` and `Critical` alert states, while also having the option to set the condition for the alert to be raised if it is `above` or `below` the given threshold. If the advanced settings are selected, a **formula** option can also be used, to define a custom formula instead of a threshold. These fields correspond to the [`warn` and `crit`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-lines-warn-and-crit) lines of the Alert configuration file.
|
||||
- **Recovery Thresholds**: This field is available through the **Show advanced** checkbox, and it is used to set the threshold that the metric value needs to meet to de-escalate from a given severity status, like `Critical to Warning` and from `Warning to Clear`. The logic is appended to the `warn` and `crit` lines of the Alert configuration file and resembles a one-line `IF-THEN-ELSE` clause.
|
||||
- **Check Interval**: This field is used to define the frequency of the health check for the alert and corresponds to the [`every`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-every) line of the Alert configuration file.
|
||||
- **Delay Notifications**: This field is available through the **Show advanced** checkbox and it is used to set delay parameters on notifications for an alert severity `escalation` or `de-escalation`. It corresponds to the [`delay`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-delay) line of the Alert configuration file.
|
||||
- **Metrics Lookup**: Adjust the database lookup parameters directly in the UI, including method (`avg`, `sum`, `min`, `max`, etc.), computation style, dimensions, duration, and options like `absolute` or `percentage`.
|
||||
- **Alert Filtering**: The **show advanced** checkbox allows filtering of alert health checks for specific infrastructure components. Options include selecting hosts, nodes, instances, chart labels, and operating systems.
|
||||
- **Formula / Calculation**: The **show advanced** checkbox allows defining a formula for the metric value, which is then used to set alert thresholds.
|
||||
|
||||
- **Agent Specific Options**: These options are only available on the `Netdata Agent` and not honored on `Netdata Cloud`. They can be accessed through the **Show advanced** checkbox.
|
||||
<!---->
|
||||
- **Repeat Notifications**: This field defines the repeat frequency for the alert notification when the alert is in either `warning` or `critical` status and corresponds to the [`repeat`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-repeat) line of the Alert configuration file.
|
||||
- **Send to**: This field is used to define a user role to which the alert notifications will be sent. If set to `silent`, then the alert won't be sent to any role. It corresponds to the [`to`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-to) line of the Alert configuration file.
|
||||
- **Custom Exec Script**: This field is used to define a custom script that will be executed when the alert is triggered (but needs to be carefully designed as it needs to call the `health_alarm_notify.sh` module) and corresponds to the [`exec`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-exec) line of the Alert configuration file.
|
||||
### Alerting Conditions
|
||||
|
||||
- **Alert Name, Description and Summary Section**
|
||||
<!---->
|
||||
- **Thresholds**: Set thresholds for warning and critical alert states, specifying whether the alert should trigger above or below these thresholds. Advanced settings allow for custom formulas.
|
||||
- **Recovery Thresholds**: Set thresholds for downgrading the alert from critical to warning or from warning to clear.
|
||||
- **Check Interval**: Define how frequently the health check should run.
|
||||
- **Delay Notifications**: Manage notification delays for alert escalations or de-escalations.
|
||||
- **Agent Specific Options**: Options exclusive to the Netdata Agent, like repeat notification frequencies and notification recipients.
|
||||
- **Custom Exec Script**: Define custom scripts to execute when an alert triggers.
|
||||
|
||||
- **Alert Template Name**: This field uniquely identifies an alert and corresponds to the [`template`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-alarm-or-template) field of the Alert configuration file.
|
||||
The Alerts Configuration Manager provides a default name for an Alert template but we recommend you modify this to have a meaningful name for your configured alert.
|
||||
- **Alert Template Description**: This field provides a brief explanation of the alert and corresponds to the [`info`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-info) line of the Alert configuration file.
|
||||
- **Alert Summary**: This field enables the users to create a custom title for the alert notification (via [Notification integrations](https://learn.netdata.cloud/docs/alerting/notifications/centralized-cloud-notifications)) and corresponds to the [`summary`](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-summary) line of the Alert configuration file.
|
||||
### Alert Name, Description and Summary Section
|
||||
|
||||
- **Alert Template Name**: Provide a unique name for the alert.
|
||||
- **Alert Template Description**: Offer a brief explanation of what the alert monitors.
|
||||
- **Alert Summary**: Create a custom title for alert notifications, which can be integrated with centralized notification systems available [here](https://learn.netdata.cloud/docs/alerting/notifications/centralized-cloud-notifications).
|
||||
|
|
|
|||
|
|
@ -1,130 +1,56 @@
|
|||
# Cloud alert notifications
|
||||
# Centralized Cloud Notifications Reference
|
||||
|
||||
import Callout from '@site/src/components/Callout'
|
||||
Netdata Cloud sends alert notifications for nodes in warning, critical, or unreachable states, ensuring alerts are managed centrally and efficiently.
|
||||
|
||||
Netdata Cloud can send centralized alert notifications to your team whenever a node enters a warning, critical, or
|
||||
unreachable state. By enabling notifications, you ensure no alert, on any node in your infrastructure, goes unnoticed by
|
||||
you or your team.
|
||||
## Benefits of Centralized Notifications
|
||||
|
||||
Having this information centralized helps you:
|
||||
* Have a clear view of the health across your infrastructure, seeing all alerts in one place.
|
||||
* Easily [set up your alert notification process](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md):
|
||||
methods to use and where to use them, filtering rules, etc.
|
||||
* Quickly troubleshoot using [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/metric-correlations.md)
|
||||
or [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/dashboard/anomaly-advisor-tab.md)
|
||||
- Consolidate health status views across all infrastructure in one place.
|
||||
- Set up and [manage your alert notifications easily](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md).
|
||||
- Expedite troubleshooting with tools like [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/metric-correlations.md) and the [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/dashboard/anomaly-advisor-tab.md).
|
||||
|
||||
If a node is getting disconnected often or has many alerts, we protect you and your team from alert fatigue by sending
|
||||
you a flood protection notification. Getting one of these notifications is a good signal of health or performance issues
|
||||
on that node.
|
||||
To avoid notification overload, **flood protection** is triggered when a node frequently disconnects or sends excessive alerts, highlighting potential issues.
|
||||
|
||||
Admins must enable alert notifications for their [Space(s)](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md#manage-space-notification-settings). All users in a
|
||||
Space can then personalize their notifications settings from within their [account
|
||||
menu](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/#manage-user-notification-settings).
|
||||
Admins must [enable alert notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md#manage-space-notification-settings) for their Space(s). All users can then customize their notification preferences through their [account menu](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/#manage-user-notification-settings).
|
||||
|
||||
<Callout type="notice">
|
||||
> **Note**
|
||||
>
|
||||
> Centralized alerts in Netdata Cloud are separate from the [Netdata Agent](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md) notifications. Alerts must be [configured individually](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md) on each node.
|
||||
|
||||
Centralized alert notifications from Netdata Cloud is a independent process from [notifications from
|
||||
Netdata](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md). You can enable one or the other, or both, based on your needs. However,
|
||||
the alerts you see in Netdata Cloud are based on those streamed from your Netdata-monitoring nodes. If you want to tweak
|
||||
or add new alert that you see in Netdata Cloud, and receive via centralized alert notifications, you must
|
||||
[configure](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md) each node's alert watchdog.
|
||||
## Alert Notifications
|
||||
|
||||
</Callout>
|
||||
Notifications can be sent via email or through third-party services like PagerDuty or Slack. Admins manage notification settings for the entire Space, while individual users can personalize settings in their profile.
|
||||
|
||||
## Alert notifications
|
||||
|
||||
Netdata Cloud can send centralized alert notifications to your team whenever a node enters a warning, critical, or unreachable state. By enabling notifications,
|
||||
you ensure no alert, on any node in your infrastructure, goes unnoticed by you or your team.
|
||||
|
||||
If a node is getting disconnected often or has many alerts, we protect you and your team from alert fatigue by sending you a flood protection notification.
|
||||
Getting one of these notifications is a good signal of health or performance issues on that node.
|
||||
|
||||
Alert notifications can be delivered through different methods, these can go from an Email sent from Netdata to the use of a 3rd party tool like PagerDuty.
|
||||
|
||||
Notification methods are classified on two main attributes:
|
||||
* Service level: Personal or System
|
||||
* Service classification: Community or Business
|
||||
|
||||
Only administrators are able to manage the space's alert notification settings.
|
||||
All users in a Space can personalize their notifications settings, for Personal service level notification methods, from within their profile menu.
|
||||
|
||||
> ⚠️ Netdata Cloud supports different notification methods and their availability will depend on the plan you are at.
|
||||
> For more details check [Service classification](#service-classification) or [netdata.cloud/pricing](https://www.netdata.cloud/pricing).
|
||||
|
||||
### Service level
|
||||
### Service Level
|
||||
|
||||
#### Personal
|
||||
|
||||
The notifications methods classified as **Personal** are what we consider generic, meaning that these can't have specific rules for them set by the administrators.
|
||||
|
||||
These notifications are sent to the destination of the channel which is a user-specific attribute, e.g. user's e-mail, and the users are the ones that will then be able to
|
||||
manage what specific configurations they want for the Space / Room(s) and the desired Notification level, they can achieve this from their User Profile page under
|
||||
**Notifications**.
|
||||
|
||||
One example of such a notification method is the E-mail.
|
||||
Notifications are sent to user-specific destinations, such as email, which are managed by users under their profile settings.
|
||||
|
||||
#### System
|
||||
|
||||
For **System** notification methods, the destination of the channel will be a target that usually isn't specific to a single user, e.g. slack channel.
|
||||
These notifications go to general targets like a Slack channel, with admins setting rules for notification targets based on workspace or alert level.
|
||||
|
||||
These notification methods allow for fine-grain rule settings to be done by administrators and more than one configuration can exist for them since. You can specify
|
||||
different targets depending on Rooms or Notification level settings.
|
||||
|
||||
Some examples of such notification methods are: Webhook, PagerDuty, Slack.
|
||||
|
||||
### Service classification
|
||||
### Service Classification
|
||||
|
||||
#### Community
|
||||
|
||||
Notification methods classified as Community can be used by everyone independent on the plan your space is at.
|
||||
These are: Email and discord
|
||||
|
||||
#### Pro
|
||||
|
||||
Notification methods classified as Pro are only available for **Pro** and **Business** plans
|
||||
These are: webhook
|
||||
Available to all plans, includes basic methods like Email and Discord.
|
||||
|
||||
#### Business
|
||||
|
||||
Notification methods classified as Business are only available for **Business** plans
|
||||
These are: PagerDuty, Slack, Opsgenie
|
||||
Exclusive to [paid plans](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md), includes advanced services like PagerDuty and Slack.
|
||||
|
||||
## Silencing Alert notifications
|
||||
## Alert Notification Silencing Rules
|
||||
|
||||
Netdata Cloud provides you a Silencing Rule engine which allows you to mute alert notifications. This muting action is specific to alert state transition notifications, it doesn't include node unreachable state transitions.
|
||||
Netdata Cloud offers a silencing rule engine to mute alert notifications based on specific conditions related to nodes or alert types. Learn how to manage these settings [here](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md).
|
||||
|
||||
The Silencing Rule engine is flexible and allows you to enter silence rules for the two main entities involved on alert notifications and can be set using different attributes. The main entities you can enter are **Nodes** and **Alerts** which can be used in combination or isolation to target specific needs - see some examples [here](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md#silencing-rules-examples).
|
||||
## Flood Protection
|
||||
|
||||
### Scope definition for Nodes
|
||||
* **Space:** silencing the space, selecting `All Rooms`, silences all alert state transitions from any node claimed to the space.
|
||||
* **War Room:** silencing a specific room will silence all alert state transitions from any node in that room. Please note if the node belongs to
|
||||
another room which isn't silenced it can trigger alert notifications to the users with membership to that other room.
|
||||
* **Node:** silencing a specific node can be done for the entire space, selecting `All Rooms`, or for specific war room(s). The main difference is
|
||||
if the node should be silenced for the entire space or just for specific rooms (when specific rooms are selected only users with membership to that room won't receive notifications).
|
||||
If a node repeatedly changes state or fires alerts, flood protection limits notifications to prevent overload. You can still access node details through Netdata Cloud or directly via the local Agent dashboard.
|
||||
|
||||
### Scope definition for Alerts
|
||||
* **Alert name:** silencing a specific alert name silences all alert state transitions for that specific alert.
|
||||
* **Alert context:** silencing a specific alert context will silence all alert state transitions for alerts targeting that chart context, for more details check [alert configuration docs](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-on).
|
||||
* **Alert role:** silencing a specific alert role will silence all the alert state transitions for alerts that are configured to be specific role recipients, for more details check [alert configuration docs](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-to).
|
||||
## Anatomy of an Email Alert Notification
|
||||
|
||||
Beside the above two main entities there are another two important settings that you can define on a silencing rule:
|
||||
* Who does the rule affect? **All user** in the space or **Myself**
|
||||
* When does is to apply? **Immediately** or on a **Schedule** (when setting immediately you can set duration)
|
||||
|
||||
For further help on setting alert notification silencing rules go to [Manage Alert Notification Silencing Rules](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md).
|
||||
|
||||
> ⚠️ This feature is only available for [Netdata paid plans](https://github.com/netdata/netdata/edit/master/docs/cloud/manage/plans.md).
|
||||
|
||||
## Flood protection
|
||||
|
||||
If a node has too many state changes like firing too many alerts or going from reachable to unreachable, Netdata Cloud
|
||||
enables flood protection. As long as a node is in flood protection mode, Netdata Cloud does not send notifications about
|
||||
this node. Even with flood protection active, it is possible to access the node directly, either via Netdata Cloud or
|
||||
the local Agent dashboard at `http://NODE:19999`.
|
||||
|
||||
## Anatomy of an alert notification
|
||||
|
||||
Email alert notifications show the following information:
|
||||
Email notifications provide comprehensive details:
|
||||
|
||||
- The Space's name
|
||||
- The node's name
|
||||
|
|
@ -138,10 +64,4 @@ Email alert notifications show the following information:
|
|||
- Threshold for triggering the given alert state
|
||||
- Calculation or database lookups that Netdata uses to compute the value
|
||||
- Source of the alert, including which file you can edit to configure this alert on an individual node
|
||||
|
||||
Email notifications also feature a **Go to Node** button, which takes you directly to the offending chart for that node
|
||||
within Cloud's embedded dashboards.
|
||||
|
||||
Here's an example email notification for the `ram_available` chart, which is in a critical state:
|
||||
|
||||
|
||||
- Direct link to the node’s chart in Cloud dashboards.
|
||||
|
|
|
|||
|
|
@ -10,55 +10,54 @@ At a high-level view, these are the domains from which the Events feed will prov
|
|||
>
|
||||
> Based on your space's plan, different allowances are defined to query past data.
|
||||
|
||||
| **Domains of events** | **Community** | **Business** |
|
||||
| :-- | :-- | :-- |
|
||||
| **[Auditing events](#auditing-events)** - <br/>Events related to actions done on your Space, e.g. invite user, change user role or change plan.| 4 hours | 90 days |
|
||||
| **[Topology events](#topology-events)**<br/>Node state transition events, e.g. live or offline.| 4 hours | 14 days |
|
||||
| **[Alert events](#alert-events)**<br/>Alert state transition events, can be seen as an alert history log.| 4 hours | 90 days |
|
||||
| **Domains of events** | **Community** | **Homelab** | **Business** | **Enterprise On-Premise** |
|
||||
|:------------------------------------------------------------------------------------------------------------------------------------------------|:--------------|:------------|:-------------|:--------------------------|
|
||||
| **[Auditing events](#auditing-events)** <p>Events related to actions done on your Space, e.g. invite user, change user role or change plan.</p> | 4 hours | 90 days | 90 days | User dependent |
|
||||
| **[Topology events](#topology-events)** <p>Node state transition events, e.g. live or offline.</p> | 4 hours | 14 days | 14 days | User dependent |
|
||||
| **[Alert events](#alert-events)** <p>Alert state transition events, can be seen as an alert history log.</p> | 4 hours | 90 days | 90 days | User dependent |
|
||||
|
||||
### Auditing events
|
||||
|
||||
| **Event name** | **Description** | **Example** |
|
||||
| :-- | :-- | :-- |
|
||||
| Space Created | The space was created.| Space `Acme Space` was **created** |
|
||||
| Room Created | A room was created on the Space.| Room `DB Servers` was **created** by `John Doe` |
|
||||
| Room Deleted | A room was deleted from the Space. | Room `DB servers` was **deleted** by `John Doe` |
|
||||
| User Invited to Space | A user was invited to join the Space.| User `John Smith` was **invited** to this space by `Alan Doe` |
|
||||
| User Uninvited from Space | An invitation for a user to join the space was revoked.| User `John Smith` was **uninvited** from this space |
|
||||
| User Added to Space | A user was added to the Space from an invitation (user accepted the invitation).| User `John Smith` was **added** to this space by invite of `Alan Doe` |
|
||||
| User Removed from Space | A user was added to the Space from an invitation. | User `John Smith` was **removed** from this space by `Alan Doe` |
|
||||
| User Added to Room | A user was added to a room on the Space. | User `John Smith` was **added** to room `DB servers` |
|
||||
| User Removed from Room | A user was removed from a room on the Space. | User `John Smith` was **removed** from room `DB Servers` by `Alan Doe` |
|
||||
| User Space Properties Changed | The properties of a user on the Space have changed, e.g. change user role | User role for `John Smith` was **changed** to `troubleshooter` by `Alan Doe` |
|
||||
| Node Added To Room | The node was added to a room on the Space. | Node `ip-xyz.ec2.internal` was **added** to room `DB Servers` by `John Doe` |
|
||||
| Node Removed To Room | The node was removed from a room on the Space. | Node `ip-xyz.ec2.internal` was **removed** from room `DB Servers` by `John Doe` |
|
||||
| Silencing Rule Created | A new alert notification silencing rule was created on the Space. | Silencing rule `DB Servers schedule silencing` on rooms `All nodes` and `DB Servers` was **created** by `John Smith` |
|
||||
| Silencing Rule Changed | An existing alert notification silencing rule was modified on the Space. | Silencing rule `DB Servers schedule silencing` on rooms `All nodes` and `DB Servers` was **changed** by `John Doe` |
|
||||
| Silencing Rule Deleted | An existing alert notifications silencing rule was removed from the Space. | Silencing rule `DB Servers schedule silencing` on rooms `All nodes` and `DB Servers` was **changed** by `Alan Smith` |
|
||||
| Space Claiming Token Created | A Space Claiming Token was created. | Claiming Token was created by user `John Doe` |
|
||||
| Space Claiming Token Revoked | A Space Claiming Token was revoked. | Claiming Token `_OtF2ssjrv` was revoked by user `John Doe` |
|
||||
| **Event name** | **Description** | **Example** |
|
||||
|:------------------------------|:---------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------|
|
||||
| Space Created | The space was created. | Space `Acme Space` was **created** |
|
||||
| Room Created | A room was created on the Space. | Room `DB Servers` was **created** by `John Doe` |
|
||||
| Room Deleted | A room was deleted from the Space. | Room `DB servers` was **deleted** by `John Doe` |
|
||||
| User Invited to Space | A user was invited to join the Space. | User `John Smith` was **invited** to this space by `Alan Doe` |
|
||||
| User Uninvited from Space | An invitation for a user to join the space was revoked. | User `John Smith` was **uninvited** from this space |
|
||||
| User Added to Space | A user was added to the Space from an invitation (user accepted the invitation). | User `John Smith` was **added** to this space by invite of `Alan Doe` |
|
||||
| User Removed from Space | A user was added to the Space from an invitation. | User `John Smith` was **removed** from this space by `Alan Doe` |
|
||||
| User Added to Room | A user was added to a room on the Space. | User `John Smith` was **added** to room `DB servers` |
|
||||
| User Removed from Room | A user was removed from a room on the Space. | User `John Smith` was **removed** from room `DB Servers` by `Alan Doe` |
|
||||
| User Space Properties Changed | The properties of a user on the Space have changed, e.g. change user role | User role for `John Smith` was **changed** to `troubleshooter` by `Alan Doe` |
|
||||
| Node Added To Room | The node was added to a room on the Space. | Node `ip-xyz.ec2.internal` was **added** to room `DB Servers` by `John Doe` |
|
||||
| Node Removed To Room | The node was removed from a room on the Space. | Node `ip-xyz.ec2.internal` was **removed** from room `DB Servers` by `John Doe` |
|
||||
| Silencing Rule Created | A new alert notification silencing rule was created on the Space. | Silencing rule `DB Servers schedule silencing` on rooms `All nodes` and `DB Servers` was **created** by `John Smith` |
|
||||
| Silencing Rule Changed | An existing alert notification silencing rule was modified on the Space. | Silencing rule `DB Servers schedule silencing` on rooms `All nodes` and `DB Servers` was **changed** by `John Doe` |
|
||||
| Silencing Rule Deleted | An existing alert notifications silencing rule was removed from the Space. | Silencing rule `DB Servers schedule silencing` on rooms `All nodes` and `DB Servers` was **changed** by `Alan Smith` |
|
||||
| Space Claiming Token Created | A Space Claiming Token was created. | Claiming Token was created by user `John Doe` |
|
||||
| Space Claiming Token Revoked | A Space Claiming Token was revoked. | Claiming Token `_OtF2ssjrv` was revoked by user `John Doe` |
|
||||
|
||||
### Topology events
|
||||
|
||||
| **Event name** | **Description** | **Example** |
|
||||
| :-- | :-- | :-- |
|
||||
| Node Became Live | The node is collecting and streaming metrics to Cloud.| Node `netdata-k8s-state-xyz` was **live** |
|
||||
| Node Became Stale | The node is offline and not streaming metrics to Cloud. It can show historical data from a parent node. | Node `ip-xyz.ec2.internal` was **stale** |
|
||||
| Node Became Offline | The node is offline, not streaming metrics to Cloud and not available in any parent node.| Node `ip-xyz.ec2.internal` was **offline** |
|
||||
| Node Created | The node is created but it is still `Unseen` on Cloud, didn't establish a successful connection yet.| Node `ip-xyz.ec2.internal` was **created** |
|
||||
| Node Removed |The node was removed from the Space, for example by using the `Delete` action on the node. This is a soft delete in that the node gets marked as deleted, but retains the association with this space. If it becomes live again, it will be restored (see `Node Restored` below) and reappear in this space as before. | Node `ip-xyz.ec2.internal` was **deleted (soft)** |
|
||||
| Node Restored | The node was restored. See `Node Removed` above. | Node `ip-xyz.ec2.internal` was **restored** |
|
||||
| Node Deleted | The node was deleted from the Space. This is a hard delete and no information on the node is retained. | Node `ip-xyz.ec2.internal` was **deleted (hard)** |
|
||||
| Agent Connected | The agent connected to the Cloud MQTT server (Agent-Cloud Link established).<br/>These events can only be seen on _All nodes_ War Room. | Agent with claim ID `7d87bqs9-cv42-4823-8sd4-3614548850c7` has connected to Cloud. |
|
||||
| Agent Disconnected | The agent disconnected from the Cloud MQTT server (Agent-Cloud Link severed).<br/>These events can only be seen on _All nodes_ War Room. | Agent with claim ID `7d87bqs9-cv42-4823-8sd4-3614548850c7` has disconnected from Cloud: **Connection Timeout**. |
|
||||
| Space Statistics | Daily snapshot of space node statistics.<br/>These events can only be seen on _All nodes_ War Room. | Space statistics. Nodes: **22 live**, **21 stale**, **18 removed**, **61 total**. |
|
||||
|
||||
| **Event name** | **Description** | **Example** |
|
||||
|:--------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------------------------------|
|
||||
| Node Became Live | The node is collecting and streaming metrics to Cloud. | Node `netdata-k8s-state-xyz` was **live** |
|
||||
| Node Became Stale | The node is offline and not streaming metrics to Cloud. It can show historical data from a parent node. | Node `ip-xyz.ec2.internal` was **stale** |
|
||||
| Node Became Offline | The node is offline, not streaming metrics to Cloud and not available in any parent node. | Node `ip-xyz.ec2.internal` was **offline** |
|
||||
| Node Created | The node is created but it is still `Unseen` on Cloud, didn't establish a successful connection yet. | Node `ip-xyz.ec2.internal` was **created** |
|
||||
| Node Removed | The node was removed from the Space, for example by using the `Delete` action on the node. This is a soft delete in that the node gets marked as deleted, but retains the association with this space. If it becomes live again, it will be restored (see `Node Restored` below) and reappear in this space as before. | Node `ip-xyz.ec2.internal` was **deleted (soft)** |
|
||||
| Node Restored | The node was restored. See `Node Removed` above. | Node `ip-xyz.ec2.internal` was **restored** |
|
||||
| Node Deleted | The node was deleted from the Space. This is a hard delete and no information on the node is retained. | Node `ip-xyz.ec2.internal` was **deleted (hard)** |
|
||||
| Agent Connected | The agent connected to the Cloud MQTT server (Agent-Cloud Link established).<br/>These events can only be seen on _All nodes_ War Room. | Agent with claim ID `7d87bqs9-cv42-4823-8sd4-3614548850c7` has connected to Cloud. |
|
||||
| Agent Disconnected | The agent disconnected from the Cloud MQTT server (Agent-Cloud Link severed).<br/>These events can only be seen on _All nodes_ War Room. | Agent with claim ID `7d87bqs9-cv42-4823-8sd4-3614548850c7` has disconnected from Cloud: **Connection Timeout**. |
|
||||
| Space Statistics | Daily snapshot of space node statistics.<br/>These events can only be seen on _All nodes_ War Room. | Space statistics. Nodes: **22 live**, **21 stale**, **18 removed**, **61 total**. |
|
||||
|
||||
### Alert events
|
||||
|
||||
| **Event name** | **Description** | **Example** |
|
||||
| :-- | :-- | :-- |
|
||||
| Node Alert State Changed | These are node alert state transition events and can be seen as an alert history log. You will be able to see transitions to or from any of these states: Cleared, Warning, Critical, Removed, Error or Unknown | Transition to Cleared:<br/>`httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` recovered with value **8.33%**<br/><br/>Transition from Cleared to Warning or Critical:<br/>`httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` was raised to **WARNING** with value **10%**<br/><br/>Transition from Warning to Critical:<br/>`httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` escalated to **CRITICAL** with value **25%**<br/><br/>Transition from Critical to Warning:<br/>`httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` was demoted to **WARNING** with value **10%**<br/><br/>Transition to Removed:<br/>Alert `httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` is no longer available, state can't be assessed.<br/><br/>Transition to Error:<br/>For this alert `httpcheck_web_service_bad_status` related to `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` we couldn't calculate the current value ⓘ|
|
||||
| **Event name** | **Description** | **Example** |
|
||||
|:-------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Node Alert State Changed | These are node alert state transition events and can be seen as an alert history log. You will be able to see transitions to or from any of these states: Cleared, Warning, Critical, Removed, Error or Unknown | Transition to Cleared:<br/>`httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` recovered with value **8.33%**<br/><br/>Transition from Cleared to Warning or Critical:<br/>`httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` was raised to **WARNING** with value **10%**<br/><br/>Transition from Warning to Critical:<br/>`httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` escalated to **CRITICAL** with value **25%**<br/><br/>Transition from Critical to Warning:<br/>`httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` was demoted to **WARNING** with value **10%**<br/><br/>Transition to Removed:<br/>Alert `httpcheck_web_service_bad_status` for `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` is no longer available, state can't be assessed.<br/><br/>Transition to Error:<br/>For this alert `httpcheck_web_service_bad_status` related to `httpcheck_netdata_cloud.request_status` on `netdata-parent-xyz` we couldn't calculate the current value ⓘ |
|
||||
|
||||
## Who can access the events?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,123 +1,42 @@
|
|||
# Netdata Plans
|
||||
# Netdata Subscription Plans
|
||||
|
||||
This page will guide you through the differences between the Community, Pro, Business and Enterprise plans.
|
||||
This page explains the Netdata subscription plan structure.
|
||||
|
||||
At Netdata, we believe in providing free and unrestricted access to high-quality monitoring solutions, and our commitment to this principle will not change. We offer our free SaaS offering - what we call **Community plan** - and Open Source Agent, which features unlimited nodes and users, unlimited metrics, and retention, providing real-time, high-fidelity, out-of-the-box infrastructure monitoring for packaged applications, containers, and operating systems.
|
||||
## Overview
|
||||
|
||||
We also provide paid subscriptions that designed to provide additional features and capabilities for businesses that need tighter and customizable integration of the free monitoring solution to their processes. These are divided into three different plans: **Pro**, **Business**, and **Enterprise**. Each plan will offers a different set of features and capabilities to meet the needs of businesses of different sizes and with different monitoring requirements.
|
||||
Netdata offers a **Community plan**, a free SaaS and Open Source Agent, while also it offers paid subscriptions — **Homelab**, **Business**, and **Enterprise On-Premise** — providing key business features and unlimited access to your dashboards.
|
||||
|
||||
> ### Note
|
||||
> To not disrupt the existing space user's access rights we will keep them in the **Early Bird** plan. The reason for this is to allow users to
|
||||
> keep using the legacy **Member** role with the exact same permissions as it has currently.
|
||||
>
|
||||
> If you move from the **Early Bird** plan to a paid plan, you will not be able to return to the **Early Bird** plan again. The **Community** free plan will always be available to you, but it does not allow
|
||||
> you to invite or change users using the Member role. See more details on our [roles and plans](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md#what-roles-are-available) documentation.
|
||||
For more info visit the [Netdata Cloud Pricing](https://netdata.cloud/pricing) page.
|
||||
|
||||
### Plans
|
||||
|
||||
The plan is an attribute that is directly attached to your space(s) and that dictates what capabilities and customizations you have on your space. If you have different spaces you can have different Netdata plans on them. This gives you flexibility to chose what is more adequate for your needs on each of your spaces.
|
||||
Each plan is linked to a Space, defining the capabilities and customizations available. Different Spaces can have different plans, offering flexibility based on your needs.
|
||||
|
||||
Netdata Cloud plans, with the exception of Community, work as subscriptions and overall consist of two pricing components:
|
||||
Netdata Cloud plans (excluding Community) involve:
|
||||
|
||||
* A flat fee component, that is applied on yearly subscriptions for the [comitted-nodes](#committed-nodes) charte (space subscription fee has been waived off)
|
||||
* An on-demand metered component, that is related to your usage of Netdata which directly links to the [number of nodes you have running](#running-nodes-and-billing)
|
||||
- A yearly flat fee for [committed nodes](#committed-nodes)
|
||||
- An on-demand metered component based on the [number of running nodes](#running-nodes-and-billing)
|
||||
|
||||
Netdata provides two billing frequency options:
|
||||
Billing options include monthly (pay-as-you-go) and yearly (annual prepayment). For more details, visit [Netdata Cloud Pricing](https://netdata.cloud/pricing).
|
||||
|
||||
* Monthly - Pay as you go, where we charge both the flat fee and the on-demand component every month
|
||||
* Yearly - Annual prepayment, where we charge upfront the flat fee and committed amount related to your estimated usage of Netdata (more details [here](#committed-nodes))
|
||||
## Running Nodes and Billing
|
||||
|
||||
For more details on the plans and subscription conditions please check <https://netdata.cloud/pricing>.
|
||||
Billing is based on the number of active nodes. We do not charge for offline or stale nodes. We calculate daily and running P90 figures to ensure fair billing by smoothing out sporadic spikes in node activity.
|
||||
|
||||
#### Running nodes and billing
|
||||
## Committed Nodes
|
||||
|
||||
The only dynamic variable we consider for billing is the number of concurrently running nodes or agents. We only charge you for your active running nodes, so we don't count:
|
||||
Yearly plans require specifying a number of committed nodes, which receive a discounted rate. Usage above these committed nodes incurs charges at the standard rate.
|
||||
|
||||
* offline nodes
|
||||
* stale nodes, nodes that are available to query through a Netdata parent agent but are not actively connecting metrics at the moment
|
||||
## Plan Changes and Credit Balance
|
||||
|
||||
To ensure we don't overcharge you due to sporadic spikes throughout a month or even at a certain point in a day we are:
|
||||
You can change your plan, billing frequency, or committed nodes at any time. For guidance, see [updating your plan](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/view-plan-billing.md#update-a-subscription-plan).
|
||||
|
||||
* Calculate a daily P90 figure for your running nodes. To achieve that, we take a daily snapshot of your running nodes, and using the node state change events (live, offline) we guarantee that a daily P90 figure is calculated to remove any daily spikes
|
||||
* On top of the above, we do a running P90 calculation from the start to the end of your billing cycle. Even if you have an yearly billing frequency we keep a monthly subscription linked to that to identify any potential overage over your [committed nodes](#committed-nodes).
|
||||
> **Note**
|
||||
>
|
||||
> - Changes like downgrades or cancellations keep notification configurations active for 24 hours. After that, any methods not supported by the new plan are disabled.
|
||||
> - Changes may restrict user access in your Space. Review role availability under [each plan](#areas-that-change-upon-subscription).
|
||||
> - Any credits are valid until the end of the following year.
|
||||
|
||||
#### Committed nodes
|
||||
## Areas That Change Upon Subscription
|
||||
|
||||
When you subscribe to an Yearly plan you will need to specify the number of nodes that you will commit to. On these nodes, a discounted price of less 25% than the original cost per node of the plan is applied. This amount will be part of your annual prepayment.
|
||||
|
||||
```
|
||||
Node plan discounted price x committed nodes x 12 months
|
||||
```
|
||||
|
||||
If, for a given month, your usage is over these committed nodes we will charge the original cost per node for the nodes above the committed number.
|
||||
|
||||
#### Plan changes and credit balance
|
||||
|
||||
It is ok to change your mind. We allow to change your plan, billing frequency or adjust the committed nodes, on yearly plans, at any time.
|
||||
|
||||
To achieve this you can check the [Update plan](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/view-plan-billing.md#update-plan) section.
|
||||
|
||||
> ⚠️ On a downgrade (going to a new plan with less benefits) or cancellation of an active subscription, please note that you will have all your notification methods configurations active **for a period of 24 hours**.
|
||||
> After that, any notification methods unavailable in your new plan at that time will be automatically disabled. You can always re-enable them once you move to a paid plan that includes them.
|
||||
|
||||
> ⚠️ Downgrade or cancellation may affect users in your Space. Please check what roles are available on the [each plans](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#areas-impacted-by-plans). Users with unavailable roles on the new plan will immediately have restricted access to the Space.
|
||||
|
||||
> ⚠️ Any credit given to you will be available to use on future paid subscriptions with us. It will be available until the **end of the following year**.
|
||||
|
||||
### Areas impacted by plans
|
||||
|
||||
##### Role-Based Access model
|
||||
|
||||
Depending on the plan associated to your space you will have different roles available:
|
||||
|
||||
| **Role** | **Community** | **Pro** | **Business** | **Early Bird** |
|
||||
| :-- | :--: | :--: | :--: | :--: |
|
||||
| **Administrators**<p>Users with this role can control Spaces, War Rooms, Nodes, Users and Billing.</p><p>They can also access any War Room in the Space.</p> | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| **Managers**<p>Users with this role can manage War Rooms and Users.</p><p>They can access any War Room in the Space.</p> | - | - | :heavy_check_mark: | - |
|
||||
| **Troubleshooters**<p>Users with this role can use Netdata to troubleshoot, not manage entities.</p><p>They can access any War Room in the Space.</p> | - | :heavy_check_mark: | :heavy_check_mark: | - |
|
||||
| **Observers**<p>Users with this role can only view data in specific War Rooms.</p>💡 Ideal for restricting your customer's access to their own dedicated rooms.<p></p> | - | - | :heavy_check_mark: | - |
|
||||
| **Billing**<p>Users with this role can handle billing options and invoices.</p> | - | - | :heavy_check_mark: | - |
|
||||
| **Member** ⚠️ Legacy role<p>Users with this role can create War Rooms and invite other Members.</p><p>They can only see the War Rooms they belong to and all Nodes in the All Nodes room.</p>| - | - | - | :heavy_check_mark: |
|
||||
|
||||
For more details check the documentation under [Role-Based Access model](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md).
|
||||
|
||||
##### Events feed
|
||||
|
||||
The plan you have subscribed on your space will determine the amount of historical data you will be able to query:
|
||||
|
||||
| **Type of events** | **Community** | **Pro** | **Business** |
|
||||
| :-- | :-- | :-- | :-- |
|
||||
| **Auditing events** - COMING SOON<p>Events related to actions done on your Space, e.g. invite user, change user role or create room.</p>| 4 hours | 7 days | 90 days |
|
||||
| **Topology events**<p>Node state transition events, e.g. live or offline.</p>| 4 hours | 7 days | 14 days |
|
||||
| **Alert events**<p>Alert state transition events, can be seen as an alert history log.</p>| 4 hours | 7 days | 90 days |
|
||||
|
||||
For more details check the documentation under [Events feed](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/events-feed.md).
|
||||
|
||||
##### Notification integrations
|
||||
|
||||
The plan on your space will determine what type of notifications methods will be available to you:
|
||||
|
||||
* **Community** - Email and Discord
|
||||
* **Pro** - Email, Discord and webhook
|
||||
* **Business** - Unlimited, this includes Slack, PagerDuty, Opsgenie etc.
|
||||
|
||||
For more details check the documentation under [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#alert-notifications).
|
||||
|
||||
##### Alert notification silencing rules
|
||||
|
||||
The plan on your space will determine if you are able to add alert notification silencing rules since this feature will only be available for paid plans: **Pro** or **Business**.
|
||||
|
||||
For more details check the documentation under [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#silencing-alert-notifications).
|
||||
|
||||
### Related Topics
|
||||
|
||||
#### **Related Concepts**
|
||||
|
||||
* [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces)
|
||||
* [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
|
||||
* [Events feed](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/events-feed.md)
|
||||
* [Role-Based Access model](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md)
|
||||
|
||||
#### Related Tasks
|
||||
|
||||
* [View Plan & Billing](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/view-plan-billing.md)
|
||||
Please refer to the [Netdata Cloud Pricing](https://netdata.cloud/pricing) page for more information on what each plan provides.
|
||||
|
|
|
|||
|
|
@ -7,18 +7,14 @@ Netdata Cloud's role-based-access mechanism allows you to control what functiona
|
|||
With the advent of the paid plans we revamped the roles to cover needs expressed by Netdata users, like providing more limited access to their customers, or
|
||||
being able to join any room. We also aligned the offered roles to the target audience of each plan. The end result is the following:
|
||||
|
||||
| **Role** | **Community** | **Pro** | **Business** | **Early Bird** |
|
||||
| :-- | :--: | :--: | :--: | :--: |
|
||||
| **Administrators**<p>Users with this role can control Spaces, War Rooms, Nodes, Users and Billing.</p><p>They can also access any War Room in the Space.</p> | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| **Managers**<p>Users with this role can manage War Rooms and Users.</p><p>They can access any War Room in the Space.</p> | - | - | :heavy_check_mark: | - |
|
||||
| **Troubleshooters**<p>Users with this role can use Netdata to troubleshoot, not manage entities.</p><p>They can access any War Room in the Space.</p> | - | :heavy_check_mark: | :heavy_check_mark: | - |
|
||||
| **Observers**<p>Users with this role can only view data in specific War Rooms.</p>💡 Ideal for restricting your customer's access to their own dedicated rooms.<p></p> | - | - | :heavy_check_mark: | - |
|
||||
| **Billing**<p>Users with this role can handle billing options and invoices.</p> | - | - | :heavy_check_mark: | - |
|
||||
| **Member** ⚠️ Legacy role<p>Users with this role can create War Rooms and invite other Members.</p><p>They can only see the War Rooms they belong to and all Nodes in the All Nodes room.</p>| - | - | - | :heavy_check_mark: |
|
||||
|
||||
## What happens to the previous Member role?
|
||||
|
||||
We will maintain a Early Bird plan for existing users, which will continue to provide access to the Member role.
|
||||
| **Role** | **Community** | **Homelab** | **Business** | **Enterprise On-Premise** |
|
||||
|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------|:-------------------|:-------------------|:--------------------------|
|
||||
| **Admins**<p>Users with this role can control Spaces, War Rooms, Nodes, Users and Billing.</p><p>They can also access any War Room in the Space.</p> | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| **Managers**<p>Users with this role can manage War Rooms and Users.</p><p>They can access any War Room in the Space.</p> | - | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| **Troubleshooters**<p>Users with this role can use Netdata to troubleshoot, not manage entities.</p><p>They can access any War Room in the Space.</p> | - | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| **Observers**<p>Users with this role can only view data in specific War Rooms.</p>💡 Ideal for restricting your customer's access to their own dedicated rooms.<p></p> | - | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| **Billing**<p>Users with this role can handle billing options and invoices.</p> | - | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| **Member** ⚠️ Legacy role<p>Users with this role you can create War Rooms and invite other Members.</p><p>They can only see the War Rooms they belong to and all Nodes in the All Nodes room.</p> | - | - | - | - |
|
||||
|
||||
## Which functionalities are available for each role?
|
||||
|
||||
|
|
@ -26,91 +22,91 @@ In more detail, you can find on the following tables which functionalities are a
|
|||
|
||||
### Space Management
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: |
|
||||
| See Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Leave Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Delete Space | :heavy_check_mark: | - | - | - | - | - |
|
||||
| Change name | :heavy_check_mark: | - | - | - | - | - |
|
||||
| Change description | :heavy_check_mark: | - | - | - | - | - |
|
||||
| Change slug | :heavy_check_mark: | - | - | - | - | - |
|
||||
| Change preferred nodes | :heavy_check_mark: | - | - | - | - | - |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
|
||||
|:-----------------------|:------------------:|:------------------:|:------------------:|:------------------:|:------------------:|:------------------:|
|
||||
| See Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Leave Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Delete Space | :heavy_check_mark: | - | - | - | - | - |
|
||||
| Change name | :heavy_check_mark: | - | - | - | - | - |
|
||||
| Change description | :heavy_check_mark: | - | - | - | - | - |
|
||||
| Change slug | :heavy_check_mark: | - | - | - | - | - |
|
||||
| Change preferred nodes | :heavy_check_mark: | - | - | - | - | - |
|
||||
|
||||
### Node Management
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
|
||||
| See all Nodes in Space (_All Nodes_ room) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: | Members are always on the _All Nodes_ room |
|
||||
| Connect Node to Space | :heavy_check_mark: | - | - | - | - | - | - |
|
||||
| Delete Node from Space | :heavy_check_mark: | - | - | - | - | - | - |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
|:------------------------------------------|:------------------:|:------------------:|:------------------:|:------------:|:-----------:|:------------------:|:-------------------------------------------|
|
||||
| See all Nodes in Space (_All Nodes_ room) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: | Members are always on the _All Nodes_ room |
|
||||
| Connect Node to Space | :heavy_check_mark: | - | - | - | - | - | - |
|
||||
| Delete Node from Space | :heavy_check_mark: | - | - | - | - | - | - |
|
||||
|
||||
### User Management
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
|
||||
| See all Users in Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| Invite new User to Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | You can't invite a user with a role you don't have permissions to appoint to (see below) |
|
||||
| Delete Pending Invitation to Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| Delete User from Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | You can't delete a user if he has a role you don't have permissions to appoint to (see below) |
|
||||
| Appoint Administrators | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Appoint Billing user | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Appoint Managers | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Appoint Troubleshooters | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Appoint Observer | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Appoint Member | :heavy_check_mark: | - | - | - | - | :heavy_check_mark: | Only available on Early Bird plans |
|
||||
| See all Users in a Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
|
||||
| Invite existing user to Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | User already invited to the Space |
|
||||
| Remove user from Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
|:-----------------------------------|:------------------:|:------------------:|:------------------:|:------------------:|:-----------:|:------------------:|:----------------------------------------------------------------------------------------------|
|
||||
| See all Users in Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| Invite new User to Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | You can't invite a user with a role you don't have permissions to appoint to (see below) |
|
||||
| Delete Pending Invitation to Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| Delete User from Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | You can't delete a user if he has a role you don't have permissions to appoint to (see below) |
|
||||
| Appoint Administrators | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Appoint Billing user | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Appoint Managers | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Appoint Troubleshooters | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Appoint Observer | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Appoint Member | :heavy_check_mark: | - | - | - | - | :heavy_check_mark: | Only available on Early Bird plans |
|
||||
| See all Users in a Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
|
||||
| Invite existing user to Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | User already invited to the Space |
|
||||
| Remove user from Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
|
||||
### Room Management
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
|
||||
| See all Rooms in a Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | - | |
|
||||
| Join any Room in a Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | - | By joining a room you will be enabled to get notifications from nodes on that room |
|
||||
| Leave Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
|
||||
| Create a new Room in a Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| Delete Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Change Room name | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | If not the _All Nodes_ room |
|
||||
| Change Room description | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| Add existing Nodes to Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | Node already connected to the Space |
|
||||
| Remove Nodes from Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
|:-----------------------------|:------------------:|:------------------:|:------------------:|:------------------:|:-----------:|:------------------:|:-----------------------------------------------------------------------------------|
|
||||
| See all Rooms in a Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | - | |
|
||||
| Join any Room in a Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | - | By joining a room you will be enabled to get notifications from nodes on that room |
|
||||
| Leave Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
|
||||
| Create a new Room in a Space | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| Delete Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Change Room name | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | If not the _All Nodes_ room |
|
||||
| Change Room description | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
| Add existing Nodes to Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | Node already connected to the Space |
|
||||
| Remove Nodes from Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
|
||||
|
||||
### Notifications Management
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
|
||||
| See all configured notifications on a Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
|
||||
| Add new configuration | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Enable/Disable configuration | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Edit configuration | :heavy_check_mark: | - | - | - | - | - | Some exceptions apply depending on [service level](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md#available-actions-per-notification-methods-based-on-service-level) |
|
||||
| Delete configuration | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Edit personal level notification settings | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | [Manage user notification settings](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md#manage-user-notification-settings) |
|
||||
| See space alert notification silencing rules | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | - | |
|
||||
| Add new space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Enable/Disable space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Edit space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Delete space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| See, add, edit or delete personal level alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
|:--------------------------------------------------------------------------|:------------------:|:------------------:|:------------------:|:------------------:|:------------------:|:------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| See all configured notifications on a Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
|
||||
| Add new configuration | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Enable/Disable configuration | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Edit configuration | :heavy_check_mark: | - | - | - | - | - | Some exceptions apply depending on [service level](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md#available-actions-per-notification-methods-based-on-service-level) |
|
||||
| Delete configuration | :heavy_check_mark: | - | - | - | - | - | |
|
||||
| Edit personal level notification settings | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | [Manage user notification settings](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md#manage-user-notification-settings) |
|
||||
| See space alert notification silencing rules | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | - | |
|
||||
| Add new space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Enable/Disable space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Edit space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| Delete space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
|
||||
| See, add, edit or delete personal level alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | |
|
||||
|
||||
|
||||
Notes:
|
||||
* Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#service-classification))
|
||||
> **Note**
|
||||
>
|
||||
> Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#service-classification))
|
||||
|
||||
### Dashboards
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: |
|
||||
| See all dashboards in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Add new dashboard to Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Edit any dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
|
||||
| Edit own dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Delete any dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
|
||||
| Delete own dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
|
||||
|:-----------------------------|:------------------:|:------------------:|:------------------:|:------------------:|:-----------:|:------------------:|
|
||||
| See all dashboards in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Add new dashboard to Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Edit any dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
|
||||
| Edit own dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Delete any dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
|
||||
| Delete own dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
|
||||
### Functions
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
|
||||
| See all functions in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Run any function in Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - |
|
||||
|
|
@ -119,27 +115,27 @@ Notes:
|
|||
|
||||
### Events feed
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
|
||||
| See Alert or Topology events | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
|
||||
| See Auditing events | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | These are coming soon, not currently available |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
|:-----------------------------|:------------------:|:------------------:|:------------------:|:------------------:|:-----------:|:------------------:|:-----------------------------------------------|
|
||||
| See Alert or Topology events | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
|
||||
| See Auditing events | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | These are coming soon, not currently available |
|
||||
|
||||
### Billing
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
|
||||
| See Plan & Billing details | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | Current plan and usage figures |
|
||||
| Update plans | :heavy_check_mark: | - | - | - | - | - | This includes cancelling current plan (going to Community plan) |
|
||||
| See invoices | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | |
|
||||
| Manage payment methods | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | |
|
||||
| Update billing email | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
|
||||
|:---------------------------|:------------------:|:-----------:|:------------------:|:------------:|:------------------:|:----------:|:----------------------------------------------------------------|
|
||||
| See Plan & Billing details | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | Current plan and usage figures |
|
||||
| Update plans | :heavy_check_mark: | - | - | - | - | - | This includes cancelling current plan (going to Community plan) |
|
||||
| See invoices | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | |
|
||||
| Manage payment methods | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | |
|
||||
| Update billing email | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | |
|
||||
|
||||
### Other permissions
|
||||
|
||||
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
|
||||
| :-- | :--: | :--: | :--: | :--: | :--: | :--: |
|
||||
| See Bookmarks in Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Add Bookmark to Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
|
||||
| Delete Bookmark from Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
|
||||
| See Visited Nodes | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Update Visited Nodes | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| **Functionality** | **Admin** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
|
||||
|:---------------------------|:------------------:|:------------------:|:------------------:|:------------------:|:-----------:|:------------------:|
|
||||
| See Bookmarks in Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Add Bookmark to Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
|
||||
| Delete Bookmark from Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
|
||||
| See Visited Nodes | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
| Update Visited Nodes | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
|
||||
|
|
|
|||
|
|
@ -1,141 +1,82 @@
|
|||
# View Plan & Billing
|
||||
|
||||
From the Cloud interface, you can view and manage your space's plan and billing settings, and see the space's usage in terms of running nodes.
|
||||
|
||||
To view and manage some specific settings, related to billing options and invoices, you'll be redirected to our billing provider Customer Portal.
|
||||
This section outlines how to view and manage your Space's plan, billing settings, and usage from the Netdata Cloud interface.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
To see your plan and billing setting you need:
|
||||
|
||||
- A Cloud account
|
||||
- Access to the space as an Administrator or Billing user
|
||||
- A Netdata Cloud account
|
||||
- Admin or Billing user access to the Space
|
||||
|
||||
## Steps
|
||||
|
||||
### View current plan and Billing options and Invoices
|
||||
### View Current Plan, Billing Options, and Invoices
|
||||
|
||||
1. Click on the **Space settings** cog (located above your profile icon)
|
||||
1. Click on the **Plan & Billing** tab
|
||||
1. On this page you will be presented with information on your current plan, billing settings, and usage information:
|
||||
1. At the top of the page you will see:
|
||||
- **Credit** amount which refers to any amount you have available to use on future invoices or subscription changes ([Plan changes and credit balance](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plan-changes-and-credit-balance)) - this is displayed once you have had an active paid subscription with us
|
||||
- **Billing email** the email that was specified to be linked to tha plan subscription. This is where invoices, payment, and subscription-related notifications will be sent.
|
||||
- **Billing options and Invoices** is the link to our billing provider Customer Portal where you will be able to:
|
||||
- See the current subscription. There will always be 2 subscriptions active for the two pricing components mentioned on [Netdata Plans documentation page](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plans)
|
||||
- Change directly the payment method associated to current subscriptions
|
||||
- View, add, delete or change your default payment methods
|
||||
- View or change or Billing information:
|
||||
- Billing email
|
||||
- Address
|
||||
- Phone number
|
||||
- Tax ID
|
||||
- View your invoice history
|
||||
1. At the middle, you'll see details on your current plan as well as means to:
|
||||
- Upgrade or cancel your plan
|
||||
- View **All Plans** details page
|
||||
1. At the bottom, you will find your Usage chart that displays:
|
||||
- Daily count - The weighted 90th percentile of the live node count during the day, taking time as the weight. If you have 30 live nodes throughout the day
|
||||
except for a two hour peak of 44 live nodes, the daily value is 31.
|
||||
- Period count: The 90th percentile of the daily counts for this period up to the date. The last value for the period is used as the number of nodes for the bill for that period. See more details in [running nodes and billing](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#running-nodes-and-billing) (only applicable if you are on a paid plan subscription)
|
||||
- Committed nodes: The number of nodes committed to in the yearly plan. In case the period count is higher than the number of committed nodes, the difference is billed as overage.
|
||||
1. Navigate to **Space settings** (the cog above your profile icon).
|
||||
2. Select the **Plan & Billing** tab.
|
||||
3. You'll see:
|
||||
- **Credit** amount, if applicable, usable for future invoices or subscription changes. More on this at [Plan changes and credit balance](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plan-changes-and-credit-balance).
|
||||
- **Billing email** linked to your subscription, where all related notifications are sent.
|
||||
- A link to the **Billing options and Invoices** in our billing provider's Customer Portal, where you can:
|
||||
- Manage subscriptions and payment methods.
|
||||
- Update billing information such as email, address, phone number, and Tax ID.
|
||||
- View invoice history.
|
||||
- The **Change plan** button, showing details of your current plan with options to upgrade or cancel.
|
||||
- Your **Usage chart**, displaying daily and period counts of live nodes and how they relate to your billing.
|
||||
|
||||
### Update a Subscription Plan
|
||||
|
||||
### Update plan
|
||||
1. In the **Plan & Billing** tab, click **Change plan** to see:
|
||||
- Billing frequency and committed nodes (if applicable).
|
||||
- Current billing information, which must be updated through our billing provider's Customer Portal via **Change billing info and payment method** link.
|
||||
- Options to enter a promotion code and a breakdown of charges, including subscription total, applicable discounts, credit usage, tax details, and total payable amount.
|
||||
|
||||
1. Click on the **Space settings** cog (located above your profile icon)
|
||||
1. Click on the **Plan & Billing** tab
|
||||
1. On this page you will be presented with information on your current plan, billing settings, and usage information
|
||||
1. Depending on your plan there could be shortcuts to immediately take you to change, for example, the billing frequency to **Yearly**
|
||||
1. Most actions will be available under the **Change plan** link that take you to the **All plans** details page where you can
|
||||
1. Downgrade or upgrade your plan
|
||||
1. Change the billing frequency
|
||||
1. Change committed nodes, in case you are on a Yearly plan
|
||||
1. Once you chose an action to update your plan a modal will pop-up on the right with
|
||||
1. Billing frequency displayed on the top right-corner
|
||||
1. Committed Nodes, when applicable
|
||||
1. Current billing information:
|
||||
- Billing email
|
||||
- Default payment method
|
||||
- Business name and VAT number, when these are applicable
|
||||
- Billing Address
|
||||
Note: Any changes to these need to done through our billing provider Customer Portal prior to confirm the checkout. You can click on the link **Change billing info and payment method** to access it.
|
||||
1. Promotion code, so you can review any applied promotion or enter one you may have
|
||||
1. Detailed view on Node and Space charges
|
||||
1. Breakdown of:
|
||||
- Subscription Total
|
||||
- Discount from promotion codes, if applicable
|
||||
- credit value for Unused time from current plan, if applicable
|
||||
- Credit amount used from balance, if applicable
|
||||
- Total Before Tax
|
||||
- VAT rate and amount, if applicable
|
||||
1. Summary of:
|
||||
- Total payable amount
|
||||
- credit adjustment value for any Remaining Unused time from current plan, if applicable
|
||||
- Final credit balance
|
||||
|
||||
Notes:
|
||||
* Since there is an active plan you won't be redirected to our billing provider, the checkout if performed as soon as you click on **Checkout**
|
||||
* The change to your plan will be applied as soon as the checkout process is completed successfully
|
||||
* Downgrade or cancellations may have impacts on some of notification method settings or user accesses to your space, for more details please check [Plan changes and credit balance](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plan-changes-and-credit-balance)
|
||||
> **Note**
|
||||
>
|
||||
> - Checkout is performed directly if there's an active plan.
|
||||
> - Plan changes, including downgrades or cancellations, may impact notification settings or user access. More details at [Plan changes and credit balance](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plan-changes-and-credit-balance).
|
||||
|
||||
## FAQ
|
||||
|
||||
### 1. What Payment Methods are accepted?
|
||||
### What Payment Methods are Accepted?
|
||||
|
||||
You can easily pay online via most major Credit/Debit Cards. More payment options are expected to become available in the near future.
|
||||
Netdata accepts most major Credit/Debit Cards and Bank payments through Stripe and AWS, with more options coming soon.
|
||||
|
||||
### 2. What happens if a renewal payment fails?
|
||||
### What Happens if a Renewal Payment Fails?
|
||||
|
||||
After an initial failed payment, we will attempt to process your payment every week for the next 15 days. After three failed attempts your Space will be moved to the **Community** plan (free forever).
|
||||
If payment fails, attempts will be made weekly for 15 days. After three unsuccessful attempts, your Space will switch to the **Community** plan. Notification methods not supported by the Community plan will be disabled after 24 hours.
|
||||
|
||||
For the next 24 hours, you will be able to use all your current notification method configurations. After 24 hours, any of the notification method configurations that aren't available on your space's plan will be automatically disabled.
|
||||
### Which Currencies Do You Support?
|
||||
|
||||
Cancellation might affect users in your Space. Please check what roles are available on the [Community plan](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#areas-impacted-by-plans). Users with unavailable roles on the Community plan will immediately have restricted access to the Space.
|
||||
Currently, we accept US Dollars (USD). Plans to accept Euros (EUR) are in the works but without a set timeline.
|
||||
|
||||
### 3. Which currencies do you support?
|
||||
### Can I Get a Refund?
|
||||
|
||||
We currently accept payments only in US Dollars (USD). We currently have plans to also accept payments in Euros (EUR), but do not currently have an estimate for when such support will be available.
|
||||
Refunds are available if you cancel your subscription within 14 days of purchase. Request a refund via [billing@netdata.cloud](mailto:billing@netdata.cloud).
|
||||
|
||||
### 4. Can I get a refund? How?
|
||||
### How Do I Cancel My Paid Plan?
|
||||
|
||||
Payments for Netdata subscriptions are refundable **only** if you cancel your subscription within 14 days of purchase. The refund will be credited to the Credit/Debit Card used for making the purchase. To request a refund, please email us at [billing@netdata.cloud](mailto:billing@netdata.cloud).
|
||||
Cancel your plan anytime from the **Plan & Billing** section by selecting 'Cancel Plan' or switching to the **Community** plan.
|
||||
|
||||
### 5. How do I cancel my paid Plan?
|
||||
### How Can I Access My Invoices/Receipts?
|
||||
|
||||
Your annual or monthly Netdata Subscription plan will automatically renew until you cancel it. You can cancel your paid plan at any time by clicking ‘Cancel Plan’ from the **Plan & Billing** section under settings. You can also cancel your paid Plan by clicking the _Select_ button under **Community** plan in the **Plan & Billing** Section under Settings.
|
||||
Find all your invoicing history under _Billing Options & Invoices_ in the **Plan & Billing** section.
|
||||
|
||||
### 6. How can I access my Invoices/Receipts after I paid for a Plan?
|
||||
### Why Do I See Two Separate Invoices?
|
||||
|
||||
You can visit the _Billing Options & Invoices_ in the **Plan & Billing** section under settings in your Netdata Space where you can find all your Invoicing history.
|
||||
Two invoices are generated per plan purchase or renewal:
|
||||
|
||||
### 7. Why do I see two separate Invoices?
|
||||
- One for recurring fees of the chosen plan.
|
||||
- Another for monthly "On-Demand - Usage" based on actual usage.
|
||||
|
||||
Every time you purchase or renew a Plan, two separate Invoices are generated:
|
||||
### How is the **Total Before Tax** Value Calculated on Plan Changes?
|
||||
|
||||
- One Invoice includes the recurring fees of the Plan you have chosen
|
||||
The total before tax is calculated by:
|
||||
|
||||
We have waived off the space subscription free ($0.00), so the only recurring fee will be on annual plans for the committed nodes.
|
||||
1. Calculating the residual value from unused time on your current plan.
|
||||
2. Deducting any applicable discounts.
|
||||
3. Subtracting credit from your balance, if necessary.
|
||||
4. Applying tax to the final amount, if positive. Negative results adjust your customer credit balance.
|
||||
|
||||
- The other Invoice includes your monthly “On Demand - Usage”.
|
||||
|
||||
Right after the activation of your subscription, you will receive a zero value Invoice since you had no usage when you subscribed.
|
||||
|
||||
On the following month you will receive an Invoice based on your monthly usage.
|
||||
|
||||
You can find some further details on the [Netdata Plans page](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plans).
|
||||
|
||||
> ⚠️ We expect this to change to a single invoice in the future, but currently do not have a concrete timeline for when this change will happen.
|
||||
|
||||
### 8. How is the **Total Before Tax** value calculated on plan changes?
|
||||
|
||||
When you change your plan we will be calculating the residual before tax value you have from the _Unused time on your current plan_ in order to credit you with this value.
|
||||
|
||||
After that, we will be performing the following calculations:
|
||||
|
||||
1. Get the **Subscription total** (total amount to be paid for Nodes and Space)
|
||||
2. Deduct any Discount applicable from promotion codes
|
||||
3. If an amount remains, then we deduct the sum of the _Unused time on current plan_ then and the Credit amount from any existing credit balance.
|
||||
4. The result, if positive, is the Total Before Tax, if applicable, any sales tax (VAT or other) will apply.
|
||||
|
||||
If the calculation of step 3 returns a negative amount then this amount will be your new customer credit balance.
|
||||
> **Note**
|
||||
>
|
||||
> A move to single-invoice billing is expected in the future, although a specific timeline is not set.
|
||||
|
|
|
|||
|
|
@ -23,9 +23,9 @@ From this tab, you can also filter alerts with the right hand bar. More specific
|
|||
- Host labels
|
||||
- Filter based on the host labels that are configured for the nodes across the War Room (e.g. `_cloud_instance_region` to match `us-east-1`)
|
||||
- Node status
|
||||
- Filter by node availability status (e.g. Live or Offline)
|
||||
- Filter by node availability status (e.g. Live or Offline)
|
||||
- Netdata version
|
||||
- Filter by Netdata version (e.g. `v1.45.3`)
|
||||
- Filter by Netdata version (e.g. `v1.45.3`)
|
||||
- Nodes
|
||||
- Filter the alerts based on the nodes of your War Room.
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ By clicking on the name of an entry of the table you can access that alert's det
|
|||
|
||||
- Latest and Triggered time values
|
||||
- The alert's description
|
||||
- A link to the Netdata Advisor's page about this alert
|
||||
- A link to the Netdata Advisor's page about this alert
|
||||
- The chart at the time frame that the alert was triggered
|
||||
- The alert's information: Node name, chart instance, type, component and class
|
||||
- Configuration section
|
||||
|
|
@ -45,7 +45,7 @@ At the bottom of the panel you can click the green button "View alert page" to o
|
|||
|
||||
### Silence an alert
|
||||
|
||||
From this tab, the "Silencing" column shows if there is any rule present for each alert, and from the "Actions" column you can create a new [silencing rule](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#silencing-alert-notifications) for this alert, or get help and information about this alert from the [Netdata Assistant](https://github.com/netdata/netdata/blob/master/docs/cloud/netdata-assistant.md).
|
||||
From this tab, the "Silencing" column shows if there is any rule present for each alert, and from the "Actions" column you can create a new [silencing rule](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#alert-notifications-silencing-rules) for this alert, or get help and information about this alert from the [Netdata Assistant](https://github.com/netdata/netdata/blob/master/docs/cloud/netdata-assistant.md).
|
||||
|
||||
## Alert Configurations tab
|
||||
|
||||
|
|
@ -53,7 +53,6 @@ From this tab you can view all the configurations for all running alerts in your
|
|||
|
||||
By running alerts we mean alerts that are related to some metric that is or was collected. Netdata may have more alerts pre-configured that aren't applicable to your monitoring use-cases.
|
||||
|
||||
|
||||
You can control which columns are visible by using the gear icon on the right-hand side.
|
||||
|
||||
Similarly to the previous tab, you can see the silencing status of an alert, while also being able to dig deeper and show the configuration for the alert and ask the [Netdata Assistant](https://github.com/netdata/netdata/blob/master/docs/cloud/netdata-assistant.md) for help.
|
||||
|
|
|
|||
|
|
@ -19,8 +19,8 @@
|
|||
### Prerequisites
|
||||
- An Okta account
|
||||
- A Netdata Cloud account
|
||||
- Access to the Space as an administrator
|
||||
- Space needs to be on the Business plan or higher
|
||||
- Access to the Space as an **Admin**
|
||||
- Space needs to be on a paid plan
|
||||
|
||||
### Setting up Okta
|
||||
Steps needed to be done on Okta Admin Portal:
|
||||
|
|
@ -66,8 +66,8 @@
|
|||
### Prerequisites
|
||||
- Authorization Server with OIDC protocol supported
|
||||
- A Netdata Cloud account
|
||||
- Access to the Space as an administrator
|
||||
- Space needs to be on the Business plan or higher
|
||||
- Access to the Space as an **Admin**
|
||||
- Space needs to be on a paid plan
|
||||
|
||||
### Setting up Authorization Server
|
||||
Your server should follow the [full specification for OIDC](https://openid.net/specs/openid-connect-core-1_0.html).
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@
|
|||
2. Open the App and Choose the Sign In Option
|
||||
- Sign In with Email Address: Enter the Email Address of your registered Netdata Cloud Account and Click on the Verification link received by Email on your mobile device.
|
||||
- Sign In with QR Code: Scan the QR Code from your `Netdata Cloud` UI under **User Settings** --> **Notifications** --> **Mobile App Notifications** --> **Show QR Code**
|
||||
3. Start receiving alert and reachability notifications for your **Space(s)** on a **Paid Business Subscription**
|
||||
3. Start receiving alert and reachability notifications for your **Space(s)** on a **Paid Subscription plan**
|
||||
|
||||
### Netdata Configuration Steps
|
||||
1. Click on the **User settings** on the bottom left of your screen (your profile icon)
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
description: |
|
||||
### Prerequisites
|
||||
- A Netdata Cloud account
|
||||
- Access to the Netdata Space as an **administrator**
|
||||
- Access to the Netdata Space as an **Admin**
|
||||
- You need to have a Discord server able to receive webhooks integrations.
|
||||
|
||||
### Discord Server Configuration
|
||||
|
|
@ -91,8 +91,8 @@
|
|||
description: |
|
||||
### Prerequisites
|
||||
- A Netdata Cloud account
|
||||
- Access to the Netdata Space as an **administrator**
|
||||
- The Netdata Space needs to be on **Business** plan or higher
|
||||
- Access to the Netdata Space as an **Admin**
|
||||
- The Netdata Space needs to be on a paid plan
|
||||
- You need to have a PagerDuty service to receive events using webhooks.
|
||||
|
||||
|
||||
|
|
@ -135,8 +135,8 @@
|
|||
### Prerequisites
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the Netdata Space as an **administrator**
|
||||
- The Netdata Space needs to be on **Business** plan or higher
|
||||
- Access to the Netdata Space as an **Admin**
|
||||
- The Netdata Space needs to be on a paid plan
|
||||
- You need to have a Slack app on your workspace to receive the Webhooks.
|
||||
|
||||
### Slack Server Configuration
|
||||
|
|
@ -185,8 +185,8 @@
|
|||
### Prerequisites
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the Netdata Space as an **administrator**
|
||||
- The Netdata Space needs to be on **Business** plan or higher
|
||||
- Access to the Netdata Space as an **Admin**
|
||||
- The Netdata Space needs to be on a paid plan
|
||||
- You need to have permissions on Opsgenie to add new integrations.
|
||||
|
||||
### Opsgenie Server Configuration
|
||||
|
|
@ -228,8 +228,8 @@
|
|||
### Prerequisites
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the Netdata Space as an **administrator**
|
||||
- The Netdata Space needs to be on **Business** plan or higher
|
||||
- Access to the Netdata Space as an **Admin**
|
||||
- The Netdata Space needs to be on a paid plan
|
||||
- You need to have permissions on Mattermost to add new integrations.
|
||||
- You need to have a Mattermost app on your workspace to receive the webhooks.
|
||||
|
||||
|
|
@ -279,8 +279,8 @@
|
|||
### Prerequisites
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the Netdata Space as an **administrator**
|
||||
- The Netdata Space needs to be on **Business** plan or higher
|
||||
- Access to the Netdata Space as an **Admin**
|
||||
- The Netdata Space needs to be on a paid plan
|
||||
- You need to have permissions on Mattermost to add new integrations.
|
||||
- You need to have a RocketChat app on your workspace to receive the webhooks.
|
||||
|
||||
|
|
@ -332,8 +332,8 @@
|
|||
To add AWS SNS notification you need:
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the space as an **administrator**
|
||||
- Space needs to be on **Business** plan or higher
|
||||
- Access to the space as an **Admin**
|
||||
- The Space needs to be on a paid plan
|
||||
- Have an AWS account with AWS SNS access, for more details check [how to configure this on AWS SNS](#settings-on-aws-sns)
|
||||
|
||||
### Steps
|
||||
|
|
@ -381,8 +381,8 @@
|
|||
To add Microsoft Teams notifications integration to your Netdata Cloud space you will need the following:
|
||||
|
||||
- A Netdata Cloud account.
|
||||
- Access to the Netdata Cloud space as an **administrator**.
|
||||
- The Space to be on **Business** plan or higher.
|
||||
- Access to the Netdata Cloud space as an **Admin**.
|
||||
- The Space to be on a paid plan.
|
||||
- A [Microsoft 365 for Business Account](https://www.microsoft.com/en-us/microsoft-365/business). Note that this is a **paid** account.
|
||||
|
||||
### Settings on Microsoft Teams
|
||||
|
|
@ -430,8 +430,8 @@
|
|||
To add Telegram notification you need:
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the space as an **administrator**
|
||||
- Space needs to be on **Business** plan or higher
|
||||
- Access to the space as an **Admin**
|
||||
- The Space needs to be on a paid plan
|
||||
- The Telegram bot token and chat ID
|
||||
|
||||
### Steps
|
||||
|
|
@ -475,8 +475,8 @@
|
|||
To add Splunk notification you need:
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the space as an **administrator**
|
||||
- Space needs to be on **Business** plan or higher
|
||||
- Access to the space as an **Admin**
|
||||
- The Space needs to be on a paid plan
|
||||
- URI and token for your Splunk HTTP Event Collector. Refer to the [Splunk documentation](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) for detailed instructions.
|
||||
|
||||
### Steps
|
||||
|
|
@ -515,8 +515,8 @@
|
|||
To add Splunk VictorOps notification (also known as Splunk On-Call) you need:
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the space as an **administrator**
|
||||
- Space needs to be on **Business** plan or higher
|
||||
- Access to the space as an **Admin**
|
||||
- The Space needs to be on a paid plan
|
||||
- Destination URL for your Splunk VictorOps REST Endpoint Integration. Refer to the [VictorOps documentation](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide) for detailed instructions.
|
||||
|
||||
### Steps
|
||||
|
|
@ -551,8 +551,8 @@
|
|||
### Prerequisites
|
||||
|
||||
- A Netdata Cloud account
|
||||
- Access to the Netdata Space as an **administrator**
|
||||
- The Netdata Space needs to be on **Pro** plan or higher
|
||||
- Access to the Netdata Space as an **Admin**
|
||||
- The Netdata Space needs to be on a paid plan
|
||||
- You need to have an app that allows you to receive webhooks following a predefined schema.
|
||||
|
||||
### Netdata Configuration Steps
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue