Registering Inventory Manager

The purpose of this functionality is to register and maintain the managers who will be responsible for the occurrences of events captured from the 4biz Inventory.

It allows the user to indicate how much time the Manager will be processed, what configuration items it will manage, the checks that will be applied, and the actions to be automatically taken.

This feature provides a variety of actions, such as including, changing, and deleting the Inventory manager.

💭 Did you know?

The automatic actions are workflows related to the processes to facilitate the resolution of events. The configurations of automatic actions are described further in this document and should be used according to each type of classification of event/configuration item.

Before getting started

To register the Inventory manager, it is necessary to register previously:

4biz Event Monitor connection;

Time;

Occurrence category;

Automatic action; and

4biz Inventory connection.

Procedure

Access the functionality through the main menu Processes > Event Management > Inventory Monitor > Inventory Manager;
Click on the desired tab (Search/Register) and function;

Function	Description
Add	Add Managers to the grids
Save	Save the Managers
Delete	Delete the Manager Edited
Clear	Clear all fields from the Form

Search

Select the filter to search for:

Filter	Description
Name	Name to search
Grid	Grid with the search result

Register

BASIC DATA

Complete the Basic Data:

Data Fields
*Name ():** Name of the connection
Connection Inventory: Source of monitoring data coming from external or internal tools

SCHEDULER DATA

Data Fields
Enable/Disable AutoCorrect
Time for event closure

🖊 Note: The autocorrect function is used to archive events and automatically close incidents related to them. The autocorrection depends on the value of the "Time for event closure" field, which means the interval of time to check for new events.

CONFIGURATION TYPE FOR CONFIGURATION ITEMS

Data Fields
Configuration Type(Specific Configuration, General Settings)

CONFIGURATION ITEM PARENT

Data Fields
Configuration item parent
Category of occurrence group
Category of occurrence
Generate occurrences of Up? (Yes/No)
Action for up (Only register event)
Urgency (Low/Medium/High)
Impact (Low/Medium/High)
Generate Down occurrences? (Yes/No)
Action for down (Only register event)
Urgency (Low/Medium/High)
Impact

CONFIGURATION ITEM CHILD OR TYPE OF CONFIGURATION ITEM

Data Fields
Configuration Type ( Configuration item child/Type of Configuration Item)
Configuration item child
Check
Category of occurrence group
Category of occurrence
Generate occurrences of Information? Yes No
Condition for Information
Action for information
Urgency (Low/Medium/High)
Impact (Low/Medium/High)
Generate Warning occurrences? (Yes/No)
Condition for Warning
Action for warning
Urgency (Low/Medium/High)
Impact (Low/Medium/High)
Generate Exception occurrences? (Yes/No)
Condition for Exception
Action for exception
Urgency (Low/Medium/High)
Impact (Low/Medium/High)
Configuration Type: Configuration item child or Type of Configuration Item
Configuration item child
Check
Category of occurrence group
Category of occurrence
Generate occurrences of Information(Yes/No)
Condition for Information
Value
Action for information
Urgency (Low/Medium/High)
Impact (Low/Medium/High)
Generate Warning occurrences? (Yes/No )
Condition for Warning
Value
Action for warning
Urgency (Low/Medium/High)
Impact (Low/Medium/High)
Generate Exception occurrences? (Yes/No)
Condition for Exception
Value
Action for exception
Urgency (Low/Medium/High)
Impact (Low/Medium/ High)

(*) Indicate mandatory field

💭 Did you know?

For each block of information (Configuration Item Parent, Configuration Item Child, or Type of Configuration Item), the following configuration has the same meaning and values: Action (Create the incident, problem, change or send the notification, Impact, and Urgency to define the priority/criticality).

While there is a logged or in execution event, for a service or CI and new incidents occur, the tool will not duplicate the main event. The additional incidents will be linked to the main one. If the main event is archived, a new one will be created.

Complete the fields available in each area;
The completion fields will be changed as the "type of configuration" chosen:
- Specific Configuration: it allows creating specific rules for a single configuration item. Those rules will be applied when the configuration item is being inventoried;
- General Settings: it allows creating rules for all configuration items. Those rules will be applied when the configuration item is being inventoried.
Enter the data necessary and click on "Add";
Click on "Save".