This section outlines the step-by-step procedure for installing and configuring IANN Monitor 6.4. Please follow the instructions carefully to ensure a successful deployment.

Extract Installation Package

Step 1: Right-click on the IANN_Monitor.zip file and select “Extract All…”. Choose a destination folder and click “Extract” to unzip and extract its contents.

Once extracted, you will find two primary archives under the IANN_Monitor directory:

IANN_Monitor/

├── IANN _Monitor_ Server.zip

└── IANN_Monitor_Client.zip

2.1 Upload Server Package and Extract IANN_Monitor_Server.zip

Step 1: Upload IANN_Monitor_Server.zip to the designated Server machine.

     The directory path where IANN_Monitor_Server.zip is uploaded will be referred to as <Install_dir> throughout this documentation.

Step 2: From <Install_dir>, extract the ZIP package using File Explorer:

1.    Right-click on IANN_Monitor_Server.zip → Select “Extract All…”

IANN Monitor Server Directory Structure

After extraction, the IANN_Monitor_Server directory will contain the following files and folders:

IANN_Monitor_Server/

·       IANN_Monitor.jar

·       application.yml

·       config.ini

·       logo.png

·       nodata.png

·       default_dashboard.zip

·       encrypt.zip

·       Heartbeat.zip

·       systemstats.zip

·       teams.zip

·       slack.zip

·       weekly_report.zip

·       alerts.zip

·       send_mail.zip

Purpose of Each Server Component:

The following table provides an overview of key files and packages included in the IANN Monitor installation bundle. Each component serves a specific role in enabling monitoring, alerting, reporting, and automation functionalities.

2.2 Installing and Setting Up Elasticsearch Without Security Certificates (SSL):

This section guides you through the initial setup and configuration of Elasticsearch.

Step 1: Download Elasticsearch from Elasticsearch 8.12.2 | Elastic

Step 2: After downloading, move the Elasticsearch file to the following location:
 <Install_dir>\IANN_Monitor_Server.

Step 3: Extract the Elasticsearch zip package.

Step 4: After extraction, go to the config folder located inside the Elasticsearch directory.

   Step 5: Inside the config folder, open the elasticsearch.yml file using Notepad.

Step 6 :Update the following basic configuration settings in elasticsearch.yml file.

Step 7 : To install Elasticsearch, navigate to the nssm folder and open the win64 directory. In the address bar, type cmd and press Enter to open the Command Prompt in that location.

Step 8 : In the Command Prompt, run the following command:

 
This will open the NSSM service installer window.

Step 9: Click the three dots next to the Application Path field, then browse to the bin folder inside the Elasticsearch 8.12.2 directory and select the elasticsearch file. Then click on Install service. This will install Elasticsearch successfully.

Step 10 : To start Elasticsearch, open Task Manager and go to the Services tab. Find Elasticsearch, right-click on it, and select Start. The service will then show as Running.

Step 11: Try accessing Elasticsearch in your browser.

Step 12: Since we haven’t set up a username and password yet – you can simply ignore authentication.

2.3 Create or Reset the Elasticsearch Username and Password

To Reset the elastic user’s password, follow the steps below.

Step 1: Navigate to the bin directory in the command prompt.

Step 2: Run the password reset tool using the command below.

Step 3: Follow the prompts

Step 4: Set a new password

    You’ll then be prompted to enter a new password twice. Choose a strong, secure password.

Step 5: Verify access via browser

    After successfully resetting the password, you can test the login by opening a browser and navigating to:

http://localhost:9200/

When prompted, enter:

Username: elastic
              Password: <elasticsearch-password>

Step 6: Expected JSON output

Upon successful login, Elasticsearch will respond with JSON similar to the following:

{
 “name” : “<node-name>”,
 “cluster_name” : “<cluster-name>”,
 “cluster_uuid” : “<cluster-uuid>”,
 “version” : {
 “number” : “8.12.2”,
 “build_flavor” : “default”,
 “build_type” : “tar”,
 “build_hash” : “<build-hash>”,
 “build_date” : “2024-02-19T10:04:32.774273190Z”,
 “build_snapshot” : false,
 “lucene_version” : “9.9.2”,
 “minimum_wire_compatibility_version” : “7.17.0”,
 “minimum_index_compatibility_version” : “7.0.0”
 },
 “tagline” : “You Know, for Search”
 }

2.4 Enable SSL/TLS Encryption (Secure Connection) for Elasticsearch:

Now, to enable SSL/TLS encryption for Elasticsearch Secure access.

Step 1: Create a certs folder inside the Elasticsearch config folder of elasticsearch to store all your security certificates.

Step 2: Place your certificate files (.crt, .key, .ca-bundle) into this certs folder.

Step 3: Edit the elasticsearch.yml file, this file is located inside the config of elasticsearch folder.

Step 4: Add the following SSL settings to your elasticsearch.yml file:

Note: Replace /path/to/your/server.key, /path/to/your/server.crt, /path/to/your/ca-bundle.pem with the actual paths to your certificate files.         

Step 5: Restart Elasticsearch to apply the SSL changes.

Step 6: To restart Elasticsearch, Go to the services in task manager and search for Elasticsearch. Right click on Elasticsearch and then restart it, It will come to running state as shown below.

Step 7: Finally Try to access https://localhost:9200/ from browser.  

Username: elastic

Password: <elasticsearch-password>      

2.5 Install and Configure Kibana

This section guides you through the steps to install, configure, and securely connect Kibana to Elasticsearch, including user creation and SSL configuration.

2.5.1 Extract Kibana

Step 1: Download Kibana 8.12.2 from the link below:
 https://artifacts.elastic.co/downloads/kibana/kibana-8.12.2-windows-x86_64.zip

Step 2: After downloading, move the Kibana file to the following location:
 <Install_dir>\IANN_Monitor_Server.

Step 3: Extract the kibana zip package.

2.5.2 Create Kibana User in Elasticsearch

To enable Kibana to communicate with Elasticsearch, create a dedicated user:

Step 1: In Task Manager, locate the running Elasticsearch service, right-click on it, and select Stop.

Step 2: Navigate to elasticsearch folder from the command prompt and run the following command.

/bin/elasticsearch-users useradd kibanauser -p password –r superuser,kibana_admin,kibana_system

The above command It creates a new user named kibanauser and Sets the password to password.

Step 3: Save the generated username and password securely. These credentials will be required in Section 3.5.4 to configure the elasticsearch.username and elasticsearch.password fields within the kibana.yml file.

Step 4: After creating the user, start Elasticsearch again from task manager.

2.5.3 Update Kibana Certificates

To enable secure HTTPS communication:

Step 1: Create the certs folder inside the kibana folder.

Step 2: move the security certificate files (.crt, .key, .ca-bundle) into this certs folder.

2.5.4 Configure kibana.yml

Edit the kibana.yml file to configure Elasticsearch URL, user credentials, and server host.

Step 1: Navigate to the config folder within the Kibana directory. This folder is located inside the extracted contents of the Kibana package.

Step 2: Update the following configuration settings in the kibana.yml file, located inside the config folder.

Note : The elasticsearch.username and elasticsearch.password are generated in section 3.5.2  

Step 3: Update the following configuration:

server.host: “0.0.0.0”

server.port: 5601

elasticsearch.hosts: [“https://<elasticsearch-host>:9200“]

elasticsearch.username: “kibanauser”

elasticsearch.password: “your_kibana_user_password”

Note : The elasticsearch.username and elasticsearch.password are generated in section 3.5.2  

Step 4: Add these lines for server SSL and Elasticsearch SSL verification in kibana.ym file.

server.ssl.enabled: true

server.ssl.certificate: /path/to/your/server.crt

server.ssl.key: /path/to/your/server.key

elasticsearch.ssl.certificateAuthorities: /path/to/your/ca-bundle

elasticsearch.ssl.verificationMode: certificate

And update the following settings.

1.    server.ssl.certificate with the path to the .crt file located at /config/certs inside kibana folder.

2.    server.ssl.key with the path to the .key file in the same directory.

3.    elasticsearch.ssl.certificateAuthorities with the path to the .ca-bundle file also found in this directory.

2.5.5 Start Kibana

Step 1: To install Kibana, navigate back to the nssm folder and open the win64 directory. In the address bar, type cmd and press Enter to open a Command Prompt window at that location and enter the command below.

             nssm install kibana

Step 2: Click on the three dots and select the kibana file located in the bin folder inside the kibana directory. This will install the Kibana service successfully.

To start Kibana, open Task Manager, go to the Services tab, find kibana, right-click on it, and select Start. The service status will change to Running as shown below.

Step 3: Access the kibana URL in browser and enter username and password.

Username: elastic

Password: <provide the Elasticsearch password>

https://localhost:5601/

2.6 IANN Monitor Application Installation

This section explains how to configure the application.yml file for the IANN Monitor application, highlighting the key settings you need to update for proper operation.

2.6.1 Generating Truststore and Keystore using Security Certificates

The IANN Monitor application uses security certificates to:

1.    Enable SSL (so that data sent over the network is encrypted)

2.    Securely connect to Elasticsearch (so it can trust the server it is talking to)

To do this, it needs two important files:

1.    A keystore, which holds the application’s own certificates used to enable SSL.

2.    A truststore, which holds certificates of systems (like Elasticsearch) the application needs to trust.

This section explains how to generate both the keystore and truststore using certificates you have already uploaded to the Elasticsearch folder.

Steps to generate truststore and keystore:

Step 1: Navigate to config/certs inside elasticsearch directory where you have placed your Security certificates from command prompt.

Step 2 :  Generate the truststore

 Run the following command from the certs directory:

What this does:

1.    keytool is a tool that comes with Java for managing certificates.

2.    -import -file <your_certificate>.crt tells it to import your certificate file (replace <your_certificate>.crt with your actual certificate file name).

3.    -keystore truststore.p12 creates a new file called truststore.p12.

4.    -storepass password sets the password to password (you can change this).

5.    -noprompt imports without asking for confirmation.

6.    -storetype pkcs12 specifies the format.

Step 3 : Generate the keystore

A keystore is used by your application to identify itself (hold its own private key and certificate) so it can enable SSL.

Run this command from the same certs directory:

What this does:

1.    openssl pkcs12 -export creates a PKCS12 keystore file.

2.    -out keystore-new.p12 is the output file name.

3.    -inkey ca.key is your private key file.

4.    -in ca.crt is your certificate file.

5.    -passout pass:password sets the keystore password.

6.    -name “your_alias_name” is an alias you give to this entry (replace with something meaningful).

Note:

1.    Keep your truststore.p12 and keystore-new.p12 files safe.

2.    Remember the passwords you set here — you will use them in your application.yml file.

2.6.2 Encrypting Password

The IANN Monitor application does not store sensitive values like passwords in plain text. Instead, it uses an encryption tool, so these values are saved in a secure, encoded format.

For example, instead of writing:

password: mysecretpassword

you’ll store something like:

password: TtjVcSpUPstVC3BYUTbGRrg1+4UKaeZJZd+KUF5mjkA=

This makes it harder for anyone to misuse your passwords even if they get access to your configuration files.

How to encrypt your sensitive values

Step 1: Go to the IANN Monitor installation directory. This is where your encryptInput.zip file is located.

Step 2: Unzip the Encryption Tool

Right-click on the encryptInput.zip file.

Select “Extract All…” from the context menu.

Step 3: Run the encryption tool

Navigate to the IANN Monitor Server folder from command prompt and run the following command.          

                     encryptInput/encryptInput.exe

Step 4: Follow the prompt to encrypt your value

When you run the tool, it will ask you:

Enter password:

       type the value you want to encrypt

       Example : 

       Enter password: mysecretpassword

       It will give you an encrypted string like:

       EQHGuVfEHaxJQLfiXSgunZfYfjJqErrPBrmQTdTSuhNUpxG6to8YQOwp8yGqFIg2

2.6.3 Default Dashboard

The Default Dashboard module in the IANN Monitor application automates the creation of dashboards and alert configurations for a given environment. This significantly reduces the manual effort required during setup and ensures a consistent, ready-to-use monitoring experience from the start — saving time and accelerating customer onboarding.

This default dashboard location needs to be specified in the application.yml file of the IANN Monitor application to enable automatic creation of dashboards and alerts.

Step 1: Before configuring the default_dashboard location in the application.yml file (as shown in later sections), you need to extract the default dashboard files to prepare it to use.

Step 2: To extract, go to IANN_Monitor_Server location.

Step 3: Extract the ZIP file by right-clicking and selecting “Extract All…”.

2.6.4 Configure application.yml  for IANN Monitor Application.

This section explains how to configure the application.yml file for the IANN Monitor application, highlighting the key settings you need to update for proper operation.

Key Sections to Update:

1.    SSL: Enable SSL for the IANN Monitor application.

2.    Port: Default is 8080. Change this if needed.

3.    FileLocation: Path to the default dashboard files, used to auto-create dashboards after installation.

4.    timeZone: Defaults to UTC. Change to CST, IST, EST, etc. as needed.

5.    defaultUser: Set the default user details like userId, firstName, and lastName.

6.    elasticSearch: Configure Elasticsearch credentials — username, password, host, port, and truststore.

7.    SMTP: SMTP settings for sending email notifications.

8.    Logo: Path to the logo file shown in the application.

9.    Saml:SSO and role mappings (if enabled)

Step 1: Go to IANN_Monitor_Server folder and open application.yml to update the configurations.

Step 2: SSL and Port Configuration:

To secure data transmission and protect sensitive information, the IANN Monitor application supports SSL.

Below is an example of how to configure SSL and set the server port in your application.yml file.

1.    Make sure to replace <Install_dir> and <keystore password> with your actual values.

2.    Adjust the port if you want the application to listen on a different port.

Note : To encrypt Keystore password refer to – 3.6.2 Encrypting Password

Step 3: FileLocation Configuration:

1.    Set the default dashboard path to fileLocation under python.

Step 4: TimeZone Configuration:

1.    By default, the timeZoneFormat under timezone is set to UTC. Change it to CST or your preferred timezone if necessary.

Step 5: Default User Configuration:

Update the following in defaultUser section:

1.    userId: The unique login username for the default admin user (e.g., superadmin).

2.    firstName: First name of the user.

3.    lastName: Last name of the user.

4.    phNo: Contact phone number.

5.    emailId: Email address for this user account.

6.    status: Keep this as Y to indicate the user is active; otherwise, keep it to N.

7.    password: The password the user will use to log in (encrypted in the system after first use).

8.    role: The user’s role, typically SUPER_ADMIN for the default administrative user.

Step 6: Elasticsearch Configuration:

The Elasticsearch section in your application.yml file is used by the IANN Monitor application to connect securely to your Elasticsearch instance.

It includes all the necessary connection details like credentials, host, port, and truststore for SSL.

Note : To encrypt Elasticsearch and truststore passwords refer to – 3.4.2 Encrypting Password

What to update:

1.    userName: The Elasticsearch username with permissions to read and write data.

2.    password: The password for the Elasticsearch user. (Consider encrypting this using the provided encryptInput tool.)

3.    hostName: The fully qualified domain name (FQDN) or IP address where your Elasticsearch is hosted.

4.    port: The Elasticsearch port. Default is 9200.

5.    scheme: Use https for secure connections.

6.    trustStore: The full path to your truststore file (.p12), which ensures the application trusts your Elasticsearch server’s SSL certificate.

7.    trustStorePassword: The password you set when creating the truststore.(Consider encrypting this using the provided encryptInput tool.)

Step 7: SMTP Configuration:

The spring.mail section in your application.yml file allows the IANN Monitor application to send email notifications.

What to update

1.    host: Your SMTP server hostname (for example, smtp.gmail.com, smtp.office365.com, or your internal SMTP server).

2.    port: The SMTP server port. Usually 587 for TLS/STARTTLS or 465 for SSL.

3.    username: The SMTP username used to authenticate (often an email address or SMTP access key).

4.    password: The SMTP password or access key. Encrypt this using the encryptInput tool before putting it here.

Step 8: Logo Configuration:

The logoPath setting in your application.yml file specifies the path to the logo image that will be displayed in the IANN Monitor application UI.

How to update the logo:

By default, the Pragmaedge logo is used. To replace it with your own brand logo, follow these steps:

1.    Delete the existing logo.png file from the IANN_Monitor_Server folder.

2.    Upload your desired logo.png file to the same IANN_Monitor_Server folder.

3.    Rename your uploaded file to logo.png.

4.    Ensure that logoPath in your configuration points to:
 IANN_Monitor_Server\logo.png

Step 9: Saml Configuration:

To integrate SAML Single Sign-On (SSO) with the IANN Monitor application.

What to update

1.    sso-url:

Update this to point to your Identity Provider’s Single Sign-On (SSO) URL.

2.    slo-url:
Set this to your Identity Provider’s Single Logout (SLO) URL.

3.    idp.metadata:

 Upload your IdP metadata XML file to the server (for example, under <Install_dir>/IANN_Monitor_Server/) and update this field with the full path to that file.

4.    registration-id:

Change this to the unique registration identifier configured for your SAML integration.

5.    idp-groups-role-mapper:
Update this mapping to reflect your IdP groups and their corresponding application roles.

SuperAdmin-SUPER_ADMIN,Admin-ADMIN,BusinessAdmin-BUSINESS_ADMIN,BusinessUser-BUSINESS_USER

The above mapping follows the format:

<SAML IdP Group> – <IANN Monitor Application Role>

Add accordingly based on your setup.

For example:

SuperAdmin-SUPER_ADMIN,Admin-ADMIN,BusinessAdmin-BUSINESS_ADMIN,BusinessUser-BUSINESS_USER

Left side (SuperAdmin, Admin, etc.) are your SAML IdP groups.

Right side (SUPER_ADMIN, ADMIN, etc.) are your IANN Monitor application roles.

Update or add mappings as needed to reflect your organization’s SAML groups and their corresponding application roles

2.6.5 Deploy IANN Monitor Application

Once application.yml changes are done.

Step 1: Navigate to win64 folder in nssm from command prompt.

Step 2: Enter the below command.

After running the command, the following User Account Control (UAC) prompt will appear:

Click “Yes” to allow NSSM to make changes to your system. This is required to install the IANNMonitorUI service.

Step 3: You will get a pop up of nssm for creating a service

Step 4: Install the IANN Monitor Application

1.    Under the “Application” tab:

a.     In the “Path” field, browse and select the java.exe file (usually located inside the Java/bin directory).

b.    In the “Startup directory” field, select the folder where the IANN Monitor UI JAR file is located.

c.     In the “Arguments” field, enter the following for without saml:

-Dspring.profiles.active=IANN_monitor  -jar IANNMonitorUI.jar

d.    To run the application with the SAML configuration, replace the iann_monitor profile in the arguments with the saml profile. The updated “Arguments” will be:

-Dspring.profiles.active=saml  -jar IANNMonitorUI.jar

2.    Once all fields are filled correctly, click on the “Install service” button to complete the setup.

Step 5: To start IANN_Monitor_UI, open Task Manager and go to the Services tab. Find IANN_Monitor_UI, right-click on it, and select Start. The service will then show as Running.

Step 6: Accessing the Application UI:   

1.    Once the application has started successfully, open your browser and search with

https://localhost:9200

2.    Use the username and password set in application.yml to log in for the first time:

Default credentials:

username:superadmin

Password: Expl0re

2.7 Send Mail and Alert Configuration:   

1.    alerts: Monitors for critical and warning conditions, evaluates if any alert thresholds are triggered, and records these alerts in Elasticsearch.

2.    send_mail: Retrieves the stored alerts from Elasticsearch and sends alert notification to the configured reporting systems.

2.7.1 Extract alerts.zip and Send_mail.zip

Step 1: Go to the IANN_Monitor folder we can see alerts and send mail packages as shown in the below and extract the zip files one after the other.

2.7.2 Edit config.ini file for Elasticsearch and SMTP Details

Step 1: Go to the IANN_Monitor_Server folder and check config.ini.

Step 2: Update the following sections for Alerts and Send Mail.

[elasticsearch] Section

[elasticsearch]
port = <elasticsearch_port>
url = https://<elasticsearch_host>:<elasticsearch_port>
username = <elastic_username>
password = <encrypted_password>
use_ssl = true

1.    Replace <elasticsearch_host> with the hostname or IP address of your Elasticsearch server.

2.    Set username to your Elasticsearch username.

3.    Update password with your encrypted Elasticsearch password.

4.    Confirm port matches your Elasticsearch port (default is 9200).

5.    Ensure use_ssl is true if you are using HTTPS.

Note : To encrypt Elasticsearch password refer to – 3.6.2 Encrypting Password

[email] Section

[email]
port = <smtp_port>
host  = <smtp_host>
from =  <smtp_sender_email_id>
username = <smtp_user>
password = <smtp_encrypted_password>

1.    host: Set this to your SMTP server address (e.g., smtp.office365.com, smtp.gmail.com, or your internal SMTP server).

2.    port: Usually 587 for TLS; change if your SMTP provider uses a different port.

3.    from: The sender email address that will appear in outgoing emails.

4.    username: Your SMTP username (often the email address or an SMTP access key).

5.    password: encrypted smtp password.

Note : To encrypt Elasticsearch password refer to – 3.6.2 Encrypting Password

2.7.3 Start Alerts and Send Mail Agents

Step 1: To Install alerts and send mail package, go back to the nssm folder and open win64 folder. Now select the path and type cmd, it will take you to the command prompt.

Step 2: Enter the below command to install alerts.

nssm install alerts

Step 3: Set the Application Path to the location of alerts.exe and click Install Service.

Step 4: To start alerts, Go to services in task manager and search for alerts . Right click on the alerts and then start it, it will come to running state as shown below.

Step 5: Enter the command below to install send mail.

nssm install send_mails

Step 6: Set the Application Path to the location of send_mails.exe and click Install Service.

Step 7: To start send_mails, Go to services in task manager and search for alerts . Right click on the alerts and then start it, it will come to running state as shown below.

Step 8: Go to the alerts and send mail package location and open the “alert.log” and “send_mail.log” text document and verify the logs for any errors or exceptions and then validate the time of the logs with the current time

2.8 Configure Heartbeat and System Stats

Heartbeat:
Heartbeat monitors the health and availability of servers and applications by regularly checking their status through configured URLs and IP’s . It ensures that critical services are up and running and promptly detects any downtime or connectivity issues

What to Update

1.    ip = [“<IP>:Server Name”]
 Specify the server IP address and its name.

For example:
 ip = [“127.0.0.1:1:WebServer1”, “127.0.0.2.11:DatabaseServer”, “127.0.0.1.12:CacheServer”]

2.    urls = [“url:Application Name”]
 Provide the application URL along with a descriptive name.

For example:
 urls = [“https://webapp.company.com:WebApp“, “http://api.company.com:APIService“, http://auth.company.com:AuthService]

3.    schedule_heatbeat_seconds = 60
 This sets how often (in seconds) the heartbeat checks run. The default is 60 seconds, but you can update it if you want health checks to run more or less frequently

Systemstats:
Systemstats collects key server metrics, including CPU usage, memory (RAM) utilization, disk space consumption, and network activity. This helps in continuously tracking the resource performance and capacity of the server infrastructure.

What to Update

1.    schedule_system_stats_seconds = 300
 This sets how often (in seconds) the system statistics are collected. The default is 300 seconds (i.e., every 5 minutes). You can change this value to run the checks more or less frequently, for example schedule_system_stats_seconds = 120 to collect stats every 2 minutes.

2.    os = windows
 Specify the operating system of the servers being monitored. For example:
 os = windows for Windows servers.

3.    environment = general
 Label the environment type for easier identification in logs and dashboards. For example:
 environment = production, environment = staging, or environment = general.

2.8.1 Heartbeat Installation

Step 1: To Install Heartbeat, go back to the nssm folder and open win64 folder. Enter the command below.

nssm install heartbeat

Now Set the Application Path to the location of heartbeat.exe and click Install Service.

Step 2: To start Heartbeat, Go to services in task manager and search for heartbeat. Right click on the heartbeat and then start it, it will come to running state as shown below.

2.8.2 Systemstats Installation

Step 1: To Install Systemstats, go back to the nssm folder and open win64 folder. Enter the command below.

nssm install systemstats

Now Set the Application Path to the location of systemstats.exe and click Install Service.

Step 2: To start systemstats, Go to services in task manager and search for systemstats. Right click on the systemstats and then start it, it will come to running state.

2.9 Teams and Slack Integration:

   Step 1: Go to the IANN_Monitor_Server folder and check for Teams and slack packages.

     Step 2: The following changes need to be made in the config.ini file, which is located in the same directory as the Teams and Slack packages.

1.    From – Specify the email ID from which notifications should be triggered.

2.    Queuedepth_threshold – Define the threshold value. Any queue exceeding this threshold will trigger a notification in Teams/Slack.

3.    Url_heartbeat_index – Provide the environment prefix along with the URL heartbeat index in a key-value pair format.

a.    Example (Single Environment):

b.    Example (Multiple Environments):

4.    System_heartbeat_index – Configure this similar to Url_heartbeat_index, but use the system heartbeat index instead of the URL heartbeat index.

5.    IANN_monitor_UI_url – Specify the IANN Monitor UI URL.

6.    Server_metrics – To monitor server metrics, provide the server metrics index along with its name and prefix.

a.    Example (Single Server):

b.    Example (Multiple Servers):

Step 3: Open Command Prompt from NSSM Folder

1.    Navigate to the nssm folder.

2.    Open the win64 subfolder.

3.    Click on the address bar, type cmd, and press Enter to open the Command Prompt window in that directory.

Step 4: Install the Teams Package

In the Command Prompt window, enter the following command to begin installing the Teams service:

1.    In the NSSM service installer window that appears, click on the three dots next to the Path field.

2.    Browse and select the teams.exe located in the server folder.

3.    Click OK to confirm.

Step 5: To start Teams, Go to services in task manager and search for Teams. Right click on the teams and then start it, it will come to running state as shown below.

Step 6: Install the Slack Package

Go to the win64 location from command prompt and run the command below.

nssm install slack

1.    In the NSSM service installer window that appears, click on the three dots next to the Path field.

2.    Browse and select the slack.exe located in the server folder.

3.    Click OK to confirm.

Step 7: To start Slack, Go to services in task manager and search for Slack. Right click on the slack and then start it, it will come to a running state as shown below.

2.10 Weekly Report Configuration

The weekly report offers a high-level overview of how your systems and applications are performing, highlighting average daily usage metrics. It is automatically generated every week to help you track trends and identify any areas that may need attention.

Note: Make sure to configure these settings and start the weekly report after your client agents have started to avoid indexing not found errors.

This section describes how to configure Weekly Reports config.ini file.

Step 1: Go to config.ini located at IANN_Monitor_Server to update the configurations.

Make sure to update the following sections:

[Environment_Type]- section

[Environment_Type]
vm = true
openshift = false
lightwell_metrics = false
environment = <environment name>
environment_prefix =  <environment prefix>
pragmaedge_image_path = <logo path>
pdf_name = <pdf name>
ram_field = RAM Utilization
image_width = 30
image_height = 15
x_axis = 240
y_axis = 1
timezone = UTC,UTC
schedule_weekly_reports_time_in_seconds = 1000

What to Update

1.    vm = true
 Set this to true if you are monitoring a VM environment.

2.    openshift = false
 Set this to true if you are monitoring an OpenShift environment; otherwise keep it false.

3.    lightwell_metrics = false
 Set this to true if you want to include Lightwell metrics in the weekly reports.
 For example:
 lightwell_metrics = true

4.    environment
 This must be manually updated after you create the environment in the UI.
 For example:
 environment = my_environment

5.    environment_prefix = iann_monitor_test
 This should match the index prefix set in your [elasticsearch] section.
 For example:
 environment_prefix = iann_monitor_test

6.    timezone = Asia/Kolkata,IST
 Set to your local timezone for accurate timestamps.
 For example:
 timezone = Asia/Kolkata,IST

7.    pdf_name = <name_for_pdf_reports>
 Sets the base name for the generated PDF reports.
 For example:
 pdf_name = system_health_report

8.    pragmaedge_image_path = <logo_file>
 Provide the image file (logo) path that will appear in your PDF reports.
 For example:
 pragmaedge_image_path = company_logo.png

[weekly_report_vm] – section

[weekly_report_vm]

serverdetails = {“App Server Metrics”: “envprefix_appserver_metrics-*”,

“Database Server Metrics”: “envprefix_dbserver_metrics-*”} 

What to Update

1.    Update headings and index name in serverdetails.

2.    “App Server Metrics” is the heading that will appear in your PDF report for this server

3.    “envprefix_appserver_metrics-*” is the Elasticsearch index pattern where this server’s metrics are stored.

[email] – section

Add the line below under the email section to send the weekly report to the specified email address:

to = receiver@email.com

[weekly_report_openshift] – section

No need to configure [weekly_report_openshift] since this is not an OpenShift environment.

2.10.1 Start Weekly Report

Step 1: Go to IANN Monitor Server folder, locate Weekly Report package and extract its contents.

Step 2: Open Command Prompt from NSSM Folder

1.    Navigate to the nssm folder.

2.    Open the win64 subfolder.

3.    Click on the address bar, type cmd, and press Enter to open the Command Prompt window in that directory.

Step 3: Install the Weekly Report Package.

nssm install Weekly_report

1.    In the NSSM service installer window that appears, click on the three dots next to the Path field.

2.    Browse and select the Weekly_report.exe located in the server folder.

3.    Click OK to confirm.

Step 4: To start Weekly_report, Go to services in task manager and search for Weekly_report. Right click on the Weekly_report and then start it, it will come to running state.