English
Afrikaans
Amharic
Arabic
Chinese (Simplified)
Dutch
Filipino
French
Georgian
German
Hausa
Igbo
Indonesian
Italian
Japanese
Javanese
Latin
Nepali
Portuguese
Russian
Somali
Spanish
Swahili
Thai
Ukrainian
Vietnamese
YorubaArchitecture of Agent-Based Setup
The agent-based setup consists of two main components at a high level:
- Agent
- AIOps Server
Motadata Docs
- AIOps
- Getting Started
- Flow Analysis
- Dashboards
- Monitors
- What is a Monitor?
- Monitor Settings
- Monitor Rediscovery
- Topology Scanner
- SNMP Device Catalog
- Process Monitoring
- Service Monitoring
- File and Directory Monitoring
- Configure the Monitoring Time-period
- Custom Monitoring Fields
- Configuring a Monitor Maintenance Window
- How to edit Monitor properties?
- How to Delete a Monitor?
- Integrations
- Agent-Based Monitoring System
- Log Management
- Plugin Management
- ServiceOps
- Technician User Guide
- Introduction
- Motadata Dashboard
- Request Management
- Overview
- Request List View
- Creating a Request
- Creating a Service Request
- Request Details Page
- Updating a Request
- Merging and Splitting Requests
- Marking Requests as Spam
- Assigning and Claiming a Request
- Archiving a Request
- Printing a Request
- Status and Assignment Transition
- Resolving and Closing a Request
- Work Conversations
- Tasks
- Adding Relations
- Adding Work Log
- Audit Trail
- Sending Email Notifications
- Integration
- Asking for Approval
- Asking for Feedback
- Adding Watchers
- Executing Scenarios
- Problem Management
- Change Management
- Release Management
- Overview
- Use Case
- Release List View
- Creating a Release
- Release Details Page
- Assigning and Claiming a Release
- Updating a Release
- Release Workflow
- Planning a Release
- Collaboration
- Asking for Approval
- Tasks
- Adding Relations
- Adding Work Log
- Audit Trail
- Sending Email Notifications
- Closing a Release
- Reopening a Release
- Archiving a Release
- Restoring Release
- Asset Management
- Contract Management
- Purchase Management
- Patch Management
- Package Management
- Project Management
- Knowledge Management
- Reports
- Approval Management
- Task Management
- Admin Section
- Overview
- Automation
- Users
- Organization
- Support Channels
- Request Management
- Service Catalog
- Problem Management
- Change Management
- Release Management
- Asset Management
- Overview
- Asset Types
- Asset Custom Fields
- Asset Status
- Asset Custom Rules
- Asset Groups
- SNMP Custom Properties
- Software Categories
- Software Types
- Relationship Types
- Asset Discovery
- Software Rules
- RDP Configurations
- Product Types
- Manufacturer Catalog
- Product Catalog
- Product Custom Fields
- Vendor Catalog
- Vendor Custom Fields
- Barcode
- IP Range Location
- Asset Movement
- Manage Baselines
- Variance Detection
- Wake On LAN
- Asset Configuration
- Contract Management
- Purchase Management
- Patch Management
- Project Management
- Knowledge Management
- User Survey
- Support User Guide
- Integration Docs
- Installation and Upgrade Document
- Introduction
- Prerequisite Guide
- Server Installation Guide
- Plugin Server Installation Guide
- High Availability
- Upgrade Guide
- Patch Installation Guide
- File Server Installation Guide
- DMZ Server Installation Guide
- Agent Installation Guide
- Remote Desktop Installation Guide
- Motadata ServiceOps WebRTC Installation Guide
- Poller Service Installation Guide
- Technician User Guide
Let us discuss the two major components in further detail.
- AgentAgent is installed on the server that you need to monitor. This unified agent has multiple capabilities that include metric polling, log forwarding, and more capabilities which we will see in the future.The agent has two major components which help in its functioning:
- .exe files (metric, log, and flow)These are executable files present in an agent that operate separately for each category, namely metric, log, and flow. They are a set of specialized executable files that run on each host monitored using an agent. They collect the relevant metrics from the system on which they run. These files then move the collected data to the agent manager for further processing.
- Agent ManagerThis is a service running on every host that has an agent installed on it. It is responsible for data collection, storing, and moving the data received from all the exe files to the master AIOps server. At the same time, it is also responsible for communicating the UI-level configuration changes made by the user in the agent to all the executable files.
- AIOps ServerThis is the master server where AIOps is installed. The data collected by the agent are then passed onto the AIOps via the agent manager. This server is the centralized location where you can view and analyze the data from all the hosts monitored by agents.
