Browse Articles

Welcome
- Welcome to Monitoring
- Getting Started
- Overview and Features
- System Requirements
Account Management
- Companies
- Users & Permissions
- Contacts & Contact Methods
- Account Settings
Web Account
- Introduction to your Monitoring Web Account
- Multiple Companies
- Multiple Users
- Charts and Graphs
- About the Search Index
- About Dashboards
- Setting Up Dashboards
- Notifications
Applications
- About Monitoring Applications
- Inventory Application
- Alerting Application
- Remote Support Application
- Data Collection Application
- Reports Application
- Server Health Application
- Logs Application
- Automation Application
- Netflow Application
- WSUS Patch Reporting Application
- VMware Application
- Zendesk Application
- XenServer Application
Data Collection
- GoToAssist Setup Assistant
- About Data Collection
- LAN Data Collection (Crawler)
- Off-LAN Data Collection
- Internet Services Testing
- About the Crawler
- Configuring Crawler Credentials
- About Crawler Plugins
Community
- Community
- About Forums and Discussions
- About Share-Its
- User Profiles
Search
- Introduction to Search
- Basic Search
- Search Shortcuts
- Advanced Search
- Using Search Templates
- Nested Search
For Developers
- For Developers
- GoToAssist Developer Tools
- Developing Applications
- GoToAssist API
- Ontology
- About Databases
- Database Concepts
- Straddling Dual Databases
- Tree-Structured Database
- Application Tutorial
- Writing Crawler Plugins
About PQL
- About GoToAssist Query Language (PQL)
- GoToAssist Query Language (PQL) Overview
- PQL Index
- PQL Keywords
- Data Types
Using PQL
- Alternatives
- Subqueries
- Expressions
- Regular Expressions (REGEX)
- Boolean Expressions
- Ephemeral Nodes
- Floating Points
- Identifiers
PQL Functions
- PQL Functions
- Join Function
- History Function
- PQL nvl and coalesce Functions
- Abbreviate Function
- Zip Function
- ID Function
- Available_history Function
- Cast Functions
- Child Function
- Created_at Function
- PQL downcase, lower, upcase and upper functions
- First Function
- Raw_history Function
- Format Function
- Regex Function
- Substring Function
- Has_history Function
- Aggregate Functions
- Num_children Function
- Observed_at Function
- Parent Function
PQL Statements
- Statements
- SELECT
- MERGE
- INSERT
- UPDATE
- DELETE
PQL Clauses and Values
- FROM clause
- WHERE clause
- NULL value
- True and False
PQL Operators
- Operators
- AND operator
- NOT operator
- OR operator
PQL Paths
- Paths
- Path Scoped Predicate
- Path Scoped Projection
- Qualified and Unqualified Paths
PQL Tutorials
- Writing simple queries using SELECT and FROM
- Writing queries using the WHERE clause
- Writing queries that extract historical values
- Writing basic queries
Examples
- Examples
- Examples for Sample Databases
- Examples Historical Data
- Examples IT scenarios
- Creating a dashboard NOC
- Query Examples
- Query Sandbox
- Sample Data and Fictitious Database
Corner Examples
- Corner Examples
- Audit software
- Track Traffic
- Find users
- Inventory management
- Monitor Servers
- More things you can do with GoToAssist
FAQs
- GoToAssist Monitoring FAQs
- WMI Errors and Solutions
Glossary
- Glossary

Application Tutorial

Three-layer mashup app

This tutorial is based on the GoToAssist Alert and GoToAssist Inventory applications, which work as web services consisting of three layers:

A user interface is provided by a flash application running in a browser. The application requires a tree that is clipped to certain bounds, zoomed to a certain level from the server, which it renders in a canvas on the browser. The application contains controls for zooming, panning, selecting nodes, and specifying queries that result in the resulting nodes being selected and visible in its viewport.
An application that queries the backend for the network hierarchy, with hinting on what to fetch by the clipping request from the flash client. This second layer links the nodes into trees and applies a layout to the resulting trees. This result is cached for efficiency. It then delivers the list of nodes that match its clipped request to the client, with a limited amount of meta information about the nodes. The client may also request additional information about any individual node.
The third layer is the core GoToAssist system, which the other layers access via the GoToAssist API.