Troubleshoot Topologies

If you fail to delete a topology or cannot make a topology inactive:

If you receive a 413 error when trying to add a large number of nodes or links to a topology:

If you receive a 400 "bad request" error when attempting to create, retrieve, modify or delete nodes or links for a topology:

The Topologies API and the Graph Topology Moobot module do not contain identical functionality. Refer to the Graph Topology topic for functionality that may not be available in the Topologies API, for example distance methods.

If the Topology loader utility fails to run, check your .csv file as follows:

See Load a Topology for more information on the utility.

If you've created a topology but you can't use it to filter a Recipe, check that the topology is active. You can update its active status using the /topologies endpoint.

Note that cloned topologies are set to inactive. Activate a cloned topology when you want to use it to filter a Recipe.

File-based Cookbook Recipes can no longer cluster on topology. You may see an error similar to the following in the Moogfarmd log file:

“File-based recipe with name [{MyRecipe}] contains topology filter configuration - this is not supported. Topology configuration for this recipe will be ignored.”

To cluster on topology, create a replacement Recipe in the UI with a topology filter.

See Configure Logging for more information on log Moogfarmd files.Configure Logging

If your alerts are failing to cluster by topology as configured in your Recipe, check that your Recipe alert matching attribute is an event field.

You can also check the contents of a custom info field for an alert you expect to be clustered, and ensure that your Recipe is correctly configured to include the data.

If you create a large topology with thousands of links, the Graph Analyser process starts to calculate Vertex Entropy when it next runs as part of Housekeeper (every 30 seconds).

If Moogsoft Onprem is processing events and updating the topology simultaneously, you may temporarily see unexpected results. Values will be correct once processing completes.

As a workaround, you can use the clone and replace endpoints in the Topologies API to clone an active topology, make changes to the inactive clone, and then replace the active topology with the updated version. See Create and Manage Topologies for more information.

If Vertex Entropy values are not updating, check that the process is turned on. In the Moogsoft Onprem UI, go to Settings > Vertex Entropy. This process is enabled by default.

If a Situation was created by a Recipe using a topology filter, the topology tab is active in the Situation Room. If the Situation was created in any other way, for example Tempus, manual merge, or a Recipe without a topology filter, the topology tab is disabled.

If an alert in a Situation is also in another Situation for a different topology (that is, it has been clustered by another Recipe using a different topology), both topologies are shown as impacted. Select another topology from the drop-down list to view it.

Manually created alerts are not added to topologies by design.

If you configured a topology in a previous Moogsoft Onprem version the topology no longer exists once you upgrade to v8.0. You can recreate a topology using the Topologies API endpoints. You can also use the Topology Loader utility to load a large topology from a .csv file.

Archived Situations in the historic database do not retain topological data.