From 43aaaa71fb2729e60a4d66e035e1453432cf8bb4 Mon Sep 17 00:00:00 2001 From: Ancairon <70198089+Ancairon@users.noreply.github.com> Date: Wed, 13 Mar 2024 08:17:30 +0000 Subject: [PATCH] Ingest new documentation --- .../manage-notification-methods.mdx | 2 +- .../centralized-cloud-notifications/pagerduty.mdx | 3 ++- docs/dashboards-and-charts/netdata-charts.mdx | 2 +- .../compile-from-source-code.mdx | 2 +- .../rest-api/netdata-badges.mdx | 2 +- docs/netdata-cloud/netdata-plans.mdx | 2 +- 6 files changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.mdx b/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.mdx index a515d0d9b..255197de0 100644 --- a/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.mdx +++ b/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.mdx @@ -76,7 +76,7 @@ Note: If an administrator has disabled a Personal [service level](/docs/alerts-& - If you're an administrator, Manager or Troubleshooter you'll also see the Rooms from a space you don't have access to on **All Rooms** tab and you can activate notifications for them by joining the room 1. On this modal you will be able to: 1. **Enable/Disable** the notification method for you, this applies accross all spaces and rooms - - Use the the toggle enable or disable the notification method + - Use the toggle enable or disable the notification method 1. **Define what notifications you want** to per space/room: All Alerts and unreachable, All Alerts, Critical only or No notifications 1. **Activate notifications** for a room you aren't a member of - From the **All Rooms** tab click on the Join button for the room(s) you want diff --git a/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/pagerduty.mdx b/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/pagerduty.mdx index 44d2c4c11..e3a621151 100644 --- a/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/pagerduty.mdx +++ b/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/pagerduty.mdx @@ -34,7 +34,7 @@ Steps to configure your PagerDuty to receive notifications from Netdata: 1. Create a service to receive events from your services directory page on PagerDuty 2. At step 3, select `Events API V2` Integration or **View Webhooks** if you already have some defined -3. Once the service is created you will be redirected to its configuration page, where you can copy the **integration key**, that you will need need to add to your notification configuration on Netdata UI. +3. Once the service is created, you will be redirected to its configuration page, where you can copy the **Integration Key** and **Integration URL (Alert Events)** fields to add them to your notification configuration in the Netdata UI. ### Netdata Configuration Steps @@ -49,5 +49,6 @@ Steps to configure your PagerDuty to receive notifications from Netdata: - Notification - you specify which notifications you want to be notified using this configuration: All Alerts and unreachable, All Alerts, Critical only * **Integration configuration** are the specific notification integration required settings, which vary by notification method. For PagerDuty: - Integration Key - is a 32 character key provided by PagerDuty to receive events on your service. + - Integration URL (Alert Events) - is the URL provided by PagerDuty where we will send notifications. diff --git a/docs/dashboards-and-charts/netdata-charts.mdx b/docs/dashboards-and-charts/netdata-charts.mdx index 251da96fe..6bf75fcf2 100644 --- a/docs/dashboards-and-charts/netdata-charts.mdx +++ b/docs/dashboards-and-charts/netdata-charts.mdx @@ -292,7 +292,7 @@ The Anomaly Rate ribbon on top of each chart visualizes the combined anomaly rat Hovering over the Anomaly Rate ribbon provides a histogram of the anomaly rates per presented dimension, for the specific point in time. -Anomaly Rate visualization does not make Netdata slower. Anomaly rate is saved in the the Netdata database, together with metric values, and due to the smart design of Netdata, it does not even incur a disk footprint penalty. +Anomaly Rate visualization does not make Netdata slower. Anomaly rate is saved in the Netdata database, together with metric values, and due to the smart design of Netdata, it does not even incur a disk footprint penalty. ## Hover over the chart diff --git a/docs/developer-and-contributor-corner/build-the-netdata-agent-yourself/compile-from-source-code.mdx b/docs/developer-and-contributor-corner/build-the-netdata-agent-yourself/compile-from-source-code.mdx index aac0b9e25..7f3106287 100644 --- a/docs/developer-and-contributor-corner/build-the-netdata-agent-yourself/compile-from-source-code.mdx +++ b/docs/developer-and-contributor-corner/build-the-netdata-agent-yourself/compile-from-source-code.mdx @@ -47,7 +47,7 @@ Additionally, the following build time features require additional dependencies: ## Preparing the source tree Certain features in Netdata require custom versions of specific libraries, -which the the build system will link statically into Netdata. These +which the build system will link statically into Netdata. These libraries and their header files must be copied into specific locations in the source tree to be used. diff --git a/docs/developer-and-contributor-corner/rest-api/netdata-badges.mdx b/docs/developer-and-contributor-corner/rest-api/netdata-badges.mdx index 2cd721d82..03f8d59f9 100644 --- a/docs/developer-and-contributor-corner/rest-api/netdata-badges.mdx +++ b/docs/developer-and-contributor-corner/rest-api/netdata-badges.mdx @@ -269,7 +269,7 @@ These are options dedicated to badges: - `fixed_width_lbl=NUMBER` and `fixed_width_val=NUMBER` - This parameter overrides auto-sizing of badges and displays them at fixed widths. `fixed_width_lbl` determines the size of the label's left side (label/name). `fixed_width_val` determines the size of the the label's right side (value). You must set both parameters together, or they will be ignored. + This parameter overrides auto-sizing of badges and displays them at fixed widths. `fixed_width_lbl` determines the size of the label's left side (label/name). `fixed_width_val` determines the size of the label's right side (value). You must set both parameters together, or they will be ignored. You should set the label/value widths wide enough to provide space for all the possible values/contents of the badge you're requesting. In case the text cannot fit the space given it will be clipped. diff --git a/docs/netdata-cloud/netdata-plans.mdx b/docs/netdata-cloud/netdata-plans.mdx index 950df593b..c8467664a 100644 --- a/docs/netdata-cloud/netdata-plans.mdx +++ b/docs/netdata-cloud/netdata-plans.mdx @@ -71,7 +71,7 @@ To achieve this you can check the [Update plan](/docs/netdata-cloud/view-plan-&- > ⚠️ Downgrade or cancellation may affect users in your Space. Please check what roles are available on the [each plans](/docs/netdata-cloud/netdata-plans#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 the **end of the following year**. +> ⚠️ 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