NetCrunch

Overview

This document provides a detailed guide to integrating AdRem NetCrunch with Callgoose SQIBS for real-time Incident Management, Incident Auto Remediation, Event-Driven Automation, and other automation workflows.

The integration enables automatic creation, updating, and resolution of incidents in Callgoose SQIBS based on alerts triggered in NetCrunch.

The guide includes:

• Installing AdRem NetCrunch
• Steps to configure Webhook notifications in NetCrunch
• Steps to create API Filters in Callgoose SQIBS
• Example Trigger & Resolve JSON payloads
• Troubleshooting recommendations

NetCrunch supports Webhooks for forwarding device, service, performance, and SNMP event notifications — which can be consumed directly by Callgoose SQIBS.

Prerequisites

• AdRem NetCrunch Account: With access to Monitoring Policies and Notification Settings.
• Callgoose SQIBS Account: With privileges to create API Filters and use API Tokens.
• Webhook/API Endpoint: Available in Callgoose SQIBS to receive NetCrunch alerts.

1. Obtain API Token and Endpoint Details

To integrate NetCrunch with Callgoose SQIBS:

Generate an API Token

Follow the document “How to Create API Token in Callgoose SQIBS”.

Find the API Endpoint

Refer to Callgoose SQIBS API Endpoint Documentation to obtain the final webhook URL.

Example Format:

https://****.callgoose.com/v1/process?from=FromValue&token=xxxx

This URL will be configured inside NetCrunch Webhook Notifications.

2. Installing AdRem NetCrunch

NetCrunch must be installed and running before you configure alert forwarding to Callgoose SQIBS.

2.1 System Requirements

Supported Operating Systems (64-bit only):

• Windows Server 2019 / 2022 (recommended)
• Windows 10 / 11 (for testing environments)

Minimum Hardware Requirements:

• CPU: Quad-core
• RAM: 16 GB minimum (32 GB recommended)
• Storage: 40 GB free space (SSD recommended)
• Network: Stable, low-latency network access

Additional Requirements:

• Administrator permissions
• Internet connectivity for updates and integrations
• Firewall rules allowing NetCrunch services

2.2 Downloading NetCrunch

• Visit the official website:
• https://www.adremsoft.com/netcrunch.tools/
• Sign in or create an account.
• Download the latest NetCrunchSetup.exe installer.
• Copy the installer to the machine where NetCrunch will run.

2.3 Installing NetCrunch

• Run the installer as Administrator.
• Click Next and accept the license agreement.
• Choose the installation directory.
• Select components to install:
• NetCrunch Server
• NetCrunch Console
• Remote Probe (optional)
• Click Install.
• Launch NetCrunch Console after installation completes.

2.4 Initial Post-Installation Setup

1. Set the Administrator password.
2. Configure network discovery ranges.
3. Enable SNMP/WMI/Flow monitoring if required.
4. Add your first device or network for monitoring.

2.5 Optional Components

• Remote Probes for segmented or distributed networks
• Web Console for browser-based monitoring
• Auto-Update Service for updates and integrations

2.6 Validate Installation

Perform post-install checks:

• Ensure NetCrunch Server Service is running
• Check Dashboard → System Health
• Add a test device
• Trigger a test alert to confirm monitoring capability

Once confirmed, proceed to webhook configuration.

3. Configuring AdRem NetCrunch to Send JSON Payloads

NetCrunch supports sending alert notifications through Webhooks.

You must configure a Webhook rule so NetCrunch sends alert JSON to Callgoose SQIBS.

3.1 Steps to Enable Webhook Notifications

• Log in to NetCrunch Console
• Use either the Desktop Console or the Web Console.
• Navigate to Notification Policies
• Go to:
• Monitoring → Policies → Notification Scripts
• Create a New Webhook Notification
• Select:
• Add Action → Webhook
• Configure:
• URL: Callgoose SQIBS API endpoint
• Method: POST
• Content-Type: application/json
• Body Template: Use placeholder variables provided by NetCrunch

3.2 Recommended Webhook Payload Template

NetCrunch supports dynamic placeholders.

Use this production-ready JSON template:

{
  "alert_id": "{AlertId}",
  "node_id": "{NodeId}",
  "node_name": "{NodeName}",
  "event_type": "{EventType}",
  "status": "{Status}", 
  "timestamp": "{EventTime}",
  "title": "{AlertName}",
  "description": "{Description}",
  "severity": "{Severity}",
  "category": "{Category}",
  "ip_address": "{IpAddress}",
  "policy": "{PolicyName}",
  "is_test": "{IsTest}"
}

4. Example JSON Payloads from NetCrunch

These sample objects represent how NetCrunch typically delivers Webhook payloads.

4.1 Alert Triggered (status: “ALERT”)

{
  "alert_id": "NC-44321",
  "node_id": "12",
  "node_name": "Linux-Production-01",
  "event_type": "ServiceDown",
  "status": "ALERT",
  "timestamp": "2025-01-12T08:42:22Z",
  "title": "Ping Response Lost",
  "description": "Node Linux-Production-01 is not responding to ping.",
  "severity": "Critical",
  "category": "Availability",
  "ip_address": "10.2.1.44",
  "policy": "Core Servers Monitoring",
  "is_test": false
}

4.2 Alert Resolved (status: “OK”)

{
  "alert_id": "NC-44321",
  "node_id": "12",
  "node_name": "Linux-Production-01",
  "event_type": "ServiceDown",
  "status": "OK",
  "timestamp": "2025-01-12T08:49:11Z",
  "title": "Ping Response Restored",
  "description": "Node Linux-Production-01 is now responding to ping.",
  "severity": "Normal",
  "category": "Availability",
  "ip_address": "10.2.1.44",
  "policy": "Core Servers Monitoring",
  "is_test": false
}

5. Configuring Callgoose SQIBS

5.1 Create API Filters in Callgoose SQIBS

To correctly map incidents from NetCrunch, you must create Trigger and Resolve filters.

5.2 Integration Template (If Available)

If a NetCrunch Integration Template is available, select it.

It automatically creates:

• Trigger filter
• Resolve filter
• Required mappings

You may customize values afterward.

5.3 Manually Add/Edit Filters

• Trigger Filter (for creating incidents)
• Payload JSON Key: status
• Key Value Contains: ALERT
• Map Incident With: alert_id
• Incident Title From: title
• Incident Description From: (optional) description
• Resolve Filter (for resolving incidents)
• Payload JSON Key: status
• Key Value Contains: OK
• Incident Mapped With: alert_id

This ensures incidents created from the same alert source are resolved correctly.

5.4 Finalizing Setup

• Save all filters
• Validate required fields (alert_id, title, status) exist in payloads

6. Testing and Validation

6.1 Trigger Test from NetCrunch

Go to:

Notifications → Webhook → Test Action

Verify in SQIBS:

• Incident is created
• Title matches
• Description appears
• Mapping uses correct alert_id

6.2 Resolve Test

Use NetCrunch's test resolve or simulate a recovery event.

Verify:

• Incident is marked Resolved
• Correct ID mapping

7. Security Considerations

• Only use HTTPS Webhook URLs
• Store API tokens securely
• Restrict NetCrunch console access
• Avoid exposing sensitive data in logs

8. Troubleshooting

No incident created

• Check Webhook URL
• Ensure status includes ALERT
• Review API logs

Incident not resolved

• Confirm payload includes status: "OK"
• Ensure mapping uses alert_id

No payload received

• Check firewall rules
• Verify NetCrunch can reach external endpoints

9. Conclusion

This guide provides a complete overview of how to integrate AdRem NetCrunch with Callgoose SQIBS for effective monitoring-driven incident management.

By following the configuration steps, alerts from NetCrunch will automatically generate and resolve incidents in Callgoose SQIBS.

Additional References:

• NetCrunch Documentation
• Callgoose SQIBS API Token Docs
• Callgoose SQIBS API Endpoint Docs
• API Filter Instructions