AQUA ViolationGroup URL Monitoring Utility

A comprehensive monitoring utility that checks the health of URLs in Salesforce AQUA ViolationGroup records. This tool queries all AQUA_ViolationGroup__c records and validates the health of Component_Screenshot_URL__c, HTML_Source__c, and Screenshot_URL__c fields.

Features

• 🔍 Autonomous Operation: Runs without user prompts
• 🚀 Concurrent Processing: Checks multiple URLs simultaneously for faster execution
• 🔄 Retry Logic: Automatically retries failed requests with exponential backoff
• 📊 Comprehensive Reporting: Generates console, JSON, and CSV reports
• 🎯 Special URL Handling: Includes support for absctl URLs (HTML_Source__c)
• 🔧 Configurable: Customizable timeouts, retry attempts, and concurrency limits
• 🎨 Rich Console Output: Color-coded results with detailed summaries

Installation

1. Clone or download the project

2. Install dependencies:

   npm install

3. Set up environment configuration:

   cp env.template .env

4. Configure your credentials in .env:

   # Salesforce credentials (for SOQL queries)
   SF_USERNAME=your_salesforce_username
   SF_PASSWORD=your_salesforce_password
   SF_LOGIN_URL=https://gus--aquatest.sandbox.my.salesforce.com
   
   # Data store authentication is now FULLY AUTOMATED! 
   # Just run: npm run monitor
   # No manual configuration needed!

Prerequisites

• Node.js 16+ and npm
• Salesforce credentials with access to AQUA_ViolationGroup__c objects
• For HTML_Source__c URLs using absctl: absctl command-line tool installed

Installing absctl

If your HTML_Source__c fields contain URLs that require the absctl command:

# Check if absctl is installed
which absctl

# If not installed, follow your organization's instructions for installing absctl

🎉 Fully Automated: The monitoring utility now automatically handles authentication!

• No manual absctl auth:login needed
• No manual cookie configuration required
• Authentication is checked and performed automatically when you run npm run monitor

Usage

Basic Usage

Test Authentication (Optional)

If you want to test the authentication setup separately:

# Test automated JWT token retrieval
npm run test-auth

This will verify that:

• absctl is installed and accessible
• JWT token retrieval is working
• Token caching is functional

Note: This is optional since npm run monitor now handles authentication automatically.

Run the Monitoring Utility

The monitoring utility now automatically handles authentication:

# This will automatically:
# 1. Check if absctl is available
# 2. Verify if you're already authenticated 
# 3. Run "absctl auth:login" if needed
# 4. Build and start the monitoring utility
npm run monitor

# Or run in development mode (without auto-auth)
npm run dev

What happens automatically:

• ✅ Checks if absctl is installed
• ✅ Verifies existing authentication status
• ✅ Runs absctl auth:login only if needed
• ✅ Handles interactive authentication prompts
• ✅ Continues gracefully if authentication fails

Advanced Usage

You can customize the behavior using environment variables:

# Custom configuration
MAX_CONCURRENT_CHECKS=5 REQUEST_TIMEOUT_MS=60000 npm run monitor

Configuration

Environment Variables

Variable	Description	Default	Required
SF_USERNAME	Salesforce username	-	Yes
SF_PASSWORD	Salesforce password	-	Yes
SF_LOGIN_URL	Salesforce login URL	https://test.salesforce.com	Yes
USE_AUTO_AUTH	Enable automatic JWT token retrieval via absctl	true	No
DATA_STORE_COOKIES	[LEGACY] Manual cookie string for data store auth	-	Only if auto-auth disabled
DATA_STORE_SESSION_ID	[LEGACY] Alternative: just session ID	-	Only if auto-auth disabled
MAX_CONCURRENT_CHECKS	Maximum concurrent URL checks	10	No
REQUEST_TIMEOUT_MS	Request timeout in milliseconds	30000	No
RETRY_ATTEMPTS	Number of retry attempts for failed requests	3	No
GENERATE_JSON	Generate JSON report	true	No
GENERATE_CSV	Generate CSV report	true	No
OUTPUT_DIR	Output directory for reports	./	No

Configuration File (.env)

# Salesforce Configuration (for SOQL queries)
SF_USERNAME=your_username@company.com
SF_PASSWORD=your_password
SF_LOGIN_URL=https://test.salesforce.com

# Data Store Authentication (AUTOMATED via absctl)
# Just run: absctl auth:login
# No manual configuration needed!

# Advanced: Disable auto-auth if you want to use manual cookies
# USE_AUTO_AUTH=false
# DATA_STORE_COOKIES="session=abc123; auth=xyz789; csrf=token123"

# Monitoring Configuration
MAX_CONCURRENT_CHECKS=10
REQUEST_TIMEOUT_MS=30000
RETRY_ATTEMPTS=3

# Output Configuration
GENERATE_JSON=true
GENERATE_CSV=true
OUTPUT_DIR=./reports

Data Store Authentication

🎉 Automatic Authentication (Recommended)

For HTML_Source__c URLs that use absctl, authentication is now completely automated:

# Just run the monitoring utility - that's it!
npm run monitor

# The system will automatically:
# ✅ Check if you're already authenticated
# ✅ Run "absctl auth:login" if needed  
# ✅ Handle interactive authentication prompts
# ✅ Retrieve JWT tokens using 'absctl auth:login --show'
# ✅ Handle token caching and refresh
# ✅ Retry with fresh tokens if authentication fails

Manual Authentication (Legacy)

If you need to disable auto-auth and use manual cookies:

1. Set USE_AUTO_AUTH=false in your .env file
2. Open your browser and navigate to your data store service
3. Login to the service normally
4. Open Developer Tools (F12)
5. Go to Network tab and make any request
6. Find a request in the list and click on it
7. Look at Headers section and find Cookie:
8. Copy the entire cookie string (everything after Cookie: )
9. Paste it in your .env file as DATA_STORE_COOKIES

Example:

USE_AUTO_AUTH=false
DATA_STORE_COOKIES="sessionid=abc123xyz; csrftoken=def456; auth=ghi789"

Report Types

1. Console Report

Real-time colored output with granular URL type segregation:

• Executive summary with health statistics
• 📋 Granular URL breakdown (e.g., "3/18 component screenshot URLs are broken")
• URL type summary table
• Detailed results for broken/partial records
• 📝 Quick summary with broken URLs by type
• Actionable recommendations with specific URL type information

2. JSON Report

Machine-readable report containing:

• Complete monitoring results with granular URL type statistics
• Detailed error information
• Response times and status codes
• Timestamp and summary statistics

3. CSV Report

Spreadsheet-compatible format with enhanced URL type information:

• One row per URL check with URL type display names
• Record information and URL details
• Status and error information
• URL type segregation for easy filtering
• Suitable for further analysis and reporting

URL Types Supported

1. Component_Screenshot_URL__c

Standard HTTP/HTTPS URLs pointing to component screenshots.

2. Screenshot_URL__c

Standard HTTP/HTTPS URLs pointing to general screenshots.

3. HTML_Source__c

Special handling for two types:

• Standard URLs: Regular HTTP/HTTPS links
• absctl URLs: URLs with filename and runID parameters that use the absctl command

How It Works

1. Connect to Salesforce using provided credentials
2. Query all AQUA_ViolationGroup__c records with at least one URL field populated
3. Process records in batches to avoid overwhelming the system
4. Check each URL with appropriate method:
   • Standard HTTP HEAD requests for regular URLs
   • absctl command execution for special HTML_Source__c URLs
5. Retry failed requests with exponential backoff
6. Generate comprehensive reports with health analysis

Understanding Results

Health Status

• Healthy: All URLs in the record are working correctly
• Partial: Some URLs are working, some are broken
• Broken: No URLs are working or no URLs found

URL Health Criteria

• Healthy: HTTP status 200-399 or successful absctl download
• Broken: HTTP status 400+, DNS resolution failure, timeout, or absctl failure

Sample Output

🔍 AQUA ViolationGroup URL Monitoring Utility
=========================================

🔧 Validating configuration...
✅ Configuration validated successfully

🔌 Initializing services...
🔐 Connecting to Salesforce...
✅ Successfully connected to Salesforce
🚀 Starting monitoring process...

📊 Found 25 AQUA ViolationGroup records with URLs
🔍 Processing 25 records...

📦 Processing batch 1/3...
✅ Processed AVG-001: healthy (3/3 URLs healthy)
✅ Processed AVG-002: partial (2/3 URLs healthy)
✅ Processed AVG-003: broken (0/2 URLs healthy)

⏱️  Monitoring completed in 45.67 seconds

📊 Generating reports...

================================================================================
AQUA VIOLATIONGROUP URL MONITORING REPORT
================================================================================

📊 EXECUTIVE SUMMARY
--------------------------------------------------
┌─────────────────────────┬──────────┬─────────────────┐
│ Metric                  │ Count    │ Percentage      │
├─────────────────────────┼──────────┼─────────────────┤
│ Total Records           │ 25       │ 100.0%          │
│ Healthy Records         │ 18       │ 72.0%           │
│ Partial Records         │ 5        │ 20.0%           │
│ Broken Records          │ 2        │ 8.0%            │
└─────────────────────────┴──────────┴─────────────────┘

📋 GRANULAR URL BREAKDOWN
--------------------------------------------------
✅ Component Screenshot URLs: 15/18 healthy, 3 broken
   → 3/18 component screenshot urls are broken (16.7%)
⚠️  HTML Source URLs: 12/15 healthy, 3 broken  
   → 3/15 html source urls are broken (20.0%)
✅ Screenshot URLs: 20/22 healthy, 2 broken
   → 2/22 screenshot urls are broken (9.1%)

📝 QUICK SUMMARY
--------------------------------------------------
📊 Overall URL Health: 47/55 healthy (85.5%)
❌ Total Broken URLs: 8 (14.5%)

Broken by Type:
  • 3/18 Component Screenshot URLs
  • 3/15 HTML Source URLs  
  • 2/22 Screenshot URLs

Troubleshooting

Common Issues

1. Salesforce Connection Failed

   • Verify username and password
   • Check login URL (sandbox vs production)
   • Ensure user has permission to access AQUA_ViolationGroup__c

2. JWT Token Authentication Issues

   • Not authenticated: Run absctl auth:login to authenticate
   • Token expired: The system will automatically refresh tokens, but you may need to re-authenticate
   • absctl not found: Install absctl and ensure it's in your PATH
   • Permission errors: Ensure your absctl user has proper permissions
   • Test first: Run npm run test-auth to verify authentication setup

3. absctl Command Not Found

   • Install absctl following your organization's guidelines
   • Verify absctl is in your PATH: which absctl
   • Authenticate after installation: absctl auth:login
   • The utility will continue with other URLs even if absctl is missing

4. Legacy Manual Cookie Issues

   • If you disabled auto-auth (USE_AUTO_AUTH=false), ensure DATA_STORE_COOKIES is set
   • Update cookies if you get 401/403 errors
   • Consider re-enabling auto-auth for easier maintenance

5. Timeout Errors

   • Increase REQUEST_TIMEOUT_MS for slow networks
   • Reduce MAX_CONCURRENT_CHECKS to be less aggressive
   • JWT token retrieval may take longer on first run

6. Memory Issues

   • Reduce MAX_CONCURRENT_CHECKS
   • Monitor large datasets and consider filtering

Development

Project Structure

src/
├── index.ts          # Main application entry point
├── types.ts          # TypeScript type definitions
├── config.ts         # Configuration management
├── salesforce.ts     # Salesforce API integration
├── url-checker.ts    # URL health checking logic
├── monitor.ts        # Main monitoring orchestration
└── reporter.ts       # Report generation

Building

# Build the project
npm run build

# Run built version
npm start

Scripts

• npm run build - Compile TypeScript to JavaScript
• npm start - Run the compiled application
• npm run dev - Run in development mode with ts-node
• npm run monitor - Auto-authenticate and run the monitoring utility
• npm run pre-monitor - Just run the authentication setup (without monitoring)
• npm run test-auth - Test automated JWT token authentication

License

ISC License

Support

For issues or questions:

1. Check the troubleshooting section
2. Review the logs for detailed error messages
3. Ensure your environment configuration is correct
4. Verify network connectivity and permissions