IANN Monitor Product Manual 6.4
Introduction to the Manual
This Manual serves as a comprehensive guide to understand and utilize the IANN (Intelligent Artificial Neural Network) system effectively. It provides essential information about the system’s purpose, core components, and operational guidance to help users make the most of its capabilities.
What is IANN?
This Manual serves as a comprehensive guide to understand and utilize the IANN (Intelligent Artificial Neural Network) system effectively. It provides essential information about the system’s purpose, core components, and operational guidance to help users make the most of its capabilities.
IANN (Intelligent Artificial Neural Network) is Pragma Edge’s AI-powered unified platform designed to bring intelligence, automation, and predictive analytics into business operations. It combines file tracking, monitoring, and AI-driven insights to ensure end-to-end visibility, operational efficiency, and proactive issue resolution.
IANN plays a key role in driving digital transformation across industries by turning traditional data exchanges into intelligent, insight-driven processes.
IANN is built as a modular system with three primary components:
- FileGPS – Tracks and monitors file transactions across systems for visibility and SLA compliance.
- Monitor – Provides real-time monitoring of processes, system health, and metrics with alerts.
AI – Adds intelligence through predictive analytics, anomaly detection, and GenAI insights.
Who should use this Manual?
This manual is intended for individuals and teams within the organization who are directly or indirectly involved in overseeing, maintaining, and responding to file movement, alert notifications, and AI-based monitoring insights across systems using the IANN platform (FileGPS, Monitor, AI).
The following roles and departments should use this manual:
- Operations & Support Teams
To configure, monitor, and troubleshoot file processing and alert conditions using FileGPS and Monitor modules. - IT & Infrastructure Teams
For setting up system parameters, managing alert configurations, ensuring file delivery timelines, and maintaining alert routing (via dashboard, email, or REST API). - Data Governance & Compliance Officers
To track file movement, adherence to organizational SLAs and identify gaps in data flow or system failures using AI-generated insights. - Integration & Middleware Teams
To manage end-to-end integration scenarios, monitor handoffs between internal systems and external partners, and ensure timely and reliable data exchange. - Business Process Owners
To gain visibility into key entity/file group performance and monitor alert thresholds critical for operational decision-making. - AI/Analytics Teams
To leverage Monitor and AI features in identifying anomalies, predicting failures, and optimizing alert rule configurations based on behavioural trends.
What this Manual Covers?
This manual serves as a unified guide for users of the IANN (Intelligent Automated Network Navigator) platform. It provides detailed, step-by-step instructions and contextual overviews across IANN Monitor
IANN Monitor Application
- Setting up and managing deployment environments (Dev, QA, Prod).
- Creating dashboards for key system and performance metrics.
- Defining thresholds and alert rules.
- Routing alerts to platforms like PagerDuty, Email, XMatters, Teams, Slack, and ServiceNow.
- Creating and managing a wide range of visualizations.
- Managing user access and roles.
Seamlessly switching between monitoring environments.
This manual is designed to equip administrators, analysts, and monitoring teams with the knowledge needed to fully leverage the IANN platform’s capabilities in detecting anomalies, ensuring operational transparency, and maintaining high system reliability across file and transaction landscapes.
IANN Monitor
1. Introduction to IANN Monitor
1.1 What is IANN Monitor?
IANN Monitor is an integrated monitoring and alerting platform designed for IBM Sterling B2B and IBM Maximo environments. It provides real-time visibility into critical application and infrastructure-level metrics, helping organizations detect and respond to issues before they impact business operations.
Key monitoring capabilities include:
- System Health Monitoring
- IBM B2B and IBM Maximo Application Metrics
- Application Logs
- Cloud Logs
IANN Monitor supports both cloud-based and on-premises deployments and is built to improve the efficiency of IBM B2B and IBM Maximo Application platforms by:
- Reducing daily manual health check costs by up to 95%
- Minimizing system downtime
- Enhancing file transfer reliability
- Offering centralized monitoring across the platform
- Serving as a single tool for end-to-end system visibility.
It also provides early problem detection and supports a variety of graphical options to visualize and interpret system data efficiently.
2. IANN Monitor - Key Monitoring Parameters
2.1 Sterling Integration Application
These datapoints are gathered through IANN Monitor’s integration with Sterling Integrator to monitor system activity, performance metrics, and potential anomalies.
2.1.1 Adapter & Mailbox Monitoring
- Adapter Status –IANN Monitor tracks whether each adapter is currently active or stopped, helping ensure all integrations are running as expected.
- Adapter Uptime –It monitors how long each adapter has been running without interruption, useful for detecting restarts or unexpected failures.
- Mailbox Depth – Shows the number of messages currently queued in each mailbox, helping identify processing delays or message backlogs.
- Mailboxes with Unextracted Messages –Identifies mailboxes that contain messages which haven’t been extracted, indicating potential issues in message retrieval.
- No of Messages Extracted Older N Days –Highlights messages that were extracted after remaining in the system for several days, useful for tracking processing delays.
- No of Messages Unextracted Older N Days –Lists messages that are still unextracted even after a set number of days, helping detect stuck or missed messages.
- External Perimeter Status –Monitors the status of perimeter servers to check if they are reachable and responsive, ensuring external communications are intact.
2.1.2. Business Process (BP) Monitoring
- BP Status –Shows the current state of individual or multiple business processes, such as running, halted, or completed.
- Document Processed –Displays the number of documents successfully processed by business processes.
- Long Running BP –Identifies business processes that are taking longer than the expected time thresholds, helping detect bottlenecks.
- Long Running BP Steps –Highlights specific steps within business processes that are unusually long, indicating potential inefficiencies.
- BP Definition Details –Provides configuration and setup information for each business process defined in Sterling Integrator.
- BP Step Metrics –Captures runtime metrics for each step within a business process, useful for performance tuning and analysis.
- BP Execution per Node –Tracks how many business processes are executed on each node in a clustered environment, aiding in load balancing.
- BPs with Large Steps –Detects business processes that have an excessive number of steps, which may indicate overly complex or poorly designed workflows.
- BP Records per Month –Summarizes the number of business processes executed each month to identify usage patterns and trends.
2.1.3. File Processing State Monitoring
- Halted BP Count –Shows the number of business processes that have completely stopped due to errors or manual termination.
- Halting BP Count –Indicates the business processes that are in the process of stopping but haven’t finished halting yet.
- Waiting BP Count –Displays the count of business processes that are idle and waiting for a trigger or event to proceed.
- Waiting on I/O BP Count –Represents business processes that are delayed while waiting for input/output operations to complete.
- Interrupted BP Count –Captures business processes that were unexpectedly stopped or disrupted before completion.
2.1.4. Environment & System Health
- Application Availability Time –Shows the total uptime and availability duration of the application.
- Service Runtime Duration –Displays how long core services have been running without interruption.
- Purge Lock Status –Indicates the current state of system locks that may need purging during maintenance.
- Indexing Details –Provides information about index records used for tracking business process statuses or audits.
- Archive Status –Tracks the status of data that has been archived for long-term storage or compliance.
- Purge Operation Status –Reflects the progress and outcome of purge tasks used to clean up old or unnecessary data.
2.1.5. Schedulers & Threads
- Schedulers Status –Displays the status of all configured schedulers across Sterling Integrator nodes.
- Active Threads –Indicates the number of currently active processing threads.
- Queue Depth –Shows how many threads are waiting in the processing queue.
- JVM Heap Utilization –Reflects the current memory (heap) usage of the Java Virtual Machine.
- Pool Connection Info –Provides details on connection usage including used and available pool connections.
2.1.6. Certificate Monitoring
- Trusted Certificates –Monitors the status and expiration of trusted certificates configured in the system.
- System Certificates –Tracks the validity period and expiration of system-level certificates.
- Certificate Authority (CA) Certificates –Displays details of the Certificate Authority, including trust relationships and expiration.
2.1.7. CM Statistics (Community Manager)
- Application References (CM) – Tracks application references defined in the Community Manager.
- Trading Partner References –Displays references and mappings related to Trading Partners.
- Workflow References –Lists workflows and their associated reference details.
2.2 Maximo Application Monitoring
IANN Monitor tracks Maximo system activity, including user sessions, work orders, asset and inventory data, purchase workflows, automation tasks, custom configurations, reports, and core system properties—offering complete visibility into operational performance and health.
2.2.1. Active Sessions and User Tracking
- User Active Sessions – IANN Monitor tracks currently active user sessions in Maximo.
- Active Sessions – Lists all user sessions being tracked for activity monitoring.
- User Login Tracking – Monitors user logins and session durations.
- Inactive Users – Identifies users who haven’t been active for a configured duration.
- User App Points – Retrieves application points assigned to a user.
- Used App Points – Shows the number of app points consumed by each user.
2.2.2 Work Orders and Maintenance
- Work Order Maintenance Records – Tracks detailed maintenance logs linked to work orders.
- Work Orders – Represents operational or repair orders for assets.
- Open Work Orders – Displays ongoing or pending work orders.
- Closed Work Order Count – Provides the number of work orders that have been closed.
- Completed Work Order Count – Indicates how many work orders have been completed successfully.
2.2.3. Assets and Inventory
- Assets – IANN Monitor manages data and lifecycle of physical and virtual assets.
- Item Master – Lists all items registered in the system.
- Inventory Items – Tracks items available in inventory for operations.
- Locations – Monitors where assets are physically or logically located.
- Dock Links – Maps assets or items to their respective storage or operational areas.
- Asset Score – Evaluates asset reliability and performance through scoring.
2.2.4. Purchase Orders and Invoices
- Purchase Orders and Invoices – Tracks procurement and billing data together.
- Purchase Orders – Lists all items or services procured through formal orders.
- Purchase Requisitions – Monitors internal requests that precede purchase orders.
2.2.5. Automation and Scheduling
- Scheduled Jobs – Displays jobs set for automatic execution.
- Cron Tasks – Tracks periodic background tasks in Maximo.
- Cron Task Parameters – Monitors parameters configured for cron jobs.
- Cron Task History – Provides historical data on cron task execution.
- Enabled Cron Tasks – Lists currently active cron tasks.
- Disabled Cron Tasks – Lists cron tasks that are inactive.
- Automation Scripts – Tracks the activity status of automation scripts.
- Stopped Escalations – Lists escalations that are no longer executing.
- Event Listeners Status – Monitors the operational state of event listeners.
2.2.6. Maximo Customization and User-Defined Configuration
- Custom Objects – IANN Monitor tracks user-defined objects extending Maximo features.
- User-defined Attributes – Monitors additional fields created by users for custom needs.
- Attribute Definitions – Represents standard field definitions used across Maximo.
- Application Metadata Tables – Tracks structure and schema of Maximo applications.
- Application Versions – Maintains records of installed Maximo module versions.
2.2.7. Saved Queries and Reports
- Saved Application Queries – Tracks user-created saved searches or filters.
- BIRT Reports – Monitors usage of BIRT reports for advanced analytics and reporting.
2.2.8. System Configuration and Properties
- System Properties – Tracks global configuration and system-level settings.
- Application Database Tables – Monitors for operational data stored in database tables.
- Application Metadata Tables – Manages metadata that defines schema and design.
- Application Versions – Tracks version history and upgrades to Maximo modules.
2.2.9. Miscellaneous
- Concurrent User Count – Tracks the number of users concurrently authorized.
- License Expiration – Monitors Maximo license expiry dates.
- Event Listener Status – Ensures listeners are running and responding as expected.
- Entitled Application Points – Monitors the tracks the total number of application points used in the IBM Maximo application, based on your organization’s entitlements defined in the IBM license agreement.
2.3 Platform Monitoring
IANN Monitor captures essential system metrics and resource utilization across Linux, Windows, OpenShift, and Kubernetes environments to ensure the health, performance, and availability of infrastructure components
2.3.1. System Stats (Linux & Windows)
- CPU – Monitors the CPU usage on the system.
- RAM – Tracks memory usage over time.
- Disk – Observes disk space and performance.
- Network – Measures incoming and outgoing network traffic.
2.3.2. OpenShift Monitoring & Cluster Monitoring
- Node Metrics – IANN Monitor gathers key metrics from OpenShift nodes, including:
- Master and Worker Node Count – Tracks how many master and worker nodes are present.
- Node Status – Monitors whether each node is in a ready state.
- CPU, RAM, Filesystem Usage – Tracks resource consumption on nodes.
- Network In/Out – Monitors the network traffic per node.
- Pod Metrics – IANN Monitor captures the latest metrics from pods, including:
- Pod Count – Tracks the total number of running pods.
- Pod Status – Monitors the health and status of each pod.
- Restart Count – Observes how many times pods have restarted.
- CPU, RAM, Filesystem Usage – Reports resource usage at the pod level.
- Network In/Out – Tracks incoming and outgoing pod network traffic.
- Persistent Volume Claims – Tracks all persistent volume claims (PVCs) in the cluster.
- Mount Paths – Retrieves and monitors mounted paths on OpenShift nodes.
- Installed Operators – Lists and tracks all operators installed in the cluster.
- Storage Classes – Displays and monitors the available storage classes in OpenShift.
- SSL Certificates – Tracks the status and expiration of SSL certificates in the environment.
2.3.3 Kubernetes Monitoring
- Pod CPU/RAM – Monitors CPU and memory usage of each pod.
- Pod Count – Counts the number of pods running.
- Restart Count – Shows how often pods have restarted.
- Node CPU/RAM – Tracks CPU and memory use at the node level.
- Node Count – Displays total number of Kubernetes nodes.
2.4 Cloud Monitoring
IANN Monitor tracks the availability, usage, and health of resources deployed in cloud environments to ensure smooth operations and early detection of issues.
2.4.1 Azure Monitoring
IANN Monitor collects and analyses data from various Azure services such as virtual machines, databases, disks, VPNs, and network components to provide real-time visibility, performance tracking, and operational insights within the Azure cloud environment.
- Activity Logs – Tracks user and resource-level activities across your Azure environment.
- Database Instances – Monitors active Azure SQL and other database services.
- Disks List – Lists and monitors Azure managed disks, including status and usage.
- VPN Gateways – Displays status of configured VPN connections for secure networking.
- Virtual Machines – Provides visibility into VM configurations, states, and locations.
- Traffic Manager – Monitors the performance and endpoint health of Azure Traffic Manager.
- NetApp Accounts – Tracks Azure NetApp account usage and performance for file storage.
- Network Security Groups (NSGs) – Inspects security rules applied to control network traffic flow.
- Load Balancers – Displays current load balancer setup and monitors traffic distribution.
- Registry Certification – Checks certificate status of Azure Container Registries for secure access.
3. IANN Monitor Application
The IANN Monitor Application is a comprehensive platform that offers graphical visualizations, real-time alerts, and deep insights across infrastructure, application, and integration layers. It streamlines monitoring, analysis, and management through the following key modules:
- Login Page – Secure authentication for user access.
- Landing Page – Overview of system, application, and integration health with quick navigation.
- Dashboard Creation – Allows users to build custom dashboards to visualize selected metrics.
- Dashboard Management – Enables users to manage, edit, or delete existing dashboards.
- Default Dashboard – The Default Dashboard comes preloaded with essential metrics and default panels, giving users a quick overview of system performance and key data points right from the start.
- Access Management – Controls user roles and permission-based access.
- Alerts Page – Displays alerts that are raised across the environment and allows users to pause/resume alerts or mark components under maintenance.
- Notification Channel – Supports routing alerts to different channels such as Email, ServiceNow, XMatters, and PagerDuty.
- Channel Configurations – Lets users configure environment-specific reporting to collaboration platforms like Microsoft Teams or Slack.
- Environment Creation – Allows creation and configuration of multiple environments (e.g., Dev, QA, Prod).
- Weekly Reports –The Weekly Monitoring Report is an automated 7-day summary that highlights system performance, availability, and health across both VM and OpenShift environments. It helps operational teams ensure reliability, detect risks early, and validate infrastructure behavior.
- Environment Switch – Enables switching between environments for focused analysis and monitoring.
3.1 Login:
Use the username and password from the application.yml file for the first login, then click the Login button to access the application.
When you login for the first time, you’ll see a blank landing page like the one below.
3.1.1 Forgot password
The “Forgot Password” feature allows users to securely reset their password if they are unable to remember it. By clicking the “Forgot Password” link, users are directed to a recovery page where they can update their login credentials through a step-by-step verification process.
Steps to Reset Your Password:
1. Enter User ID and Captcha
Begin by entering your User ID and completing the Captcha, which ensures the request is from a legitimate user and helps prevent automated attacks.
2. Receive OTP via Email
Based on the entered User ID, a One-Time Password (OTP) will be sent to the registered email address associated with your account.
3. Reset Password
a. Enter your username in the User ID field.
b. Provide a new password and re-enter it to confirm.
c. Enter the Captcha as shown.
d. Input the OTP received via email and submit the form.
4. Submit and Update Password
Once you click Submit, your password will be updated successfully to the new one.
4. Create and Manage Environment
4.1 Create Environment:
To create a new environment in IANN Monitor, the following fields are mandatory and must be filled out:
1. Environment
2. Environment Name
3. Index Prefix
Make sure to use a valid Index Prefix as defined in the config.ini file or Kubernetes ConfigMap.
Click the +Create button to add the new environment.
Note: The Environment Name field does not support special characters. Only alphanumeric values are allowed.
4.2 Manage Environment:
In the “Manage Environment” section, you will see a list of environments with fields “Name,” “Prefix,” and “Action.” Within the “Action” column, you can perform actions such as editing or deleting the environment as needed.
5. Environment Switch
When you click on Environment Switch, a list of environments you’ve created will appear in a pop-up window. From here, you can select the desired environment for your current task.
Once an environment is selected, you will be redirected to its landing page.
To access dashboards within the selected environment, click on Manage Dashboard. If no dashboards have been created yet, the Manage Dashboard section will appear empty.
6.Dashboard
To create a new dashboard, click on the Add Dashboard icon as shown in the screenshot.
Enter a title for your dashboard and click Save to complete the creation process.
6.1 Panels:
If you want to create a new panel, click on the Icon mentioned in the screenshot. After that row was added successfully.
Initially, each panel shows three icons:
1. Settings Icon – Allows you to rename the panel title.
2. Delete Icon – Removes the panel entirely.
3. Down Arrow – Expands or minimizes the panel
Once you expand the panel using the down arrow, you’ll see a ‘+’ (Add Graph) icon like in the screenshot below:
Using the Add Graph option, you can add any type of graph based on your requirements.
When you select Add Graph, you will be directed to the Create Graph page as shown below.
6.2 Creating a Graphs in IANN Monitor
To create a graph in IANN Monitor, follow these steps:
- Select Index (Index Name)
Choose the Elasticsearch index that serves as the data source for your graph.
- Choose Graph Type (Graph Type)
Select the type of graph you want to create:
- Line
- Bar
- Gauge
- Text
- Table
- Enter Graph Name
Provide a user-defined name for your graph to help identify it easily.
- Select Units (Applicable only for Line Graphs)
Choose how you want the values to be displayed:
- Numeric
- Percentage
- Bytes
6.2.1 Create Queries
Each query consists of several key steps:
1. Select Metric Type
Choose the aggregation method for your data:
a. Average: Calculates the mean of numeric values for each time bucket.
b. Sum: Computes the total of all numeric values within each time bucket.
c. Count: Returns the number of records/documents within each time bucket.
Note: Query creation is not applicable for Table Graphs.
Time-Based Data Bucketing:
To create meaningful time-series graphs, data is grouped into dynamic time buckets using a Date Histogram Aggregation. The bucket size adjusts automatically based on the selected time range to maintain chart readability and performance.
This bucketing applies to Average, Sum, and Count aggregations.
Time Range | Bucket Interval |
≤ 12 hours | 1 minute / 5 minutes |
1 day | 5 minutes |
< 3 days | 10 minutes |
< 5 days | 25 minutes |
< 7 days | 70 minutes |
≤ 30 days | 10 hours |
≤ 60 days | 13 hours |
≤ 180 days | 15 hours |
≤ 365 days | 1 day |
> 365 days | 2 days |
This logic ensures that charts remain readable and performant regardless of the data volume or time span.
2. Choose Query Type
Three query types are supported:
3. Field-Only Query
a. Input: Field name
b. How it works: Data is fetched directly from the specified field and visualized as per the selected graph type.
4. Filtered Query
a. Input: Filter field and filter value
b. How it works: Data is filtered based on the provided condition and then visualized.
5. GroupBy Query
a. Input: Enable Group By checkbox and specify the field to group by
b. How it works: Unique values from the Group By field are used to create multiple
visual elements (e.g., lines, bars, gauges).
Note: When Group By is enabled, only one query can be created. Multiple queries are supported only when Group By is not used.
6. Set Alias Name
Provide an alias for your query. This name will be displayed on the graph legend, making it easier to identify the data.
7. Save the Graph
Once all the details are configured, click Save Graph to generate and add the graph to your dashboard.
6.3 Understanding Each Graph Type
6.3.1. Graph Type: Line
A line graph displays data trends over time. It’s ideal for visualizing metrics like CPU usage, memory consumption, or traffic patterns.
When to Use:
1. To monitor continuous data over time
2. To compare multiple data lines
3. To highlight fluctuations and trends
Supports:
1. Units (Numeric, Percentage, Bytes)
Defines how the data values are formatted and displayed in the graph.
(e.g., CPU usage as Percentage, file size in Bytes, or raw numbers as Numeric)
2. Metrics (Average, Sum, Count)
Specifies the aggregation method applied to the selected field.
(e.g., calculate average CPU usage, total disk I/O, or count of events)
3. Multiple Queries
Allows adding more than one query to compare or overlay different data points in a single graph.
(Useful for showing different fields or filters side-by-side)
4. Group By
Splits data into multiple visual elements based on the unique values of a selected field.
(e.g., CPU usage per server, requests per endpoint, etc.)
5. Tooltip (Hover to see detailed values)
Displays precise data values when you hover over graph elements.
(Helps users view exact numbers without cluttering the graph)
6. Legends with Filtering and Sorting
a. Sorting Options: Legends can now be sorted in three modes:
i. Ascending: Sort legend items from lowest to highest value.
ii. Descending: Sort legend items from highest to lowest value.
iii. Normal: Display legend items in their original order (default).
b. Quick Filtering:
You can filter by legend value to instantly locate and highlight a specific data point, helping you analyze exact values more quickly
6.3.2. Graph Type: Gauge
Gauge graphs are used to represent a single metric value against a fixed scale. They are ideal for showing real-time status or capacity usage, such as CPU load or active connections.
When to Use:
1. To show current system status
2. To visualize values in a fixed range (e.g., 0–100%)
Behaviour:
1. For values greater than 0, the status is shown as “Running”
2. For value 0, the status is displayed as “Stopped”
Supports:
1. Metrics (Average, Sum, Count)
Specifies the aggregation method applied to the selected field.
(e.g., calculate average CPU usage, total disk I/O, or count of events)
2. Multiple Queries
Allows adding more than one query to compare or overlay different data points in a single graph.
(Useful for showing different fields or filters side-by-side)
3. Group By
Splits data into multiple visual elements based on the unique values of a selected field.
(e.g., CPU usage per server, requests per endpoint, etc.)
6.3.3. Graph Type: Bar
Bar graphs display categorical data using rectangular bars. Each bar represents a different data value or category.
When to Use:
1. To compare values across different categories
2. To use with Group By for multiple bars
Supports:
1. Metrics (Average, Sum, Count)
2. Group By
3. Multiple Queries (if Group By is not enabled)
4. Legends with Filtering and Sorting
a. Sorting Options: Legends can now be sorted in three modes:
i. Ascending: Sort legend items from lowest to highest value.
ii. Descending: Sort legend items from highest to lowest value.
iii. Normal: Display legend items in their original order (default).
b. Quick Filtering:
You can filter by legend value to instantly locate and highlight a specific data point, helping you analyze exact values more quickly.
6.3.4. Graph Type: Text
Text graphs show a single metric as plain text. Useful for showing key values (like today’s count, latest status, or totals).
When to Use:
1. To display a summary or headline metric
2. For dashboards with limited space
Supports:
1. Metrics (Average, Sum, Count)
2. Group By
3. Multiple Queries (if Group By is not enabled)
6.3.5. Graph Type: Table
The Table graph type presents data in a tabular format, ideal for users who prefer
structured and detailed information to display.
When to Use:
Use the Table graph when you want to view data in a structured, row-column format that supports detailed analysis, sorting, filtering, and keyword-based searches.
Ideal for log records, alerts, and data comparisons.
Supports:
1. Tabular Representation: Displays data in a clean, structured table format.
2. Table Search:
Search Using
Column Name: To filter the data in table for a particular column use column Name:
keyword to search in Filter By field in query and update the graph.
Search Using keyword: Directly enter the keyword you want to search for in the “Filter By ” field. It is useful to search all the column values in the table.
Note: Search with special characters other than underscore won’t be possible.
3. Sorting:
Each column includes up/down arrow icons to sort data in ascending or descending order.
4. Pagination:
Enables smooth navigation across large datasets when editing.
5. Enable & Disable Columns:
In the Table Graphs section, you can choose which fields you want to show or hide using the Modify Headers option.
If you only want to display certain fields in the table:
a. Click on Modify Headers.
b. A list of available fields will appear with checkboxes.
c. Uncheck the fields you don’t want to display.
d. Click Save.
e. The table will now only show the fields that are checked.
Example:
In the screenshot below, the fields Certificate Expiry Date and Created Date are unchecked. So, these fields won’t appear in the table — only the remaining checked fields like TIMESTAMP, Days, and Name will be visible.
6. Modify Table Column Position:
In the Table Graphs section, you can rearrange the order of fields using drag and drop functionality in the Modify Headers section.
If you want to change the position of a field:
a. Click on the Modify Headers button.
b. Hover your mouse over the field name you want to move.
c. Click and drag it to the position where you’d like it to appear in the table.
d. Once you’re happy with the new order, click Save.
Example:
In the screenshot below, the Name field has been moved to the second position and Days is placed third — just by dragging and dropping them into the desired order.
7. Dynamic Field Names:
For table graphs, users have the option to customize or rename field headers according to their preferences.
To do this:
a. Go to the Edit page of the Table Graph.
b. You’ll find an option called Modify Headers (as shown in the screenshot below).
Once you click on Modify Headers,
a list of all the current field names in the table will appear (see screenshot below).
To change a field name, simply click on it, type the new name, and then click Save.
8. The updated field name will now be displayed in the table.
Example:
In the screenshot below, the Name field has been moved to the second position and Days is placed third — just by dragging and dropping them into the desired order.
In Panel view, the timestamp position is fixed at the beginning and cannot be changed, ensuring consistent visualization across all panels.
6.4 Graph Resize, Drag and Drop
Graph Resize:
To resize the graph component, use the resize handle located at the bottom-right corner of the panel (as highlighted in the image). The handle is represented by a wrench-like icon. Simply click and drag this icon to adjust the graph’s dimensions according to your preference.
Drag and Drop:
Hover near the top area of the graph to reveal the drag handle. hold to move the graph and rearrange its position on the dashboard Panels.
Note: Drag and drop is only possible within the panel.
7. Manage Dashboard
Manage dashboard is used to view the created dashboards and its graphs.
7.1 Calendar Date Selection:
Located at the upper right side of the interface, the calendar feature allows users to retrieve specific data by selecting a date. This is particularly useful for accessing historical data that occurred on a specific day. Users can click on a date within the calendar to choose their desired date, and the system will retrieve data related to that selected date.
7.2 Auto Refresh:
The auto-refresh functionality is a convenient feature that automatically updates or refreshes the displayed data at regular intervals. Users have the option to turn this feature on or off based on their preferences.
Auto Refresh Off:
Users can disable auto-refresh if they prefer to manually refresh the data or if they want to freeze the data at a specific point for analysis.
Theme Options: We provide both dark and light themes for the interface, with the default theme set to dark. This means that when you initially access the application, it will be in dark mode by default. However, you have the flexibility to switch to the light theme if you prefer a different visual style.
A toggle button allows users to switch between light and dark themes for a more personalized viewing experience.
Dark Theme:
Light Theme:
7.3 Download CSV:
The IANN Monitor application includes a CSV download feature that allows users to export data displayed in graphs for a specified time interval selected in the calendar.
Check out the information below on downloading CSV files:
1. Select the graph from which you want to download the CSV data, then click the download button located at the top of the graph.
2. Check your Downloads folder for the file, then open it to view the data.
8. Configuring Alerts and Notification Channel
In this we have two features as shown below.
1. Notification Channel
2. Configuring Alert
8.1 Notification Channel:
Used to configure alerts to be delivered to various external systems and communication channels such as PagerDuty, ServiceNow, XMatters, and Email. This ensures timely reporting and incident response across integrated platforms.
When you click on Notification Channel, you will be navigated to a new page that contains two main sections:
- Create Notification Channel
- Manage Notification Channel
8.1.1 Creating a New Notification Channel
To create a new channel:
1. Click on Create Notification Channel.
2. Fill in the following details:
a. Channel Name:
Enter a name for the notification channel you are configuring.
b. Channel Type:
Choose the type of channel from the dropdown list. The available types include:
i. Email
ii. ServiceNow (Snow)
iii. XMatters
iv. PagerDuty
Channel Type Configuration Details
1. When Email is selected as the channel type, an additional field for Email Address will appear.
2. Enter the email address to which alerts should be sent.
ServiceNow (Snow)
1. When Snow is selected, the following fields will appear:
a. URL
b. Username
c. Password
d. Severity levels: Critical, Warning, No Data
2. Fill in the ServiceNow integration details and select which severities should be reported.
XMatters
1. When XMatters is selected, the following fields will be displayed:
a. XMatters URL
b. XMatters Username
c. XMatters Password
d. Severity levels: Critical, Warning, No Data
2. Provide the XMatters configuration details and select the alert severities to report.
PagerDuty
1. When PagerDuty is selected, the following fields will appear:
a. Routing Key
b. Severity levels: Critical, Warning, No Data
2. Enter the PagerDuty routing key and select the applicable alert severities.
Additional Settings
1. Set Reminder:
Enable this option to configure a time interval for repeated alert reminders.
2. Default:
Enable this to set the configured channel as the default for specific alert types.
Once all the required details are provided, click the Create button at the bottom-left corner of the screen to save the channel.
8.1.2 Manage Notification Channel
When you click on the Manage Notification Channel, you will get the list of notification channels below.
When you click on Action, it displays Edit and Delete options, which allow you to modify or remove the channel configuration.
8.2 Configuring Alerts:
The Alerts feature enables users to monitor key metrics and receive notifications when thresholds are breached. Users can configure alerts with different severity levels (Critical, Warning, No Data, etc.), set reminder intervals, and route alerts to various channels like Email, PagerDuty, ServiceNow, or XMatters.
Each graph can have multiple alerts, but only the top three are displayed by default. Alerts can be paused, resumed, or edited as needed. Advanced options like Group By Alerts and Dynamic Alerts offer more flexibility and clarity.
This feature ensures timely awareness of system issues, helping teams act quickly and efficiently.
To create or modify alerts on the Graph page:
- Navigate to the Alerts tab in graphs inside panels.
- Fill in the required information:
- Alert Name
- Query to which alert to be configured
- Evaluation Frequency (in minutes)
- Alert Category – either Critical or Warning
- Notification Channel – where alerts should be sent
- Custom Message (optional)
Note: Although you can configure multiple alerts, only the top three alerts are visually represented on the graph. To view all configured alerts, click on the Edit option. If a decimal number is used in alert configuration, it will be interpreted as a whole number.
8.2.1 Alert Types
The system categorizes alerts into the following six types:
- Critical Alerts
Triggered when a monitored value crosses a defined threshold, based on the configured condition:
- isAbove: Alert is triggered if the value exceeds the threshold.
- isBelow: Alert is triggered if the value falls below the threshold.
This allows accurate detection of abnormal spikes or drops for timely intervention.
Sample Email Notification:
- Warning Alerts
These act as early indicators of potential issues. A warning alert is raised when a value falls within a configured range:
- warningFrom: Lower bound of the warning range
- warningTo: Upper bound of the warning range
If the value lies between these bounds, a warning alert is generated—providing time for proactive action.
Sample Email Notification:
- OK State Alerts
Indicates that the configured alert is active but none of its triggering conditions (Critical, Warning, No Data) were met. It confirms that:
- The alert is correctly configured.
- The monitored value is within acceptable limits.
- No Notifications will be raised to this type of alerts.
- No Data Alerts
If the “No Data” checkbox is selected during configuration, an alert will be triggered when no data is received during the evaluation period—highlighting gaps in data availability.
Sample Email Notification:
- Paused Alerts
If the Pause toggle is enabled for an alert, it is temporarily disabled. While paused, the alert notification will not trigger—even if its conditions are met. It can be reactivated using the Resume option.
- Reminder Alerts
Reminder alerts serve as follow-up notifications when an issue remains unresolved. They continuously alert users at configured intervals until the condition is cleared—ensuring visibility and timely action on persistent issues.
8.2.2 Alerts for Group By:
Alerts involving grouping (e.g., by server or node) are raised under the following conditions:
- When the alert’s state changes
- When a standard alert transitions to a Group By alert
- When new key fields are detected in the alert’s current values
Example:
If only node1 is down, one alert is triggered.
Later, if node2 also goes down, an updated alert is raised.
However, no additional alert is triggered for node1, and no resolved email is sent when node2 comes back up.
8.2.3 Dynamic Alerts
Dynamic alerts enable real-time data insertion into alert messages using placeholders. This enhances message clarity and relevance.
To use dynamic alerts:
Insert a variable using the @ symbol followed by the field name in your message.
For example:
Message: CPU utilization is high on the @server
When the alert is triggered, @server will be automatically replaced with the actual server name (e.g., node1), producing:
Message: CPU utilization is high on node1
Note: Ensure that the placeholder matches the exact field name used in the alert context to ensure proper substitution.
9. Alerts Data
The Alerts Data Page provides a centralized view of all system or application alerts. It helps users monitor the health and performance of various components in real time.
Key Features:
1. Alert Summary Bar
Displays the total count of alerts categorized by severity:
a. Critical: Indicates serious issues requiring immediate attention.
b. Warning: Highlights potential issues that may need investigation.
c. Ok: Represents components functioning within acceptable thresholds.
d. No Data: Occurs when data is unavailable or not received.
e. Paused: Alerts that have been temporarily disabled.
2. Tabular View
The table lists detailed information for each alert, including:
a. Alert Name: The name or identifier of the alert.
b. Timestamp: The last time the alert was triggered or evaluated.
c. Status: The current state of the alert (e.g., Critical, Ok).
d. Pause/Resume Control: Allows users to enable or disable individual alerts.
3. Maintenance Mode
A single-click option to pause or resume all alerts at once. When all alerts are paused, no notifications will be sent to configured channels.
4. Filter and Search Options:
Users can:
a. Search for alerts by name or status.
b. Use severity filters to view specific types of alerts.
c. Customize the display by selecting alert categories of interest.
10. Landing Page
The Landing Page provides a comprehensive overview of key system components and health indicators. It offers real-time insights across several critical modules, allowing users to monitor the overall state and performance of the system at a glance. The modules displayed include:
The landing page provides a consolidated view of infrastructure health, application uptime, and active alerts across your environment.
1. Infrastructure Monitoring:
1.1. Common Metrics for VMs and OpenShift:
1.1.1. CPU Usage: Shows current processor usage levels.
1.1.2. RAM Usage: Indicates memory consumption.
1.1.3. Disk Usage: Tracks disk space utilization.
1.1.4. Network Usage: Monitors network traffic and performance.
1.2. Additional for Virtual Machines (VMs):
1.2.1. System Status: Displays the real-time operational status of each VM.
1.3. Additional for OpenShift:
1.3.1. Total Nodes: Displays the total number of nodes in the OpenShift cluster.
1.3.2. Active Nodes: Indicates the number of nodes currently in a healthy and active state.
2. Application Monitoring:
2.1. Sterling Integrator (SI):
2.1.1. SI Uptime: Shows if the SI service is operational.
2.1.2. Adapter Status: Displays the status of configured adapters.
2.2. Maximo Application Suite (MAS):
2.2.1. MAS Uptime: Monitors the availability of the MAS environment.
2.2.2. Application Status: Tracks uptime of individual Maximo applications.
3. Alert Monitoring:
3.1. Alert Summary:
3.1.1. Displays the count of alerts by type (e.g., Critical, Warning, Info).
3.2. Alert List:
3.2.1. Timestamp – When the alert was raised.
3.2.2. Alert Status – Current state (e.g., Active, Resolved).
3.2.3. Alert Name – Description or identifier of the alert.
3.2.4. State – Indicates whether the alert is Paused or Resumed.
10.1 Landing Page for VM:
10.1.1 System Status
Displays the current health status of the overall system as a percentage, indicating whether it is operating smoothly or experiencing issues.
10.1.2 RAM
Displays the current memory utilization of the system as a percentage, providing insights into how much RAM is being consumed.
10.1.3 CPU
Shows the current processor usage as a percentage, helping to monitor system performance and detect potential load or bottlenecks.
10.1.4 App Availability
Indicates the number of continuous days the Sterling Integrator (SI) application has been running without interruption, reflecting overall application uptime.
10.1.5 Alerts Overview
1. Visualizes all system alerts using a pie chart.
2. Each color in the chart represents a different alert type.
3. Hovering over a segment displays the count of alerts for that type.
10.1.6 Disk
Displays disk usage in the form of bar graphs, showing the used storage capacity of available disks.
10.1.7 Network
1. Network Inbound Traffic: Shows the volume of incoming network traffic, typically measured in bytes/sec.
2. Network Outbound Traffic: Shows the volume of outgoing network traffic, also measured in bytes/sec.
10.1.8 Alerts List
Provides a detailed list of system alerts, including:
1. Alert Name: The name or description of the alert.
2. Timestamp: When the alert was triggered.
3. Status: Indicates the severity or nature of the alert (e.g., Critical, No-Data).
4. Resume/Pause: Allows administrators to resume or pause alert tracking as needed.
10.1.9 Adapter Status
1. Adapter Name: Displays the name or identifier of the adapter.
2. Status: Shows whether the adapter is Connected or Disconnected.
10.2 Landing Page for OpenShift:
The Landing Page provides a real-time overview of critical system metrics through separate, focused modules. Each module highlights a specific aspect of the system’s operational status.
10.2.1 Node Health
Displays the overall health of the system as a percentage, helping identify if the node is performing optimally or facing any issues.
10.2.2 RAM Usage
Shows the current memory utilization as a percentage, offering insights into how much RAM is actively being consumed.
10.2.3 CPU Usage
Displays the current processor usage as a percentage, helping monitor system load and detect potential performance bottlenecks.
10.2.4 App Availability
Indicates the number of continuous days the Sterling Integrator (SI) application has been running without interruption, providing a measure of system uptime and stability.
Provides an overall health indicator or status of the system, indicating whether it is running smoothly or if there are issues.
10.2.6 Alerts Overview
1. Alerts are visualized using a pie chart, with each color representing a different type of alert.
2. Hovering a segment displays the count of alerts associated with that type.
10.2.7 Disk Status Module
Displays disk usage using bar graphs, representing the used storage space of each disk relative to its total capacity.
10.2.8 Network Status Module
1. Network Inbound Traffic: Shows the volume of incoming network traffic, typically measured in bytes/sec or bits/sec.
2. Network Outbound Traffic: Shows the volume of outgoing network traffic in similar units.
10.2.9 Alerts List Module
This module provides a detailed, tabular view of all active alerts:
1. Alert Name: Displays the name or description of the issue.
2. Timestamp: Indicates the exact time and date the alert was triggered.
3. Status: Shows the current status of the alert (e.g., Critical, No-Data).
4. Resume/Pause: Allows administrators to resume or pause specific alerts as needed.
10.2.10 Adapter Status Module
1. Adapter Name: Shows the name or identifier of each adapter.
2. Status: Indicates the current status of the adapter (e.g., Connected, Disconnected).
11. Default Dashboard
The Default Dashboard is a ready-to-use view that displays key system metrics and performance indicators. It includes essential panels to help users quickly monitor system health and performance without any manual setup.
When you click on default dashboard you will get a popup as displayed below.
Need to provide the Dashboard name and select the Notification channel name to which the graphs are to be configured (We can select single or multiple notification channel names) and after clicking ‘create’ the default dashboard is created (takes at least 1min to create).
11.1 Default Dashboard for Sterling Integrator:
The Default Dashboard for Sterling Integrator includes the following pre-configured panels and graphs, providing a comprehensive overview of system activity and performance.
11.1.1. SDE
Application Status:
System status
contains the App Availability graph
App Availability: It represents the Number of days from when the SI application is up and running.
11.1.2. SI Metrics:
Metrics consists of SI Metrics, SSP CM Metrics, SSP PS NODE3 Metrics and SSP PS NODE1 Metrics. In this panels contains CPU, RAM, NETWOEK, DISK UTILIZATION data in form of graphs.
11.1.3. Perimeter Server Status:
It will show perimeter server status in gauge graphs.
This report group has the following data points
Purge Count: Purge cleans up the business process data once it completes its life span.
Archive Count: Purge cleanup the business process data once it completes its life span.
Index Count: It represents the count of index which sets all completed or terminated business process data to be ready for archiving or purging.
DB Usage: It represents the overall database size utilized by the SI table space.
It represents a collection of open and connections with the database in the SI.
This report group has the following data points
Halted Count: It shows the number of Business processes which are halted.
Halting Count: It shows the count of business process state between active and halted state.
Waiting Count: It shows the number of Business processes waiting for actions to be completed before continuing to run.
Waiting on IO Count: It shows the number of Business processes waiting for required input or output and will resume after receiving input or sending output.
Interrupted Count: It shows the count of Business processes which are interrupted by manual or automatic action.
The status of all adapters which are active and inactive for all the different protocols of Sterling integrator.
11.1.8. Schedulers:
This reports Schedulers status.
11.1.9. Business Process Reports:
It shows the details of the Business Process.
11.1.10. Queue Depth:
It shows the count of Maximum numbers of business processes that can be in a queue at a given time.
It shows the size of Heap in the SI.
11.1.12. Community Manager Activity:
Here are the following Activities.
11.1.13. Database Health Check:
11.1.15. Logs:
Logs are generated by Sterling B2B Integrator based on monitoring activity.
Here we track each component’s activities using the logs provided by Sterling integrator
11.2 Default Dashboard for Maximo Application:
The Default Dashboard for Maximo Application includes the following pre-configured panels and graphs, providing a comprehensive overview of system activity and performance.
11.2.1. Maximo Entitled Application Points:
Shows the total number of application points used in the IBM Maximo application, based on your organization’s entitlements defined in the IBM license agreement.
11.2.2. MAS Application Status:
Shows the application status of MAS.
11.2.3. Node Count and Pod Count:
It shows the overall Node count and pod count.
11.2.4. Master Node Status and Metrics:
It displays Master Node status and Master Node metrics which include CPU,RAM,Disk and Network Usage.
11.2.5. Worker Node Status and Metrics:
It displays Worker Node status and Worker Node metrics which include CPU,RAM,Disk and Network Usage.
Pod status and metrics monitoring within the given namespace, metrics include CPU,RAM,Disk and Network Usage.
11.2.7. Database Health Check:
It displays Database Health Metrics Data.
11.2.8. Asset Health:
It displays Asset Health including Asset Name and its score.
It displays Active User Sessions within MAS Application.
11.2.10. External Integration Logs:
It displays Synchronous Integration Logs.
It displays the details of MAS License Expiration.
It displays user app points with details specific to the entitlement.
11.2.13.
Consumed App Points:
It displays the Consumed App Points of MAS Application.
It displays the Used App Points of MAS Application.
It displays the Runtime Logs of MAS pods.
11.2.16. Auditing Queries:
IANN Monitor tracks auditing queries across key Maximo data points such
as work orders, service requests, assets, purchase orders, locations,
inventory, cron tasks, automation scripts, and custom configurations.
12. Access Management
When you navigate to the Access Management section, you will find two primary options:
- Create User
- Manage Users
12.1 Access Management - User Creation
When you click on “Create User”, the system will prompt you to enter the following mandatory details to create a new user:
1. User ID: A unique identifier assigned to the user.
2. Password: A secure password for the user account.
3. First Name: The user’s first name.
4. Last Name: The user’s last name.
5. Email: A valid email address for communication and account-related notifications.
6. Phone: The user’s contact number.
7. Role: Select a role for the user from the available list.
8. Status: Set the user’s status (e.g., Active, Inactive).
9. Environments: Choose one or more environments from the available options.
12.2 Access Management - User Management:
Managing Users
Step 1: Click on “Manage User” to access the user management interface.
In the Manage User section, you can search for and manage existing users using a variety of filters:
1. User ID: Search by the user’s unique identifier.
2. First Name: Filter users by their first name.
3. Last Name: Filter users by their last name.
4. Email: Search users using their email address.
5. Role: Filter users based on assigned roles (e.g., SUPER_ADMIN, ADMIN, BUSINESS_ADMIN, BUSINESS_USER).
6. Status: Filter users by account status (e.g., Active, Inactive).
For both Role and Status, a list of selectable options will be provided, allowing you to choose the appropriate values when managing users.
Note: If you leave all fields empty and click “Search User”, the system will display all existing users by default.
User Management Actions
Below the list of users, the following management actions are available:
1. Edit: Update user details such as name, email, role, or other relevant information.
2. Delete: Permanently remove the user from the system.
3. Activate: Enable access for an inactive user, restoring their account privileges.
4. Deactivate: Restrict access for an active user by marking their status as inactive.
By using these options, you can effectively control and maintain user accounts according to your organizational needs.
12.3 User Roles:
User roles in the IANN Monitor platform determine the level of access and permissions each user has across various modules and environments. These roles help ensure secure, controlled, and role-specific access based on organizational responsibilities.
12.3.1 SUPER_ADMIN
1. Has unrestricted access to all modules and environments.
2. When a Super Admin creates another Super Admin, the new user will:
a. Access Existing Environments: Gain full access to all environments assigned during their creation.
b. Access Newly Created Environments: Automatically gain access to all environments created after their account is set up, whether added by themselves or by other Super Admins, ensuring uninterrupted administrative access across the platform.
12.3.2 ADMIN
Access Capabilities:
1. Can create Business Admin (BA) and Business User (BU) accounts with access limited to specific assigned environments.
2. Access is restricted to only the environments explicitly assigned.
Accessible Modules:
1. Landing Page
2. Access Management
3. Environment Switch
12.3.3 BUSINESS_ADMIN
Access Capabilities:
1. Can perform edit and delete actions within their assigned environments.
2. Access is limited to those specific environments.
Accessible Modules:
1. Landing Page
2. Create Dashboard
3. Manage Dashboard
4. Alerts Data (includes Alerts Page and Notification Channel)
5. Environment Switch
12.3.4 BUSINESS_USER
Access Capabilities:
1. Has read-only access within assigned environments.
2. Access is limited to assigned environments and does not include:
a. Maintenance Options
b. Pause & Play functionality for Alerts
Accessible Modules:
1. Landing Page
2. Manage Dashboard
3. Alerts Data (Alerts Page only)
4. Environment Switch
13. Channel Configuration
The Channel Configuration feature allows you to define which Teams, or Slack channels receive environment-specific alerts.
- The overall health status of an environment is sent to the configured non-critical alert
- Critical alerts are directed to the configured critical alert
This configuration ensures that both critical and non-critical alerts are routed to the appropriate channels for timely visibility and action.
13.1 Steps to Configure a Channel
Step 1: Navigate to the Channel Configuration page within the IANN Monitor UI.
Step 2: Open the Channel Configuration interface.
Step 3: Select the Application Type – either Teams or Slack.
Step 4: Choose the Channel Type based on your requirement:
1. Critical – Sends critical alerts for the environment.
2. Non-Critical – Sends overall environment health status.
Step 5: Configure the Frequency by setting the interval (in minutes or hours) for sending notifications.
Step 6: Provide the appropriate destination based on the selected Application Type:
1. For Teams, enter the Teams Channel Email ID.
2. For Slack, enter the Webhook URL.
Step 7: Click Create to save the configured channel.
Note: For instructions on obtaining the email address for Microsoft Teams and the webhook URL for Slack, please refer to Section 14 of this Manual.
13.2 Viewing and Managing Channel Configurations.
Step 1: Click on Manage Channel Configuration to view the list of existing channel configurations.
Step 2: In the Actions column,
1. Click the Edit icon to modify the configuration.
2. Click the Delete icon to delete a configuration from this section.
14. Dashboard Backup for Seamless Environment Management
Managing dashboards across multiple environments is simplified with the Dashboard Backup feature. Rather than recreating dashboards, panels, graphs, queries, and alerts manually, you can now export an existing dashboard and import it into another environment with ease.
Please follow the steps below to Back Up a Dashboard
Step 1: Go to the Manage Dashboard section.
Step 2: Hover over the dashboard you want to back up.
Step 3: Click the Download icon (as shown in the screenshot below).
Your dashboard file will be downloaded automatically to your system’s Downloads folder.
Please follow the steps below to upload the Dashboard to a different Environment.
Step 1: Switch to the environment where you want to upload the dashboard.
Step 2: Go to the Manage Dashboard section.
Step 3: Click on the Upload Dashboard button (see screenshot below).
Step 4: In the file selector popup, choose the previously downloaded dashboard file.
Step 5: Click Upload.
That’s it! The dashboard will now be available in the selected environment and will display environment-specific data.
Note: You cannot upload a dashboard to the same environment from which it was exported. Doing so will overwrite the existing dashboard without creating a new one.
15. Setting Up Teams and Slack Integrations (Email & Webhook)
15.1 Get Email address for a Teams Channel:
Step 1: In the Microsoft Teams channel that you want to send the email to, click on the three dots in the top right-hand corner and select the “Get Email Address” option from the drop-down menu.
Step 2: In the panel that pops up, click the “Copy” button to save the address to your clipboard.
Note: This feature needs to be turned on by your IT admin. Also, sending email to a channel isn’t available if you’re using Teams as part of a Office 365 Government plan.
15.2 Getting Webhook URL for Slack Channel:
Step 1: head over to https://api.slack.com/app, your Slack apps dashboard. It will look something like this:
Step 2: Click on “Create an App”
Step 3: Select “From scratch.” In the next screen, specify a name for your app and click on create.
Step 4: once after creating App, navigate to Incoming Webhooks under features and turn on toggle switch.
Step 5: click on add new webhook to workspace.
Step 6: select to which channel you would like to send notifications and click on allow.
Step 7: copy the webhook URL
