ArcGIS Monitor is an enterprise-grade monitoring solution that works with ArcGIS Enterprise by providing information about system health, usage, and performance. It captures key metrics and attributes to quantify system health over time, helping you maximize your GIS and IT investment. Monitor also aggregates system-level data into actionable information to help identify problems before they affect users and raises awareness to operations teams. This information can also be used by GIS administrators to maintain the operational health and performance of your enterprise GIS implementation or by managers to analyze long-term trends.
Software architecture
ArcGIS Monitor consists of the following components:
- ArcGIS Monitor Server provides a web interface that serves as the central hub for analyzing monitored environments, configuring monitoring, configuring settings, and managing users and permissions.
- ArcGIS Monitor Agent collects data from registered components on the machine on which it's installed. Data collected by Monitor Agent is sent to the Monitor Server installation to which it's registered for centralized data reporting and analysis.
- The Monitor database repository stores system settings and all data metrics. It is recommended that you create a dedicated database and user for Monitor. Once Monitor Server is connected to the database, it manages the creation of the ArcGIS Monitor Information Model and the maintenance of its schema.
Roles
Roles in Monitor are configured to allow for varying degrees of access in Monitor depending on each user’s duties in an organization. Depending on the size of the organization, these roles may be performed by one user or several users. Monitor includes the following purpose-built roles:
Administrator—Administrators can manage Monitor system settings, users, and all aspects of monitoring an enterprise GIS implementation.
Manager—Managers can manage all aspects of monitoring an enterprise GIS implementation but don't have access to Monitor system settings and can't add and manage users.
Viewer—Viewers can view alerts and analyze long-term trends in an enterprise GIS implementation but can't register components, make changes to monitoring, or change Monitor system settings.
Essential terminology
The following is a list of essential Monitor terminology:
Alerts
Alerts serve as the primary method for tracking the health, usage, and performance of registered components. Alerts are created for registered components when their metric values fall outside of specified alert rule threshold values. When an alert is created, its status and state appear on the Alerts page.
Analysis
Analysis allows you to create views that help answer broad, large-scale questions about the overall health, usage, performance, and inventory of an organization's enterprise GIS implementation. Analysis views can also be used to identify specific issues and identify correlations between key data, such as related alerts and metric values.
Collections
Collections are groups of components that you create to organize components into logical groups that serve as the foundation for metric data analysis, service level agreement calculations, notifications, and incidents. Collections can be created for specific environments, such as production, staging, or development, and for specific types of components, such as databases, hosts, or ArcGIS software. You can also create notifications and webhooks for collections and enable feature services to make collection data available for use in other ArcGIS applications, such as ArcGIS Dashboards.
Components
Components are the hardware and software resources that comprise your enterprise GIS implementation. When components are registered, they are actively monitored at set intervals. Each component contains attributes and metrics specific to its type, and some components contain subcomponents. For example, an ArcGIS Enterprise portal contains a GIS server and has web services.
Dataviews
Dataviews are data query compositions that are used by Analysis view elements to create visualizations that help you observe, identify, and troubleshoot issues that are unique to your system architecture and environments. Monitor includes several system dataviews that power many of the system displays in Monitor. If the resources that you want to visualize aren't available in the system dataviews, you can create custom dataviews to join and filter data to meet the specific needs of your organization.
Incidents
Incidents can be used to schedule maintenance tasks for a collection of monitored components. Reminder emails can be configured and sent to the collection's subscribed users to notify them of incidents.
Observers
Observers are background processes that are responsible for collecting attribute and metric data for registered components. Each component type has a unique set of observers that monitor critical aspects of the component.
Metrics
Metrics are properties with corresponding numerical values that can be used to track various aspects of an environment and its components over time. Alert rules can be individually configured for the component's metrics to notify Monitor administrators when metric values are outside of a predefined set of threshold values.
Notifications
Notifications inform users of specific events and changes to the monitored environment, such as an alert for low system resources on a host component or an upcoming incident for scheduled maintenance. You can subscribe to Monitor resource events, events for any resource across the monitored environment, or events for a single collection and send notifications about those events using email or webhooks.