Eyer.ai simplifies Azure Monitor setup and management. Here's what you need to know:
- Eyer.ai works with Azure Monitor to track cloud resources
- It helps set up monitoring, choose metrics, and create alerts
- Key benefits: early problem detection, cost reduction, and improved security
Quick setup guide:
- Download and install Eyer.ai
- Connect to your Azure account
- Select resources to monitor
- Set up data collection rules
- Create alert rules
- Use the dashboard for analysis
| Feature | Eyer.ai Benefit |
|---|---|
| Easy setup | Simplifies Azure Monitor configuration |
| Custom metrics | Track business-specific data points |
| User-friendly interface | Accessible for non-technical users |
| Automated analysis | Quickly identifies root causes |
| Real-time data | Provides up-to-date resource information |
Eyer.ai makes Azure monitoring straightforward, helping you catch issues early and make smarter cloud decisions.
Key parts of Azure Monitor
Azure Monitor is your all-in-one tool for cloud management. Here's what it offers:
Main components
1. Metrics
These are your cloud's vital signs. They show:
- CPU usage for VMs
- Disk I/O for databases
- Network traffic for web apps
Azure Monitor collects these automatically. You can view them in real-time or over time.
2. Logs
Think of logs as your cloud's diary. They record:
- App errors
- Security events
- System changes
Azure Monitor Logs stores all this data. You can search, analyze, and set alerts based on it.
3. Alerts
Your early warning system. Set rules, and Azure Monitor watches for them. When triggered, you can:
- Get notified
- Run an Azure Function
- Create an ITSM ticket
Here's how they work together:
| Component | Function | Value |
|---|---|---|
| Metrics | Collect performance data | Spot trends and issues |
| Logs | Record detailed events | Deep analysis and troubleshooting |
| Alerts | Notify on specific conditions | Proactive problem-solving |
Benefits for cloud management
Azure Monitor isn't just a dashboard. It's a game-changer:
- Catch problems early: Track metrics and logs to spot issues before they escalate.
- Cut costs: Right-size your resources based on actual usage.
- Boost security: Spot suspicious activities in your logs.
- Automate responses: Set up automatic fixes for common issues.
- Plan smarter: Use long-term trends to make better scaling decisions.
It's like having a super-smart assistant watching your cloud 24/7, ready to help when needed.
Getting ready to use Eyer.ai with Azure Monitor
Let's walk through the setup process for Eyer.ai with Azure Monitor.
What you need to run Eyer.ai
You'll need:
- Windows 10 RS4 or higher
- C++ Redistributable (2015 or newer)
- 10 GB free disk space
Here's where that space goes:
| Purpose | Environment | Path | Space Needed |
|---|---|---|---|
| Package installation | Windows | C:\Packages\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent | 500 MB |
| Extension Logs | Windows | C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent | 100 MB |
| Agent Cache | Windows | C:\WindowsAzure\Resources\AMADataStore.{DataStoreName} | 10.5 GB |
Required Azure permissions
You'll need:
- Azure RBAC: A role for creating and managing Azure resources.
-
Cognitive Services: For Azure OpenAI, you need one of these:
- Cognitive Services OpenAI User
- Cognitive Services OpenAI Contributor
- Cognitive Services Contributor
- Key Vault: Owner or contributor access (for customer-managed keys).
Setting up Azure
- Turn on managed identity for your Azure VMs.
- Create a Data Collection Rule (don't link it yet).
-
Make sure you can reach these HTTPS endpoints:
- global.handler.control.monitor.azure.com
<virtual-machine-region-name>.handler.control.monitor.azure.com<log-analytics-workspace-id>.ods.opinsights.azure.com
- Domain-join your device to a Microsoft Entra tenant.
Installing Eyer.ai
Let's get Eyer.ai set up for Azure monitoring. Here's how:
Download
- Go to eyer.ai
- Find "Downloads"
- Pick the Windows 10 RS4+ version
- Hit download
Install
Got the file? Great. Now:
- Find it (probably in Downloads)
- Right-click, "Run as administrator"
- Follow the wizard
- Pick where to install (default's fine)
- Choose components (for Azure, select all)
- Click "Install"
Heads up: You'll need 10 GB of free space.
Check It's Working
After install:
- Start menu > "Eyer.ai"
- Look for the icon in your system tray
- Right-click > "About" to see the version
Stuck? Check Eyer.ai docs or hit up their support team.
2. Linking Eyer.ai to Azure
Let's connect Eyer.ai to your Azure resources. This is key for setting up monitoring.
Login Options
You've got two ways to connect:
- Microsoft Entra ID (recommended)
- API Key
Setting Up
For Microsoft Entra ID:
- Open Eyer.ai
- Go to Settings > Azure Connection
- Pick "Microsoft Entra ID"
- Enter your Azure tenant ID, client ID, and client secret
For API Key:
- In Eyer.ai, head to Settings > Azure Connection
- Choose "API Key"
- Put in your workspace ID and API key
"To access the Azure Monitor Log Analytics API, you need to register a client app with Microsoft Entra ID and request a token." - Azure Documentation
Test It Out
After entering your details:
- Hit "Test Connection" in Eyer.ai
- Wait a bit
- Green checkmark? You're good to go
- No luck? Double-check your info
Make sure your app has the right permissions. Azure says: "Ensure that your app has the necessary permissions to use the Log Analytics API by selecting the appropriate delegated permissions."
3. Choosing what to monitor
Let's dive into picking what to keep tabs on in Azure using Eyer.ai. We'll break it down into three key steps:
Picking resources to watch
First, identify your crucial Azure resources. These might be:
- Virtual Machines
- Storage Accounts
- Databases
- Networking Resources
Focus on what directly impacts your app's performance and user experience. Running a web app? Keep an eye on your web server VMs and database performance.
Adjusting settings
Now, let's fine-tune your monitoring. In Eyer.ai:
- Hit the "Resources" tab
- Pick your resource
- Click "Configure Monitoring"
Here's where you set:
- How often to check
- How long to keep data
- Which metrics matter most
For a VM, you might track CPU usage, memory, and disk I/O.
Setting up custom metrics and alerts
Need something specific? Custom metrics are your friend.
To set one up:
- Go to "Custom Metrics" in Eyer.ai
- Click "Add New Metric"
- Define it (like number of active users)
- Choose how to collect data
Now for alerts:
- Head to "Alerts"
- Hit "Create New Alert Rule"
- Pick your resource and metric
- Set your conditions
For instance, alert when a VM's CPU hits 80% for over 5 minutes.
| Alert Part | What It Is | Example |
|---|---|---|
| Resource | What to watch | Web Server VM |
| Signal | What to measure | CPU Usage |
| Threshold | When to act | > 80% |
| Time Window | How long it's true | 5 minutes |
| Action | What happens | Email sent |
"To create an alert rule, combine the resources to be monitored, the monitoring data from the resource, and the conditions that trigger the alert." - Azure Documentation
Remember: Balance is key. Too little monitoring misses issues. Too much? Data overload.
4. Setting up data collection
Let's dive into setting up data collection in Eyer.ai. This step is crucial for getting the right info when you need it.
What Eyer.ai collects
Eyer.ai uses Azure Monitor to grab:
- Platform metrics
- Activity logs
- Service health info
- Alerts
- Log analytics
This mix gives you a 360-view of your Azure resources.
Creating data collection rules
Data Collection Rules (DCRs) are the heart of Eyer.ai's data gathering. Here's how to set them up:
- Open Eyer.ai
- Hit "Data Collection"
- Click "Create New Rule"
- Pick your data source
- Choose your metrics or logs
- Set any tweaks or filters
- Pick where to send the data
For a web server VM, it might look like this:
| Data Source | Metrics | Logs | Destination |
|---|---|---|---|
| Web Server VM | CPU Usage, Memory, Disk I/O | IIS Logs, Windows Events | Log Analytics workspace |
How often to collect
You need to balance detail and system load. Here's a quick guide:
| Resource Type | Collection Frequency | Why? |
|---|---|---|
| Critical VMs | Every 1 minute | Catch issues fast |
| Standard VMs | Every 5 minutes | Good middle ground |
| Storage accounts | Every 15 minutes | Metrics change slower |
| Databases | Every 2 minutes | Spot performance hiccups |
More frequent collection = more data and potentially higher costs. Start here and tweak as needed.
Pro tip: Use the Azure Monitor DCR Config Generator tool to kickstart your DCRs. This PowerShell script can save you time and catch any data points you might miss.
sbb-itb-9890dba
5. Setting up alerts
Let's dive into setting up alerts in Eyer.ai for Azure Monitor. It's crucial for keeping tabs on your cloud resources.
Making alert rules
Here's how to create an alert rule:
- Open Eyer.ai
- Go to "Alerts"
- Hit "New Alert Rule"
- Pick resources to monitor
- Set the trigger condition
- Choose actions for when it's triggered
For instance, to watch a critical VM's CPU:
| Resource | Metric | Condition | Time | Action |
|---|---|---|---|---|
| VM-PROD-01 | CPU Usage | > 90% | 5 minutes | Email IT team |
Setting alert limits
Think about these when setting limits:
- Resource type
- Importance
- Normal behavior
Quick guide:
| Resource | Metric | Warning | Critical |
|---|---|---|---|
| VM | CPU | > 80% | > 90% |
| Database | DTU | > 70% | > 85% |
| Storage | Latency | > 100ms | > 250ms |
Choosing how to send alerts
Eyer.ai offers these notification options:
- SMS
- Voice call
- Webhook (for custom integrations)
Pick what works for your team. For urgent stuff, use multiple channels.
"We use email for non-critical alerts and SMS for immediate attention. It's cut our response time by 50%", says Sarah Chen, DevOps Lead at TechCorp.
6. Understanding monitoring data
Using the Eyer.ai dashboard
The Eyer.ai dashboard is your monitoring command center. Here's how to use it:
- Get a quick overview of your resources
- Use filters to zoom in on what matters
- Create custom views for your go-to data
Reading metrics and logs
Eyer.ai grabs two main data types from Azure:
| Data Type | What is it? | When to use it |
|---|---|---|
| Metrics | Numbers collected regularly | Spot performance issues fast |
| Logs | Detailed event records | Dig deep into problems |
For metrics:
- Look at trends, not just single points
- Compare now vs. then
- Watch for sudden changes
For logs:
- Use KQL to slice and dice data
- Hunt for errors and weird stuff
- Connect the dots between logs and metrics
Spotting patterns and unusual events
To catch issues before they blow up:
- Know what's "normal" for your resources
- Let Eyer.ai flag the weird stuff
- Look for repeating patterns
"Eyer.ai's ML smarts helped us catch problems 30% faster than before", says Alex Chen, TechSolutions Inc. CTO.
Keep an eye out for regular spikes or dips - they might point to tasks you can tweak.
Fixing common problems
Using Eyer.ai with Azure Monitor? Here's how to tackle the most common issues:
Connection issues
Can't connect to Azure? Try this:
- Double-check your Azure login
- Confirm your permissions
- Test the connection again
Still no luck? Log out and back in.
Data collection problems
No data flowing? Here's what to do:
- Review your data collection rules
- Check your collection frequency
- Run this query to check for daily limit issues:
Operation | where OperationCategory == 'Data Collection Status'
A "Warning" status? You've probably hit your cap. Think about upgrading or tweaking your settings.
Alert setup troubles
Alerts acting up? Follow these steps:
- Go over your alert rules
- Check your alert limits
- Test your action group
| Issue | Fix |
|---|---|
| No notifications | Check email filters and action group settings |
| Alert overload | Adjust thresholds or combine similar alerts |
| Slow alerts | Review data collection frequency |
Keep in mind: There's a 100/hour limit for email alerts per address. SMS and voice calls? One every five minutes per number.
Still stuck? Eyer.ai's support team is ready to help you get your monitoring back on track.
Tips for using Eyer.ai with Azure Monitor
Speed Things Up
Want to make Azure Monitor work faster with Eyer.ai? Here's how:
1. Optimize your queries
Filter early and skip evaluated where clauses. Your queries will run WAY faster.
2. Aggregate smartly
When using summarize and join, pick your dimensions carefully. It'll save your CPU a headache.
3. Don't scan everything
Add TimeGenerated filters to ALL subqueries. It keeps your resource use in check.
| Tip | What It Does |
|---|---|
| Early filtering | Processes less data |
| Skip evaluated where clauses | Keeps queries fast |
| Smart aggregation | Uses less CPU |
| TimeGenerated filters | Scans less data |
Lock Down Your Data
Keep your monitoring info safe:
- Use TLS 1.3 (at least) for your agent
- Set up customer-managed keys for more control
- Put data locks on your Log Analytics workspace
Keep Things Running Smooth
Don't forget to:
- Check your security settings often
- Watch for idle resources and cut them loose
- Set up alerts for weird stuff
- Look at how your resources are doing over time
Conclusion
Let's recap how to use Eyer.ai with Azure Monitor:
- Download and set up Eyer.ai
- Connect it to your Azure account
- Pick your Azure resources to monitor
- Set up your data collection
- Create your alerts
- Use the dashboard to analyze your data
Why bother with Eyer.ai? It makes Azure Monitor better:
| Feature | What it does for you |
|---|---|
| Custom metrics | Track what matters to your business |
| Easy-to-use interface | Non-techies can use it too |
| Auto root cause analysis | Find and fix issues fast |
| Real-time data | Get the latest on your Azure resources |
With Eyer.ai and Azure Monitor, you can:
- Catch problems early
- Make smarter decisions
- Save on cloud costs
It's that simple.
FAQs
How do you implement monitoring in Azure?
Setting up monitoring in Azure is straightforward:
- Open Azure portal
- Search for "Monitor"
- Click "Monitor" in results
- Choose "Log Analytics" from the menu
- Select a workspace to start
Here's how to create alerts from log data:
| Step | Action |
|---|---|
| 1 | Go to "Alerts" in Monitor menu |
| 2 | Click "Create > Alert Rule" |
| 3 | Choose resource scope |
| 4 | Set alert logic in "Conditions" |
| 5 | Set up notifications in "Actions" |
| 6 | Name alert and set severity in "Details" |
| 7 | Click "Review + Create" |
Adjust thresholds as needed. Too many alerts? Increase the threshold. Missing issues? Lower it.
"Azure Monitor is available out of the box once you have an active subscription in Azure", - Microsoft documentation
Costs to consider:
- Basic alert rule: ~$0.1/month
- Dynamic Threshold rule: ~$0.2/month
- Email notifications: ~$2/month per 1,000 emails
