Axibase Warehouse Designer. Overview

Transcription

1 Axibase Warehouse Designer Overview

2 Reporting Overview Types of reports (by usage) capacity planning and performance analysis Capacity planning identifies trends Performance analysis identifies outliers Types of products (by integration) generic, role-specific, application-specific Types of products (by architecture) document, model, component Document Model Component Crystal Cognos BIRT Jasper Primeur QuickReporter Tivoli Common Reporting TeamQuest Hyperformix Tivoli Performance Analyzer Axibase Warehouse Designer

3 Reporting Objectives Need to deliver targeted reports to system owners, capacity managers, and management App1 App2 App3 App-n Report1 Report2 Report3 m x n reports Report-m

4 Challenges The number of required reports increases exponentially with the size of the environment servers apps t1 apps other apps metrics , , ,000 10, ,000 5,000 4,000 3,000 2,000 1, ,000 5,000 10,000 Assumptions: - 20 servers per application. 20% apps are Tier 1, 80% are Other. - Each application report contains 20 key metrics for Tier1 and 5 key metrics for Other applications.

5 Component Architecture Scheduled templates generate charts and statistics for all servers monitored by ITM Components are stored in AWD and assembled into reports at runtime, per user request m templates are required to cover the entire environment (irrespective of servers count) Template1 App1 App2 App-n Template2 Template3 m templates Template-m

6 AWD Overview Axibase Warehouse Designer is an application-specific reporting tool for ITM 6.x and TDW 2.1 Delivers reports on ITM-managed resources using a simplified, web-based user interface Architecture: component-based (statistics, charts, analytics) Unlike document-centric tools, AWD assembles reports from components at runtime - based on user permissions and user preferences.

7 Architecture - Basic ITM6.1 TEMS/TEPS/TDW support according to the latest IBM support matrix ITM6.2 Axibase was part of the beta-testing program. AWD deployment options: Windows/Linux. Self-managed embedded configuration and statistics database. Protocols: JDBC for database connectivity, SOAP for TEMS web services queries. Client requirements: IE/Firefox/Opera

8 Architecture - Advanced Multiple concurrent adapters for isolated and shared TEMS, TEPS, TDW installations Consolidation of reports form multiple TEMS servers into global reports Single point of access to historical and real-time reports irrespective of data/tema location Rank, violation, and multi-server reports across multiple TEMS servers, transparently to the user Enterprise Scenario Service Provider Scenario

9 Enterprise Features Integration with multiple HTEMS/TDW servers for single point of access Single sign-on (SSO) with TEPS accounts and permissions HTTP API for integration with TEPS workspaces, intranet portals and third-party tools Query-based grouping of ITM agents into custom resource groups (by OS, IP address, etc.) Report filtering by application, resource group, MSL Administrator- and user-managed dashboards

10 Ad-hoc Designer Very simple workflow select server agent table attribute interval Real-time instance lookup (disk names, QM names, database names) Calendar, raw data, statistics, trending, 100+ graphics properties Server Agent Table Attribute(s) Instance(s) Interval

11 Host Reports Single server view across multiple TEMAs (OS, DB, applications, UA) Drill-down into ad-hoc designer for additional customization Filter hosts by MSL, resource group, application Typical use case: At a glance view of key performance metrics on a particular server

12 Multiple Host Reports Multi-host graphs across TEMAs of the same type installed on different servers Customized time interval, list of targets Typical use case: Compare performance across a group of servers

13 Rankings Ranking of TEMAs by attribute value and metric: average, min, max, mean, forecast, percentiles Filter ranks by MSL, resource group, application Filter ranks by metric value, standard deviation, slope, intercept Typical use case: Identify outliers. Underperforming and underutilized servers (virtualization/ consolidation candidates). Overloaded or resource-constraint servers (running out of disk space).

14 Violations Ranking of TEMAs by the number of/duration of violations against a pre-defined threshold Metrics: violation count, violation duration, longest violation Unlike ITM6 situations, a violation can be defined to occur if the threshold was violated for longer than a certain period of time or number of consecutive samples Support for custom (AWD-internal) calendars as a mechanism of filtering violations during nonprime/vacation hours specific to the application or resource group (unlike TDW shifts and periods which are applied to all agents/attributes) Typical use case: Identify servers that generate most support calls. Evaluate their impact. NNNNNNNNN NNNNNNNNN NNN

15 Grids Grid-based ranking of TEMAs by attribute value and metric Metrics: average, min, max, mean, forecast, percentiles (95, 90, 75) Drill-down into ad-hoc designer for additional customization Filter ranks by MSL, resource group, application Typical use case: Same interface as Rank reports but more trending analysis.

16 Distribution Grouping of TEMAs by attribute value into percentile ranges Metrics: by average, mean, forecast etc. Filter by MSL, resource group, application Typical use cases: virtualization: identify VM candidates using historical performance data, quantify impact of virtualization projects, optimize placement of virtual machines

17 Baselines Regression forecasts can be highly inaccurate for CPU, network and memory usage IT operations cyclicality (EoQ, EoY) Multiple baselines can be overlayed on a single chart (now, 1 week ago, 1 month ago etc.)

18 User-defined Views Consolidated reports for attributes stored in different TDW tables (e.g. Memory, Disk, CPU) No incremental disk space cost because it s a view Transparent to end users: UDV reports are similar to table-based reports

19 Real-time Charts 1-click launch-in-context from a historical report Up to 5 second interval Available on all numeric agent attributes (not just HDC-enabled) Typical use case: Bottleneck analysis and performance diagnostics.

20 Delivery Options Dashboards (personal & administrative) TEPS workspaces Web-based SQL console with CSV export schedule-based PDF delivery to subscribers

21 Export Options Single-click export of raw data or high-level statistics in CSV and PDF formats On-the-fly transformation of Candle timestamps

22 Integration Interfaces HTTP API 20+ methods for retrieving host/agent/rank reports from AWD Typical use cases: - create reporting workspaces in ITM for each agent/server - enrich alerts and support tickets with historical data - post frequently used PDF reports on intranet URL

23 Evaluation 30-day evaluation software available at