Web Player metrics to monitor (advanced)
These more advanced Spotfire Web Player metrics can help you determine if your Spotfire implementation is appropriately sized.
Metric | Location |
---|---|
Memory health status | On the Instances page, select the
Web Player instance on the left.
These metrics are under Performance counters. For more information, see Web Player and Automation Services resource usage. |
Processor health status | |
Web Player open documents | |
Web Player cached documents | |
Concurrent users | |
Memory in all .NET heaps (Number of bytes in all heaps) | |
Data engine memory | |
Data engine query cache memory | |
Data engine paged out memory | |
Data engine paged in memory | |
Private data table size ("Private bytes") | Under Information, click View details. |
What to look for
Note: Web Player instances that are used for scheduled updates are
often in the "Exhausted" state. This is expected behavior. For more
information, see
Basic Troubleshooting, and
Services monitoring.
Web Player open documents and Web Player cached documents values that are higher than expected based on the use pattern.
Paging out memory is acceptable as long as the temp disk is not filled up. However, if large amounts of data is paged in very often, the RAM size might need to be upgraded.
Parent topic: Services monitoring