Skip to main content
Matrix42 Self-Service Help Center

Getting started with Infrastructure Forensics

What is the Infrastructure Forensics add-on

Infrastructure Forensics, available on our Matrix42 Extension Gallery, is the solution package to federate data from Matrix42 FireScope SDDM into Matrix42 Enterprise Service Management (ESM).

Please make sure that the service bus (Azure, RabbitMQ) is already available prior to proceeding to the outlined steps.

This guide is meant to provide the best practice on federation of multiple NICs/IPs from Matrix42 FireScope SDDM to Matrix42 Enterprise Service Management.

The configuration steps are intended for environments which are using serial numbers of CIs as identification criteria.

Follow the sequence below to achieve a consistent federation, but keep in mind that these steps are to be taken after Matrix42 FireScope SDDM discovery has been executed.

  1. Set up Matrix42 Enterprise Service Management (ESM) by:
  • Installing the Infrastructure Forensics extension;
  • Configuring the Enterprise Service Bus;
  • Configuring the  Enterprise Service Bus matching rules.
  1. Set up Matrix42 FireScope Secure Discovery and Dependency Mapping (SDDM) by:
  • Creating the discovery rule and logical group for CIs with serial numbers;
  • Configuring the integration.

Prerequisites

A pre-installed environment hosting Matrix42 Enterprise Service Management (ESM) with a supported version needs to be available. Same applies to Matrix42 FireScope SDDM with either an Account (cloud) or on-premise installation.
In addition, an already configured Service Bus which is either Azure Service Bus or RabbitMQ needs to exist including topic and subscriptions.

Setting up Matrix42 Enterprise Service Management

This section covers the necessary configuration to be made within Matrix42 Enterprise Service Management (ESM).

Installing the Infrastructure Forensics extension

To install the Infrastructure Forensics extension, log in to ESM and navigate to the Administration application. Click the Extension Gallery navigation item to access the Matrix42 Extension Gallery.

Once in the Matrix42 Extension Gallery, look for Infrastructure Forensics and install the application including all requirements. You will be redirected back to ESM once the installation of all packages is complete.

Configuring the Enterprise Service Bus

The Matrix42 Enterprise Service Bus (ESB) needs to be set up in the Administration application under Integration > Enterprise Service Bus > Settings.

ServiceBusConfig.png

For details on the configuration, please refer to this article.

To troubleshoot service bus communication, follow the instructions provided in the Service Bus VII: Message Validation article.

Configuring the Enterprise Service Bus matching rules

To ensure correct handling of federated CIs, matching rules need to be adjusted and a new one should be created. To edit the matching rules, go to Integration > Enterprise Service Bus > Matching Rules in the Administration application.

For more information on Enterprise Service Bus matching rules, please refer to Matching rules for Service Bus integration.

Adjusting the SPSComputerType matching rule

First, the sequence of the SPSComputerType rule needs to be adjusted so that the SystemSerialNumber attribute is used with a higher priority than SDDMConfigurationItemID.

ComputerMatchRule.png

Adding the SPSComputerClassNetworkCard rule

To be able to consolidate NICs, create a new matching rule for the SPSComputerClassNetworkCard data definition with the following input values:

  1. Type: Data Definition.
  2. Schema: SPSComputerClassNetworkCard.
  3. Matching Keys:
  • First key with Priority 10, Name MAC and Expression MACAddress.
  • Second key with Priority 20, Name IP and Expression IPAddress.

NetworkCardMatchingRule.png 

Troubleshooting

If CIs are sent to the service bus, but not created within Matrix42 Enterprise Service Management, it might be due to missing matching rules.

This will be indicated with an error message in HostCommon.log located under <installationPath>\Matrix42\Matrix42 Workplace Management\Logs\ and might look similar to the following extract of a missing matching rule for SPSPtinterType:
2022-03-02 12:06:00,493 ERROR 47 HostCommon (null) (null) (null)  (null) 11.0.0.3327   - M42.BaseLogger;MessageReceiver.MessageExceptionHandler: Message Type: SPSPrinterType
MQAdapterMatchingInfo doesn't contain entry for 'spsprintertype'
   at Matrix42.EnterpriseServiceBus.BizLogic.Services.ESBCommonReceiver.MessageHandler(JsonMessage message)
   at Matrix42.ServiceBus.Subscriber.<>c__DisplayClass31_0`1.<<CreateReceiver>g__receiver|0>d.MoveNext(

Setting up Matrix42 FireScope Secure Discovery and Dependency Mapping

This section covers the necessary configuration to be made within Matrix42 FireScope Secure Discovery and Dependency Mapping (SDDM).

Creating the discovery rule and logical group for CIs with serial numbers

To prevent CIs without serial numbers from being federated (which would result in duplicate CIs), a new discovery rule needs to be created and linked to a logical group.

  1. Navigate to Configuration > Discovery Jobs > Rules and click the add button to create a new rule.

FSCreateNewRule.png

  1. Provide a name and add the filter criteria to filter records by Serial Number with the Is Not Empty value.

FSNewRuleFilter.png

  1. Configure an action to add filtered records to a new logical group by selecting the Add to new Logical Group action and providing a name for the group.

FSNewRuleAction.png

Once saved the created logical group can be added to the CI selection within the federation settings. 

Configuring the integration

After logging in to your account in Matrix42 FireScope SDDM, navigate to Integration Manager, in the left-hand menu select CMDB Federation Matrix42, and start the configuration with clicking Connect.

FSIntergationOptions.png

Connection

The first step is setting up the connection to the Service Bus.

Make sure to enter all details according to Matrix42 CMDB Federation Connection Setup.

FSConnectionToServiceBus.png

Outbound to Matrix42

The second step of the configuration is the definition of CIs to be federated to Matrix42 ESM. Specify the settings under Outbound to Matrix42.

Most important settings during configuration are:

  • Configuration Item Selection;
  • Preview & Send Outbound Job.
  1. The Configuration Item Selection allows to control which CIs will be included in the federation. They can be either defined manually or by using the dynamic selection based on logical groups.

FSOutboundToMatrix.png

Both logical groups and individual selections are considered during the federation.

  1. The Preview & Send Outbound Job option is used for getting a preview of CIs prior to federating them.

To federate, execute the Export to CMDB action and acknowledge the displayed warning.

FSExportToCMDB.png

For step-by-step guide on filling in outbound settings, please refer to Matrix42 CMDB Outbound Configuration Item Federation.

  • Was this article helpful?