-
Notifications
You must be signed in to change notification settings - Fork 128
added STM zones file #5160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
emgcentreon
wants to merge
32
commits into
staging
Choose a base branch
from
MON-195661_stm_zones
base: staging
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
added STM zones file #5160
Changes from all commits
Commits
Show all changes
32 commits
Select commit
Hold shift + click to select a range
b7331eb
added STM zones file
emgcentreon b57eb2c
added organization page image
emgcentreon 6057174
Update cxm/sidebarsCxm.js
emgcentreon bcfdba3
Apply suggestions from code review
emgcentreon 992aa49
corrections
emgcentreon a1db8ec
Merge branch 'MON-195661_stm_zones' of https://github.com/centreon/ce…
emgcentreon 0f0decf
Update stm-zone.md
emgcentreon 5f59818
Update stm-zone.md
emgcentreon 51def2a
Update stm-zone.md
emgcentreon 78ec432
Apply suggestions from code review
emgcentreon d172667
corrections to STM zones
emgcentreon fc93c5e
Delete i18n/fr/docusaurus-plugin-content-docs-cxm/current/assets/conf…
emgcentreon 3607ffc
Add files via upload
emgcentreon ee16330
Apply suggestions from code review
emgcentreon afb11f8
Apply suggestions from code review
emgcentreon aa21d37
Apply suggestions from code review
emgcentreon 00678a9
Merge branch 'staging' into MON-195661_stm_zones
smau-centreon 64ec33d
Improved formatting and fixed broken link
smau-centreon efcd7e1
Merge branch 'MON-195661_stm_zones' of https://github.com/centreon/ce…
smau-centreon ea66715
corrections to stm zones
emgcentreon f7d1308
correction to STM zones
emgcentreon d016201
Apply suggestions from code review
emgcentreon 62bf854
corrections to STM zones
emgcentreon f822af2
Apply suggestions from code review
emgcentreon b066d09
corrections to STM zones
emgcentreon dc566e9
stm zones
emgcentreon 074fcbf
STM zones
emgcentreon 4e0531b
add STM zones
emgcentreon e5a6f30
Update create-a-scenario.md
emgcentreon 3dab135
Update create-a-scenario.md
emgcentreon fda938c
Apply suggestions from code review
emgcentreon 8a3b9aa
Apply suggestions from code review
emgcentreon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| --- | ||
| id: stm-zones | ||
| title: Monitoring non-public user journeys (closed beta) | ||
| --- | ||
|
|
||
| A private Synthetic Monitoring Zone (STM Zone) allows you to monitor your user journeys on internal domains or networks specific to your organization using a probe deployed inside your infrastructure. | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| - A machine inside your infrastructure to host the probe. The machine must be able to access the application you will monitor. | ||
| - The Docker credentials provided by Centreon. The credentials are sent by Centreon using a secure Keeper link. Save these credentials in your own safe. | ||
| - A user journey configured on the internal application to monitor. | ||
|
|
||
| ## Step 1: Create a new STM zone | ||
|
|
||
| 1. From the **Global View**, open the site selector in the top-left corner and select your organization’s page. | ||
|
|
||
|  | ||
|
|
||
| 2. On your organization’s configuration page, click the **Synthetic Monitoring Zones** tab. | ||
|
|
||
| 3. Click **+ New Synthetic Monitoring Zone**. Give the zone a meaningful name (e.g., Paris Office) then click **+ Create**. | ||
|
|
||
| Your new zone now appears in the list. | ||
|
|
||
| ## Step 2: Associate a probe to the STM zone | ||
|
|
||
| 1. Click **Associate a probe** to the right of your zone. A window opens with 2 Docker commands: | ||
|
|
||
| 2. Use the first command to log into the Centreon Docker registry with [the credentials provided by Centreon](#prerequisites) | ||
|
|
||
| ```shell | ||
| docker login docker.centreon.com/centreon-dem-beta | ||
| ``` | ||
|
|
||
| ## Step 3: Create and launch the probe | ||
|
|
||
| 1. To create and launch the probe, execute the second command you obtained at [step 2](#step-2-associate-a-probe-to-an-stm). | ||
|
|
||
| 2. Refresh the page: once launched, the probe is automatically saved and appears to the right of the associated zone in the **Synthetic Monitoring Zones** list. | ||
|
|
||
| ## Step 4: Associate the zone with a user journey | ||
|
|
||
| 1. Go to **Configuration** and select the **User Journeys** tab. | ||
|
|
||
| 2. On the journey you want to run from your private zone, click on the three dots on the right, then click on **Advanced**. | ||
|
|
||
| 3. In the **Advanced configuration** window, scroll down to the **Synthetic Monitoring Zones** section. Your private zone appears under **Private Zones**. Select it and click **Save**. | ||
|
|
||
| After a short while, the probe will have executed its first check and your internal journey monitoring will be operational. You can analyze it just like a regular [user journey](../../how-to-articles/user-journey-screen.md). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file added
BIN
+20.9 KB
...ontent-docs-cxm/current/assets/configuration/user-journey/organization-page.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
52 changes: 52 additions & 0 deletions
52
...cusaurus-plugin-content-docs-cxm/current/configuration/user-journey/stm-zone.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| --- | ||
| id: stm-zones | ||
| title: Superviser des parcours utilisateur non-publics (beta fermée) | ||
| --- | ||
|
|
||
| Une Zone de Monitoring Synthétique (zone STM) privée vous permet de superviser vos parcours utilisateur sur des domaines internes ou des réseaux propres à votre organisation, via une sonde déployée dans votre infrastructure. | ||
|
|
||
| ## Prérequis | ||
|
|
||
|
emgcentreon marked this conversation as resolved.
emgcentreon marked this conversation as resolved.
emgcentreon marked this conversation as resolved.
|
||
| - Une machine située dans votre infrastructure devra héberger une sonde. Elle devra pouvoir accéder à l'application à superviser. | ||
| - Les identifiants Docker fournis par Centreon. Les identifiants vous sont transmis par Centreon via un lien sécurisé Keeper. Sauvegardez les identifiants dans votre propre coffre-fort. | ||
| - Un parcours utilisateur configuré sur l'application interne à superviser. | ||
|
|
||
| ## Étape 1 : Créer une nouvelle zone STM | ||
|
|
||
|
emgcentreon marked this conversation as resolved.
|
||
| 1. Depuis la **Vue Globale**, ouvrez le sélecteur de site en haut à gauche et ouvrez la page de votre organisation. | ||
|
|
||
|  | ||
|
|
||
| 2. Dans la page de configuration de votre organisation, cliquez sur l'onglet **Zones de Monitoring Synthétique**. | ||
|
|
||
| 3. Cliquez sur **+ Nouvelle Zone de Monitoring Synthétique**. Donnez un nom significatif (ex. : Paris Office) à la zone puis cliquez sur **+ Créer**. | ||
|
|
||
| Votre nouvelle zone apparaît désormais dans la liste. | ||
|
|
||
| ## Étape 2 : Associer une sonde à la zone STM | ||
|
|
||
| 1. Cliquez sur **Associer une sonde** à droite de votre zone. | ||
|
|
||
| Une fenêtre s'ouvre avec 2 commandes Docker : | ||
|
|
||
| 2. Utilisez la première commande pour vous identifier au registry Docker Centreon avec [les identifiants fournis par Centreon](#prérequis) : | ||
|
|
||
| ```shell | ||
| docker login docker.centreon.com/centreon-dem-beta | ||
| ``` | ||
|
|
||
| ## Étape 3 : Créer et démarrer la sonde | ||
|
|
||
| 1. Exécutez la deuxième commande obtenue à [l'étape 2](#étape-2--associer-une-sonde-à-une-zone-stm) pour créer la sonde et la démarrer. | ||
|
|
||
| 2. Rafraîchissez la page : une fois démarrée, la sonde s'enregistre automatiquement et apparaît à droite de la zone associée dans la liste des **Zones de Monitoring Synthétique**. | ||
|
|
||
| ## Étape 4 : Associer la zone à un parcours utilisateur | ||
|
|
||
| 1. Allez dans **Configuration** et sélectionnez le **Parcours Utilisateur** de votre site. | ||
|
|
||
| 2. Sur le parcours que vous souhaitez exécuter depuis votre zone privée, cliquez sur les trois points à droite puis sur **Avancé**. | ||
|
|
||
|
emgcentreon marked this conversation as resolved.
|
||
| 3. Dans la fenêtre **Configuration avancée**, faites défiler jusqu'à la section **Zones de Monitoring Synthétique**. Votre zone privée apparaît sous **Zones Privées**. Sélectionnez-la et cliquez sur **Sauvegarder**. | ||
|
|
||
| Après un bref délai, la sonde aura réalisé son premier contrôle et votre supervision de parcours interne sera alors opérationnelle. Vous pouvez l'étudier de la même manière qu'un [parcours utilisateur](../../how-to-articles/user-journey-screen.md) normal. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.