Initial Setup (SaaS)
Complete your first-time Hydranaut configuration for the cloud-hosted platform.
Prerequisites
- Active Hydranaut account
- Admin role
- Email verification completed
Setup Workflow
Step 1: Access Your Dashboard
- Navigate to hydranaut.nimbitlabs.com
- Log in with your credentials
- You'll land on the main dashboard
Step 2: Complete Account Profile
- Click your avatar (top-right) → Account Settings
- Fill in required fields:
- Organization Name: Your company/team name
- Time Zone: Select your local timezone
- Notification Email: Where alerts will be sent
- Click Save Changes
Step 3: Create Your First Environment
Environments organize services by deployment stage.
- Navigate to Environments → Create New
- Enter environment details:
- Name: e.g., "Production"
- Description: e.g., "Live production services"
- Color Tag: Select a color for visual identification
- Click Create Environment
Recommended environments:
- Production
- Staging
- Development
Step 4: Configure Default Settings
- Go to Settings → Monitoring Defaults
- Set global defaults:
- Health Check Interval: 5 minutes (recommended)
- Health Check Timeout: 30 seconds
- Expected Status Code: 200
- Retry Attempts: 3
- Click Save Defaults
Note: These are defaults; you can override per service.
Step 5: Set Up Alert Preferences
- Navigate to Settings → Alert Preferences
- Configure global alert settings:
- Alert Threshold: Number of failed checks before alerting (default: 2)
- Alert Cooldown: Minimum time between alerts (default: 15 minutes)
- Email Notifications: Enable/disable
- Click Save Preferences
Step 6: Review Subscription Tier
- Go to Account Settings → Subscription
- Verify your current tier
- Review limits:
- Service monitoring limit
- Data retention period
- Available integrations
- Upgrade if needed
→ Subscription Tiers Comparison
Verification Checklist
Confirm your setup is complete:
- Account profile filled out
- At least one environment created
- Default monitoring settings configured
- Alert preferences set
- Subscription tier confirmed
What's Next?
After initial setup:
Configuration Best Practices
Environment Naming
Use clear, consistent names:
- ✅ Good: "Production", "Staging", "Development"
- ❌ Avoid: "Prod1", "Test-Env-New", "Temp"
Health Check Intervals
Balance monitoring frequency with API load:
- Production: 5 minutes (default)
- Staging: 10 minutes
- Development: 15 minutes
Alert Thresholds
Set thresholds to avoid alert fatigue:
- Critical services: 2 failed checks
- Standard services: 3 failed checks
- Development: 5 failed checks
Troubleshooting
Can't Create Environment
Problem: "Create Environment" button is disabled.
Solutions:
- Verify you have Admin role
- Check subscription tier limits (Free tier: 1 environment)
- Try refreshing the page
Settings Not Saving
Problem: Changes to defaults don't persist.
Solutions:
- Check for validation errors (red text)
- Ensure all required fields are filled
- Clear browser cache and retry
- Try different browser
Email Verification Required
Problem: Some features locked until email verified.
Solutions:
- Check spam folder for verification email
- Request new verification email from Account Settings
- Contact support if not received within 10 minutes
Advanced Configuration
Custom Health Check Headers
Add authentication headers for protected endpoints:
- Go to Settings → Monitoring Defaults → Advanced
- Click Add Header
- Enter header name and value: