ArcGIS Monitor: An Introduction...ArcGIS Monitor: Why? •Need end to end monitoring for effective...
Transcript of ArcGIS Monitor: An Introduction...ArcGIS Monitor: Why? •Need end to end monitoring for effective...
Andrew Sakowicz
ArcGIS Monitor: An Introduction
Agenda
• Motivation and audience
• Use cases
• Installation and Configuration
• Key features
- Health
- Alerts
- Availability
- Usage
- Performance
- Root Cause Analysis (RCA)
• 2020 Improvements
ArcGIS Monitor: Why?
• Need end to end monitoring for effective diagnostics
• Standard monitoring tools:
- Focus primarily on infrastructure
- IT controlled
- No ArcGIS components
- Low success of ArcGIS troubleshooting
- Integrating “ArcGIS” has challenges and high LOE
Optimize Your Enterprise GIS Deployments
Average cost of IT downtime is $5,600 per minute. Source: Gartner
ArcGIS Monitor: Why?Optimize Your Enterprise GIS Deployments
• Customers require:
- Faster resolution time
- Better performance
- Lower cost of administration
- End-user satisfaction
• Dozens of components
• Hundreds of discreet metrics
• Which metrics are important?
• Filter the signal from the noise
• ArcGIS Monitor
- Tailored for ArcGIS
- Non-invasive sampling
- Minimal resource footprint
- Conforms to the environment
- Single or multi-datacenter
The Monitored EnvironmentGrowing in complexity
ArcGIS Enterprise
FederatedGIS Server
RelationalDatabase
+ArcGIS Pro users License Manager
GeoEventServer
SpatiotemporalData StoreArcGIS
Monitor
Hosting GIS Server
Relational & TileData Store
Portal
for ArcGIS
Web
Adaptor
Web
Adaptor
Denver
London
Tokyo
Key features
• Monitors Enterprise components and
underlying infrastructure
• Low level data summarized to
meaningful and actionable information
CPUMemoryDiskNetworkEvents
Hardware
Software
Services Response TimeBusy TimeThroughputSOC Usage
Health ChecksLog EntryUsage StatisticsConfigurationSecurity
ArcGIS Monitor:• Health
• Performance
• Usage
USAGE
Target Audience
RCA
• Administrators:
- Alerts
- Root Cause Analysis (RCA)
• Managers:
- Availability
- Performance
- Usage
• Developers:
- errors analysis
- customization
Alerts
Error Analysis
Availability
Simple use case
Problems: Points “disappeared” from a mapFirst noticed around 7 am
Golf Courses points
“disappeared”
Select RCA for this time rangeAnalyze Sources and click on Log error messages
Analyze error message
Investigate “Source” machine
Problem: ArcGIS Data Store
service not running.Restarting service throws
logging error.
Resolve: correct password and start ArcGIS Data Store service
✓
Verify resolution
✓
Points are visible
https://enterprise.arcgis.com/en/monitor/latest/get-started/arcgis-
monitor-system-requirements.htm
Installation
Single machine deployment
Distributed deploymentFull stack monitoring
Monitoring service
Configuration
Review your solution(s) architectureExamples
Portal
for ArcGIS
Hosting
Server
ArcGIS
Data Store
(relational + tile cache)
Web Adaptor
GeoEvent
Server
ArcGIS
Server
Gallery: Tutorials and Videos
https://arcgismonitor.maps.arcgis.com
Gallery: Select required Extensions
https://arcgismonitor.maps.arcgis.com
Extensions examples
License InventoryWhat and how many licenses do we have?
Number of UsersHow many unique users were there
during this time period?
User NamesWho were the specific users during
this time period?
% of Licenses UsedWhat percentage of the licenses were used during this time period?
ArcSOC OptimizerSetting min / max instances across 100 to 1000s of services
in dynamic environments is challenging
ArcSOC Optimizer
• Decrease or increase instances, based on:
• 1. historical usage
• 2. available memory and process count
Alerts
AlertsStarting point for troubleshooting
Charts and Stats Details and Logs Source Urls Admin Url
Availability
Availability
• Availability is usually expressed as a percentage of uptime in a given time span
(typically 1 month) and calculated as follows:
Availability (%) = (Total time – Downtime) / Total Time *100%
• ArcGIS Monitor defines downtime based on a critical alert duration.
Availability
• In the case below, in January 2019:
- Total Time= 31*24 = 744 hours (44640 minutes) , see Duration H:M; the total downtime
- Downtime = 47 hours and 24 minutes (2844 minutes), see Non Availability H:M).
- Availability (%) = (44640-2844)/44640*100=93.629%
Usage
Usage
• Usage (or user load) is typically measured using:
- Transactions or requests per time, e.g. per seconds, 5 min, day.
- User IP per time, e.g. per seconds, 5 min, day.
- Users per time, e.g. per seconds, 5 min, day.
• Measured at:
- Load balancer (LB)
- Web server
- ArcGIS Server
- Database
• Format:
- Chart time series
- Table
- Map
Usage at LB: transactions (or requests)Categories > Usage > Tr/Interval
• Chart format
Performance
Performance at LBReports > Usage > Response Time (sec)
Performance at ArcGIS ServerCategories > ArcGIS > Busy Time per Tr (sec)
• Busy Time per Tr (sec) is the total time (seconds) per transaction consumed by
ArcGIS Server service.
Root Cause Analysis (RCA)
Typical cases and
Root Cause Analysis (RCA)“Source” - the most downstream failing component
“Impact” – all upstream failing components
Portal
for ArcGIS
Hosting
Server
ArcGIS
Data Store
(relational + tile cache)
Web Adaptor
GeoEvent
Server
ArcGIS
Server
“Impact”
Portal
for ArcGIS
Hosting
Server
ArcGIS
Data Store
(relational + tile cache)
Web Adaptor
ArcGIS
Server
“Impact”
GeoEvent
Server
Example 1 Example 2
“Source”
“Source”
Overloaded systemLoad exceeds the designed capacity
Source Impact
RCA: Usage spike Throughput (tr/s)
Bottleneck
Source Impact
RCA: Free instances = 0 Bottleneck are often created by increased load
Unstable InfrastructureInterruption to the underlying resources
Source Impact
RCA: CPU spike by unexpected process, e.g. virous scan
RCA: Portal for ArcGIS Server service stopped
RCA: ArcGIS Server machine rebooted
RCA: Database not running
Demo sitehttps://arcgismonitor.esri.com/
2020 improvements and beta
program
Auto-discovery demo
PostgreSQL, SQL Server , Oracle
• Power BI integration
- through relational database schema
ArcGIS Rest API: Portal, Ops Dashboards and Esri JS applications
ArcGIS Rest API
Portal item
Operation Dashboard
Webhooks
ArcGISMonitor
Webhooks
Webhooks Demo
Print Your Certificate of Attendance
Print Stations Located in 150 Concourse Lobby
Tuesday12:30 pm – 6:30 pm
Expo
Hall B
5:15 pm – 6:30 pm
Expo Social
Hall B
Wednesday10:45 am – 5:15 pm
Expo
Hall B
6:30 pm – 9:30 pm
Networking Reception
Smithsonian National Museum
of Natural History
Download the Esri
Events app and find your event
Select the session
you attended
Scroll down to
“Survey”
Log in to access the
survey
Complete the survey
and select “Submit”
Please Share Your Feedback in the App