​

Monitor Service

​

What is Monitor Service?

​

Key Features

• Free to Use: No cost for monitoring your services
• Multiple Monitor Types: HTTP, PING, PORT, and SOCKET monitoring
• Flexible Check Intervals: Configure checks from 30 seconds to 24 hours
• Custom Timeouts: Set maximum wait time for responses
• Email Notifications: Receive instant email alerts to your provided email address when services go down
• Real-time Dashboard: View uptime status and historical data
• Response Time Tracking: Monitor performance metrics
• Status Code Validation: Verify expected HTTP status codes
• Error Tracking: Capture and log error messages

​

Monitor Types

​

HTTP Monitoring

• Website availability
• API endpoint health
• REST API monitoring
• Webhook endpoints

​

PING Monitoring

• Server uptime
• Network connectivity
• Host availability

​

PORT Monitoring

• Database port monitoring
• Custom service ports
• Port availability checks

​

SOCKET Monitoring

• Custom protocol monitoring
• Socket-based services
• Real-time connection checks

​

Getting Started

​

Step 1: General Information

1. Service Name: Enter a friendly name to identify your monitor (e.g., “Antryk Website”, “API Endpoint”)
2. Target URL: Enter the URL or endpoint you want to monitor (e.g., https://antryk.com)

​

Step 2: Monitor Settings

1. Monitor Type: Select from HTTP, PING, PORT, or SOCKET
2. Expected Status: Enter the expected status code (e.g., 200 for OK, 201 for Created)

​

Step 3: Check Interval

• Range: 30 seconds to 24 hours
• Default: 5 minutes (300 seconds)
• Use the slider or enter a specific value in seconds

• 30 seconds: Critical services requiring immediate detection
• 1 minute: High-priority endpoints
• 5 minutes: Standard monitoring (recommended)
• 15 minutes: Low-priority services
• 1 hour: Non-critical monitoring

​

Step 4: Timeout Configuration

• Range: 1 second to 60 seconds
• Default: 10 seconds
• Use the slider or enter a specific value in seconds

• 1-5 seconds: Fast APIs and static sites
• 10 seconds: Standard web services (recommended)
• 30 seconds: Slow endpoints or heavy processing
• 60 seconds: Very slow services or batch operations

​

Step 5: Notification Configuration

1. Email Address: Enter the email address where you want to receive notifications when your service goes down
2. Add Multiple Emails: Click the plus icon to add additional email addresses for team notifications

• Service Goes Down: You will receive an email notification immediately when your service is detected as down (status check fails). The email will be sent to all email addresses you configured during monitor creation.
• Service Recovers: Get notified when your service comes back online after being down
• Response Time Exceeds Threshold: Alerts for performance degradation
• Unexpected Status Code: Notifications when the service returns an unexpected HTTP status code

​

Step 6: Deploy Monitor

​

Monitor Dashboard

​

Monitor Overview

• Monitor ID: Unique identifier for your monitor
• Status: Active/Inactive status with visual indicator
• Target URL: The endpoint being monitored
• Check Frequency: How often checks are performed
• Monitor Type: HTTP, PING, PORT, or SOCKET
• Expected Status: The expected response code

• Copy ID: Copy the monitor ID for API usage
• Edit: Modify monitor configuration
• Delete: Remove the monitor

​

Monitor Results

• Checked At: Timestamp of each check
• Status: UP or DOWN status with visual indicator
• Response Time: Time taken for the response (in milliseconds)
• HTTP Code: Status code received
• Error: Error message if check failed

• Pagination for large result sets
• Filter by date range
• Export results
• View detailed error logs

​

Status Codes

• 200: OK - Service is healthy
• 201: Created - Resource created successfully
• 204: No Content - Success with no response body
• 301/302: Redirects - Service is redirecting
• 400: Bad Request - Client error
• 401: Unauthorized - Authentication required
• 403: Forbidden - Access denied
• 404: Not Found - Resource not found
• 500: Internal Server Error - Server error
• 502: Bad Gateway - Gateway error
• 503: Service Unavailable - Service temporarily unavailable
• 504: Gateway Timeout - Gateway timeout

​

Email Notifications

​

Service Down Notification

• Service name you configured
• Target URL that is down
• Timestamp of when the issue was detected
• Error details (if available)
• Monitor type and expected status

​

Service Recovery Notification

​

Notification Best Practices

• Use Active Email Addresses: Ensure the email address you provide is one you check regularly
• Add Team Members: Add multiple email addresses to notify your entire team
• Check Spam Folder: If you’re not receiving notifications, check your spam/junk folder
• Email Filters: Set up email filters to prioritize monitor notifications
• Separate Monitors: Use different email addresses for different environments (production vs staging)

​

Best Practices

​

Check Intervals

• Critical Services: Check every 1-5 minutes
• Standard Services: Check every 5-15 minutes
• Non-Critical: Check every 15-60 minutes

​

Timeout Settings

• Set timeout to 2-3x your expected response time
• Account for network latency
• Consider peak traffic times

​

Multiple Monitors

• Create separate monitors for different endpoints
• Monitor both production and staging environments
• Set up monitors for critical API endpoints

​

Notification Management

• Add multiple email addresses for team alerts
• Use email filters to organize notifications
• Set up escalation for critical services
• Verify email addresses are correct before deploying monitors

​

Use Cases

​

Website Monitoring

Service Name: Production Website
Target URL: https://example.com
Monitor Type: HTTP
Expected Status: 200
Check Interval: 5 minutes

​

API Health Checks

Service Name: User API
Target URL: https://api.example.com/health
Monitor Type: HTTP
Expected Status: 200
Check Interval: 1 minute

​

Database Port Monitoring

Service Name: PostgreSQL Database
Target URL: db.example.com
Monitor Type: PORT
Expected Status: 5432
Check Interval: 5 minutes

​

Server Availability

Service Name: Web Server
Target URL: server.example.com
Monitor Type: PING
Expected Status: OK
Check Interval: 1 minute

​

Pricing

​

Limitations

• Maximum monitors per account: 50 (subject to change)
• Email notifications only (SMS/webhooks coming soon)
• Historical data retention: 30 days

​

Troubleshooting

​

Monitor Shows as DOWN but Service is Up

1. Check if the URL is accessible from your browser
2. Verify the expected status code matches the actual response
3. Increase timeout if service is slow to respond
4. Check firewall rules blocking monitoring servers

​

Not Receiving Email Notifications

1. Verify Email Address: Double-check the email address you provided during monitor creation is correct
2. Check Spam/Junk Folder: Monitor notification emails may be filtered as spam
3. Verify Monitor Status: Ensure your monitor is in Active status (not paused or deleted)
4. Check Service Status: If your service hasn’t actually gone down, you won’t receive notifications
5. Email Provider Issues: Some email providers may delay or block automated emails
6. Multiple Emails: If you added multiple emails, check all of them

​

High Response Times

1. Check your service performance
2. Review server logs for issues
3. Consider CDN or caching solutions
4. Optimize database queries or API responses