Netreo monitors a wide range of data, offering a comprehensive overview of both Azure and standalone resources. Much of the information tracked by Netreo is not available in Azure Portal. A comprehensive list of differences by each resource is outlined later in this article so you can compare Netreo vs native Azure Monitoring.
In addition to monitoring, Netreo offers a number of unique automation features designed to provide users with ability to recover their cloud apps and services from production issues. When Netreo detects an issue, it can execute automated server reboots, run Powershell scripts, recycle IIS app pools, restart WebApps, start Azure Automation runbooks, etc. These operations are easily configured with a few clicks of a button.
Furthermore, Netreo offers an auto-scaling engine that allows for sophisticated auto-scaling conditions of Cloud Services, SQL Azure, WebApps, SQL Data Warehouses, etc. These capabilities are far superior to what is offered in the Azure Portal.
Metrics from various resources can be correlated, aggregated and computed to define advanced conditions for alerts, automation and auto-scaling rules. Contrary to Azure Portal, any signal from the monitored environment can be used in alerts, auto-scaling and self-healing automation.
In addition to real-time self-updating dashboards, Netreo allows users to browse their dashboards back in time to when issues occurred for investigation into Root Cause Analysis (RCA). Historical reports provide access to captured data for up to one (1) year. Customers can also ingest data collected by Netreo into their own SQL database for custom reporting and analysis.
To ease initial monitoring setup, the product comes built-in with useful metrics and alerts out of the gate. Furthermore, to save on configuration time, monitoring profiles can easily be saved, shared and applied to other resources via “resource templates” functionality.
Netreo seamlessly integrates with other popular third party applications, such as PagerDuty, Autotask, Slack, Zendesk, Nagios, Zabbix, and more. Full list of supported integrations is provided later in this article. SSO is supported for customers running Azure AD/ADFS/Office365/Google Apps/etc.
There are a number of features that target Managed Service Providers and other consulting organizations. MSPs can easily manage multiple customers (CSP’s are supported). MSPs can choose to keep their customers in separate Netreo sub-accounts and even invite their customers into these sub-accounts. White-labeling is supported.
DevOps can automate monitoring setup of their continuously deployed environments by using Netreo REST API. Keeping Production Azure resources or subscriptions separate from DEV/QA services is supported.
Here are just some of the important differences where Netreo tracks more data or provides automation and auto-scaling capabilities that far exceed the default native Azure offering:
|Netreo Benefits (features that Azure portal doesn’t have)
Azure Windows VMs
|Azure Cloud Services
Azure Service Bus
(Queues, Blob, File, Table)
|Azure Redis Cache
|Azure Backups Vault
Azure Virtual Network Gateways
Azure SQL Data Warehouse
|Azure Data Factories
|Azure Stream Analytics Jobs
|Azure Event Hubs
|Azure DocumentDb Collection
|Azure Media Services
|Azure Scheduler Job Collection
In addition to monitoring Azure resources, Netreo supports the following resources non-Azure resources:
|Standalone Windows Server
|Standalone SQL Server
|Other Endpoints: Socket,
Netreo provides integrations for 3rd party applications listed below. Integrations can be set up in just a few minutes.
|Netreo can open a new Autotask ticket when an alert is triggered, and automatically close it when alert is resolved.
|Netreo can open a new Freshdesk and Freshservice ticket when an alert is triggered, and automatically close it when alert is resolved.
|Netreo can post a notification message in a specified HipChat room when an alert is triggered and when it is resolved.
|Netreo can add a new log entry in Logentries a new log entry when an alert is triggered and when it is resolved.
|Netreo can add a new log entry in Loggly a new log entry when an alert is triggered and when it is resolved.
|During every monitoring cycle, host status and metrics can be synchronized to Nagios XI.
|Netreo can raise a new PagerDuty incident when an alert is triggered, and automatically resolve it when alert is resolved.
|Netreo can post a notification message in a specified Slack channel when an alert is triggered and when it is resolved.
|During every monitoring cycle, Netreo will push collected data into SQL Azure/SQL Server database of customers’ choice.
|Netreo can send a notification message as SMS using Twilio when an alert is triggered and when it is resolved.
|Any 3rd party product that is not explicitly covered in this list can still be integrated with by creating custom XML/JSON webhooks. Netreo can push notifications when an alert is triggered and when it is resolved.
|During every monitoring cycle, host status and metrics can be synchronized to Zabbix.
|Netreo can push a notification message to specified Zap in Zapier when an alert is triggered and when it is resolved.
|Netreo can open a new Zendesk ticket when an alert is triggered, and automatically close it when alert is resolved.
Trying Netreo is simple and hassle free. Typical setup takes 3-5 minutes and Netreo auto-detects everything it can monitor within user’s Azure subscription automatically. Sign up and see for yourself!