# Add Business Service
To create a new Business Service, follow the instructions below:
* From the left-side menu, click on the Business Service module.
* Click the **Add** button at the screen's top-right corner to open the **Add/Edit Business Service Configuration** page.
* On the configuration editor screen, you’ll find visual design tools, including **Add Node**, **Add Edge**, **Add Text**, and **Add Line**, which allow you to construct and customize the business service layout.
These elements allow you to build, label, and connect the service components as per your business logic.
* Enter a **Title** for your business service at the top of the canvas. This will be the name displayed in the service list and throughout the platform.
Use the design tools to start building your service structure:
## Add Node
Each **node** represents a key component of your service architecture, such as a server, application, database, or port, that you want to monitor. Nodes are the building blocks of your business service layout and reflect how elements are connected and dependent on each other.
When creating a Business Service, you are essentially mapping your service topology. This allows you to visualize how components interact (e.g., upstream/downstream relationships) and track each device or process's real-time status.
Clicking **Add Node** lets you insert these monitored components onto the editor canvas. Once added, each node can be configured with specific parameters such as the device type, polling mode, IP address, and the nature of the check (e.g., CPU, process, disk, TCP).
Also, the status of each node is individually monitored, which collectively determines the health and availability of the overall business service.
When adding a node to a Business Service, the pop-up window contains **three sections**:
### **Node Configuration**
This section defines **what you want to monitor** and **how the data will be collected**. It includes details such as the IP address of the monitored asset, the type of resource (e.g., disk, port, process), and the statistics you wish to track. This is the **core functional setup** for the node.
**Node Configuration | Basic Details**
| **Label** | **Action** | **Description / Example** |
| -------------------- | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **IP Address\*** | Select from the drop-down. | Choose the IP address of the device you want to monitor. Only discovered and onboarded IPs will be listed here. |
| **Resource\*** | Select from the drop-down. | Select the resource type to monitor, such as CPU, Memory, Process, Disk, TCP, etc. |
| **Statistics\*** | Select from the drop-down. | Choose the specific metric/statistics to track based on the selected resource. For example, available stats may include port status or response time if the resource is TCP. |
| **Label Type\*** | Select from the drop-down. | Select the label type to be displayed on the node. This is usually an identifier like a Hostname or an IP address. |
| **Show Label** | Toggle checkbox. | Enable this to display the label on the node in the editor view. |
| **Label Trim Value** | Enter a numeric value (optional). | Specify the number of characters to trim the label if it's too long to display. |
### **HA (High Availability) Configuration**
This section allows you to configure **logical relationships** between multiple nodes in a service group. HA rules define the **impact of node availability** on the overall service status. For example, a service can be marked “Up” if either Node A or Node B is active (OR condition), or only when both are active (AND condition).
**HA Configuration | Basic Details**
| **Label** | **Action** | **Description / Example** |
| -------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Is Enabled** | Toggle checkbox | Enable this to activate HA grouping for this node. |
| **Nodes** | Select from the drop-down | Choose the other node(s) that will be part of the same HA group. |
| **Condition** | Select from the drop-down |
Define how the node group should behave:
OR – Service is Up if any one node is up
AND – Service is Up only if all selected nodes are up
|
| | | |
### **Style Configuration**
This section controls the **node's visual appearance on the editor canvas. You can adjust its size and shape or assign an icon or** image for quick identification.
**Style Configuration | Basic Details**
| **Label** | **Action** | **Description / Example** |
| ---------------- | --------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Size\*** | Click the **(–)** or **(+)** icons to decrease/increase the node size, or manually enter a numeric value. | Choose the size of the node on the canvas. Helps distinguish critical nodes. |
| **Shape** | Select from the drop-down | Choose the visual shape for the node: Dot, Hexagon, Image, Star, Triangle. |
| **Select Image** | Appears if "Image" shape is selected |
Pick an image/icon to represent the node visually.
Options include: Access Controller, Access Point, Battery, Router, Server, etc.
These icons help quickly identify the type of component on the canvas.
|
After making the necessary changes, click **Update** to apply and save the configuration.
When mouse-hovering over a node, the following details can be viewed:
* Host Name
* IP Address
* Make
* Model
* Device Type
* Region
* State
* City
* Location
{% hint style="info" %}
Right-clicking on a node will display options to **Edit or Delete** the selected component.
{% endhint %}
## Add Edge
It allows you to connect two nodes in the service layout visually. These connection edges find the **flow**, **dependency**, or **communication** between service components.
Edges illustrate **upstream/downstream relationships**, **directional dependencies**, or **data flow paths** between systems, applications, or infrastructure components.
Once you click **Add Edge**, you can draw a line from one node to another and configure its visual and directional properties.
**Edge Configuration | Basic Details**
| **Label** | **Action** | **Description / Example** |
| --------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Line Type\*** | Select from the drop-down. |
Defines the style of the connecting line. Available options:
Straight Solid Line: A direct, solid line between two nodes
Smooth Solid Line: A curved, solid line for better visual flow
Straight Dot Line: A dashed (dotted) line in a straight format
Smooth Dot Line: A curved, dashed line (smooth with dots)
|
| **Arrow** | Select from the drop-down. |
Determines the direction of flow between the two nodes. Options include:
No Arrow: Simple connection with no direction
To: One-way arrow pointing from source to target
From: One-way arrow pointing from target to source
From & To: Two-way arrow indicating bidirectional communication
|
| **Edge Width** | Use the **(–)** or **(+)** icons or enter a numeric value manually. |
Adjusts the thickness of the connecting line. Useful for emphasizing key connections or layered paths.
Example: 1 for default thickness, 3 for a bolder line.
|
After making the necessary changes, click **Update** to apply and save the configuration.
{% hint style="info" %}
Right-clicking on an Edge will display options to **Edit or Delete** the selected component.
{% endhint %}
## Add Text
It allows you to insert custom annotations or labels anywhere on the canvas within your Business Service layout. Text elements are beneficial for:
* Identifying the role of a node (e.g., Dev Server, Linux App Server)
* Grouping sections with labels (e.g., Frontend Layer, Database Cluster)
* Adding notes or comments for internal clarity (e.g., Temporary Connection, Failover Path)
These text elements are static and do not impact service logic; they are purely for **visual documentation**.
For example, you might label a node as “Primary Redis Cache – Linux Based” for clarity within a team or during audits.
#### **Text Configuration | Basic Details**
| **Label** | **Action** | **Description / Example** |
| --------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Label** | Enter text in the input box. |
Type the content you want displayed on the canvas.
Example: Dev Server, DR Zone, Linux Node.
|
| **Font Size** | Click **(–)** or **(+)** icons to adjust, or enter a numeric value manually | Sets the size of the text. |
| **Font Family** | Select from the drop-down |
Choose a typeface for the text.
Example: Arial, Courier, or Sans-serif, depending on visual preference or style guide.
|
After making the necessary changes, click **Update** to apply and save the configuration.
{% hint style="info" %}
* **Right-clicking on an edge** will display options to **Edit** or **Delete** the selected connection.
* **Text labels** can be freely moved across the canvas after adding, allowing you to align them with relevant nodes, edges, or groups for better clarity.
{% endhint %}
## Add Line
Draw straight lines between objects for grouping or visual separation. You can drag, position, and connect these elements to map out your service as per its architecture or logical flow.
Its configuration options are identical to those available for an edge.
Once all nodes, edges, and configuration parameters are added, click **Save** to store the Business Service configuration.
---
# 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://docs.infraon.io/infraon-help/infinity-user-guide/business-service/add-business-service.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.