Panopta offers native integration with Azure Monitor, enabling Panopta to ingest your Azure monitoring data. As well, Panopta can perform automatic discovery and monitoring of instances within your Azure account. This is configurable by service type and region, and can also be fully customized using your Azure tags.
Azure data should be used as an augmentation of, not a replacement for, the data obtained by the Panopta server agent and external monitoring. The server agent can provide more detailed and accurate data across any OS distribution or application you may be running on your compute instance. As well, our external monitoring ensures you're getting the full picture of your current operating environment as well as a view into what your customers are experiencing.
On this page
Connecting Panopta and Azure
To grant Panopta access your Azure Monitor data, you'll need to create a service account within your Azure account that grants Panopta read-only access.
- Click the
+ Add button in the global navigation bar at the top of your screen. From the Catalog Modal that appears, select
- On the Cloud Monitoring splash page, select
- Follow the on-page instructions to create an Azure service account Panopta to utilize.
- Once you've obtained your
App ID and
- Once your
App ID and
Password have been validated, you can configure your monitoring settings.
- Service Filtering: select the Azure services you'd like to monitor. It's better to only select the ones you're using, otherwise it uses vital API calls
- Instance Filtering: you can choose to only import instances that match the Azure tag filters you define
- Regions: we encourage you to only select the regions you operate in
- Options - Tag Import: enabling tag import will pull in your Azure tags with your Azure instances
- Options - Routine Scan: every 20 minutes, we'll look for new instances in your account and will begin monitoring them assuming they meet your filter criteria. Virtual Machine instances using the Panopta agent can be monitored immediately if you install the agent on boot.
- Options - Destination Group: any time instances are imported, they'll be placed in this group in the control panel. This is great for setting default values which are inherited from their parent group as well as apply default templates
- Options - Template: apply a template to every instance that's imported
Import. We'll start pulling in your instances which meet your filter criteria and begin monitoring them.
API Limits and Throttling
By default, each Azure account gets 1M Azure Monitor API calls per month for free. When Panopta makes Azure calls to obtain metrics (every 10 minutes), it utilizes your API calls quota. We encourage you utilize the Panopta agent on Virtual Machine instances, not only for the cost savings, but also the increased functionality and granularity. You can read more about it here.
Once you exceed 1M Azure Monitor calls for the month, Microsoft will charge your account $10 per 1M calls. You can read more about their pricing here.
In certain large-scale scenarios, Azure could begin throttling API calls. We will begin backing-off at that time. If you expect to utilize close to or the full 1M calls per month, we recommend reaching out to Azure to ask for a limit increase. If you'd like Panopta to collect Azure metrics more often than every 10 minutes, please email firstname.lastname@example.org. As well, you can override this at the metric level by editing the metric. Check out templates to do this in bulk.
If you're running the agent (Linux version > 2017.40, Windows version > 18.34), Virtual Machine metrics will be automatically added to your existing agent-based instances.
Example: if you have a Linux Virtual Machine instance you're already monitoring with the agent, and the agent version is > 2017.40, we won't create a second "Virtual Machine" instance with the Azure Monitor connection - the new Azure Monitor metrics will be added to your existing instance
Virtual Machine Incident Confirmation
If you're monitoring a Virtual Machine instance with external checks - such as HTTP, HTTPS, or Ping - and we identify an incident, we'll first confirm with Azure that the instance is still around. If it was gracefully removed, we will not alert. If the instance was not removed gracefully, we will alert as normal.
The following Azure integrations are supported:
- Azure Apps
- Azure Cache (Redis)
- Azure Data Warehouse
- Azure Document Database
- Azure Functions
- Azure MySQL
- Azure SQL
- Azure Storage Blob
- Azure Storage File
- Azure Storage Queue
- Azure Storage Table
- Azure Storage
- Azure VM