# Using impact analysis {% embed url="" %} *** The impact analysis is available from the tab of the same name in each of the park elements. {% hint style="success" %} **Example of infrastructure** We'll take a simple example. A router is connected to a switch to which a rack containing a server is attached. ![alt text](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-0d528514dcd34eae59e65a915976882527bf7cf7%2Fanalysis_impact-1.png?alt=media) {% endhint %} ## Notions 2 concepts need to be understood: * **Impact**: represented by default by a red arrow. If this element encounters a problem, it will impact all linked elements. * **Dependency**: represented by default by a blue arrow. A dependency is an element which will be directly affected by the impact. A dependency does not necessarily affect the elements linked to it. {% hint style="info" %} **An important element to understand** is that you need to place yourself in the context of the element in question. If you select a switch, the impacts and dependencies will be different if you select an element linked to the switch. {% endhint %} ## Create an impact analysis *** ### Adding hardware Your equipment must be powered up before you can use the impact analysis. If we go back to our example given above, we'll start from the 1st item, i.e. the router. * Go to **`Assets`** > **`Network devices`** * Select the network hardware you require * In the **`impact analysis`** tab, the hardware you are on will appear * On the right-hand bar, click on * The list of categories appears, choose the one that suits you (here network hardware to link our switch to our router) * Drag and drop the hardware you want. * Do the same with all the hardware you want You'll get a result like this (depending on how you've placed your items) ![alt text](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-76517280c04c5f0bf4a454d79b456ec42b7040aa%2Fanalysis_impact-2.png?alt=media) *** ### Adding links Now that our materials have been placed, we need to add the links in order to check their impact and dependencies (or both). * From the right-hand menu, click on * Your mouse will then appear with a * Hold your mouse over the 1st element, and release the mouse over the element to be linked. * Repeat the operation for all the desired elements ![alt text](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-0d528514dcd34eae59e65a915976882527bf7cf7%2Fanalysis_impact-1.png?alt=media) *** ### Explanation of links As mentioned above, you need to understand the context of the selected element. What we see in the diagram above is that all the links are in red. This means that if the router were to fail, all the following elements would be affected. If we position ourselves on **Rack 1**, the behaviour will not be the same: ![alt text](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-2f190cc953dfea06ca6a988e2f42c07dac0d8901%2Fanalysis_impact-3.png?alt=media) In this example, **from the point of view of Rack 1**, the only hardware that would impact the infrastructure if it were to fail is **SRV-GLPI**. **Rack 1** depends on **Router EDGE-51** and **Switch A3**. They are in blue (dependency) because they would not be impacted if Rack 1 were to experience a problem. ## Dependency and impact on the same hardware We can add a router to our example, which will be linked to the 1st original router: ![alt text](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-b75453b5954130dcf2e4ed764b8e8c9ace032072%2Fanalysis_impact-4.png?alt=media) * To do this, create a relationship in one direction and then in the other using the option seen above. The purple arrows mean that they are dependent on each other and that they would both be affected if one of them were to encounter a problem. They are therefore both dependent and impacted. ## No impact There is one last type of link, those that have no dependency or impact: ![alt text](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-9c8cdbfe77ae70e32db05091c67c7282a1ad4e22%2Fanalysis_impact-5.png?alt=media) The black arrows mean that from the element you are on, there will be no imapct if that element were to fail. In our example, we are on **Rack 1**. This does not communicate with **Rack 2**, so there will be no dependency or impact in the event of a failure. ## Groups Groups can be created using the :fontawesome-regular-object-group: icon in the right-hand menu. Groups allow you to see all the elements that depend on another piece of equipment. You can create a name for the group and choose a background colour. ![alt text](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-3cfae0f782256d64c388a0f775bb59cba49a3e19%2Fanalysis_impact-6.png?alt=media) To delete a group, right-click on it and select delete. This only deletes the group, not the items it contains. ## Save your imapct analysis Remember to save your project with ## Deleting elements You can delete an element using . This deletes the element and the link. ## Download your project You can download your impact analysis using . The download format is PNG. ## Enlarge your analysis Use the icon to make your analysis full screen. You can also use your mouse wheel to zoom in and out. ## Link configuration You can configure certain options using
alt text
*** ### Visibility In visibility, you can choose to show only impacts and/or dependencies. *** ### Colours In the colours tab, you can change the colours of dependencies, impacts and impacts and dependencies. *** ### Maximum depth The maximum depth is the number of elements that can be displayed on your imapct analysis. If you select "infinity", there will be no display limit. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.glpi-project.org/tutorials/inventory/impact_analysis.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.