Cloud Email Services (Gmail, Outlook, OAuth2)
NetCrunch includes dedicated sensors for monitoring cloud-hosted email services such as Gmail and Outlook. These sensors offer the same diagnostic functionality as traditional email sensors but use OAuth 2.0 authentication instead of basic credentials. They support Gmail, Microsoft 365/Outlook.com, and custom OAuth providers.
Overview
NetCrunch supports monitoring of modern cloud-based email platforms using a dedicated Cloud Email Service node. Once added, this node can host any of the three specialized cloud email sensors, which replicate the functionality of standard email monitors—while using OAuth 2.0 authentication to access protected accounts.
These sensors allow testing of mail delivery time, mailbox contents, and even scanning message bodies for alert conditions. This provides comprehensive, agentless visibility into cloud-hosted mail systems without the use of insecure credentials.
Supported Email Providers
The sensors support:
- Gmail / Google Workspace
- Microsoft Outlook.com / Microsoft 365
- Custom OAuth 2.0 providers (requires manual config of endpoints)
Authentication Setup
To use any of these sensors, you must create a Cloud Email Service Authentication Profile, which includes:
- Authentication Type: OAuth 2.0
-
Account Type:
- Gmail
- Outlook.com
- Custom OAuth settings
- Username (email address)
- Token authorization endpoint (for custom OAuth)
- Authorization code/token (generated via popup)
This ensures secure, standards-compliant access to mailbox data without storing passwords.
Available Cloud Email Sensors
All sensors are added from the Monitoring → Sensors section of a Cloud Email Service node.
Cloud Data Email
A powerful sensor that monitors inbound email content. It reads messages via IMAP and can:
- Filter by sender, subject, or content keywords
- Parse structured content for metrics
- Trigger alerts when specific phrases or values are found
- Monitor message arrival timing or missing messages
Typical use cases:
- Alert parsing from third-party systems
- Monitoring external job results or reports
- Verifying status emails from appliances or partners
Cloud Email Round-Trip
Tests the entire email pipeline by sending a message to a monitored mailbox and reading it back via IMAP.
- Sends test email via SMTP
- Tracks delivery delay
- Measures authentication success
- Detects send/receive failures or latency
Ideal for:
- SLA verification
- End-to-end delivery testing
- Alerting on silent mail failures or blocked delivery paths
Cloud Mailbox
A mailbox-level sensor that:
- Connects via IMAP using OAuth2
- Monitors mailbox health and authentication
-
Tracks counters like:
- Total message count
- Message age
- Folder-specific statistics
Useful for:
- Monitoring mailbox activity trends
- Alerting when usage exceeds thresholds
- Ensuring IMAP service is accessible and responsive
Key Differences from Traditional Sensors
| Feature | Traditional Email Sensor | Cloud Email Sensor |
|---|---|---|
| Authentication | Basic credentials | OAuth 2.0 |
| Mailbox type | Local/SMTP/IMAP/POP3 | Gmail, Outlook, custom OAuth IMAP |
| Security | Password stored (hashed) | Token-based (secure) |
| Compatibility | Any mail server | OAuth-supported cloud services |
| Integration | Node-based (Email Server) | Cloud Service Node |
Summary
Cloud Email sensors in NetCrunch allow secure, modern monitoring of cloud-hosted mail systems without compromising visibility or functionality. Whether you're tracking delivery time, scanning inboxes for alerts, or auditing mailbox usage, these sensors let you do so securely, efficiently, and without deploying agents.