Advanced Administration: Kaseya Traverse

Advanced Administration: Kaseya Traverse

Rajib Rashid

Sr. Director, Product Management

Copyright ©2014 Kaseya 1

Traverse Advanced Administration

The information in this presentation is confidential and proprietary to Kaseya and may not be disclosed or distributed without the prior written permission of Kaseya. This document, and any related presentation, as well as Kaseya's strategy, possible future developments, products, platforms, directions and/or functionality are all subject to change without notice at Kaseya’s sole discretion. The information in this document does not constitute a commitment, contract, promise or legal obligation to deliver any material, code or functionality. This document is provided without warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. This document is for informational purposes only and may not be incorporated into a contract. All forward-looking statements, including those set forth in this presentation, are subject to various assumptions, risks and uncertainties that could cause actual results to differ materially from projections. Readers are cautioned not to place undue reliance on such forward-looking statements, and specifically, not to rely upon such in making purchasing decisions.


Intelligent Baseline Analysis


Intelligent Baseline Analysis

Why Baseline? – Observe “normal” behavior

– Adjust thresholds in bulk

– Eliminate false alarms

Adaptive Thresholds – Identify “peak” hours from past history

– Customizable by time-of-day, day-of-week

API Enabled – Automate “rolling” baseline adjustment


Baseline Analysis Workflow


New Suggested Thresholds


Dynamic Adaptive Thresholds


Service Level Measurements


Service Level Measurements

Track availability goals – Choose reporting period

• Daily, weekly or monthly

• Custom schedule – Business hours during weekday only

– Determine acceptable downtime • Planned maintenance work

• Software update, patch deployment

– Define service definition • Single device or test

• Service Container across multiple entities


Business Service Availability


Detailed Drill-Down Analysis


Monitoring vs. SLA Measurement

Standard Monitoring

Query device for result

Compare polled value

Raise alarm, trigger action

Affects device/container

SLA Measurement

Goal oriented (pass/fail)

Uses standard monitoring

Critical events only

Proper thresholds needed


Device Templates & Profiles


Device Templates & Profiles

Static Device Template – Snapshot in time of test configuration

– Clone name, thresholds, action profile, schedule

Linked Device Template – Only need to update a “master” device

– Changes propagated to associated devices

Application Profile – Collection of general metric category

– Applied as filter during test discovery


Linked Device Template


Test Discovery Workflow


BVE API Server


BVE API Server

Bulk provisioning and configuration changes – Change warning threshold for all Round Trip Time tests

Automation – Integration w/change control system

– Create new device with ping & SNMP tests

– Add device to an existing container

Data query – Current status of all devices

– List all tests that make up a specific container

– Results for CPU utilization on server A for last week


Command Syntax

<object>.<operation> [“param1=value1” …] – object : device, container, test, dge, user, result, event, …

– operation : create, delete, update, list (search), status, …

Certain commands require admin/superuser privilege

Object, operation, parameter names are case insensitive

Parameter values are case sensitive

Parameters must be quoted (“), separated by comma (,)

For list of parameters: help object.command

Example: – Device.list “deviceName=*router”

– Container.update “serviceName=My_Container”, “actionName=Notify Admin”


Response Format

<status> <response> [additional details] – status : OK, ERR

– response : three digit numerical code

201 response indicated command has been accepted

203 response is followed by search result

Period (.) on a line by itself indicates end of search result

Designed to be parsed by automation tools

Yet keep it human readable


Sample API Commands


device.list "devicename=switch*"

OK 203 request accepted, records returned: 1

"serialNumber=140000", "deviceName=switch0.zyrion.com", "address=192.168.10.251", "deviceType=Switch/Hub", "parentNames=", "snmpCid=secret1", "snmpPort=161", "snmpVersion=1", "snmpOptimize=1", "agentBatchMode=1", "agentPort=161", "agentCommunity=(hidden)", "agentVersion=1"", "tag1 (Tag 1)=", "tag2 (Tag 2)=", "tag3 (Tag 3)=", "tag4 (Tag 4)=", "tag5 (Tag 5)=", "locationName=Default Location", "dgeName=localhost", "isSuspended=false", "clearOnOk=false", "smartNotify=true", "showOnSummary=true", "accountSerialNumber=49", "accountName=My_Company", "isReadOnly=false", "isImported=false", "model=PowerConnect 3024", "vendor=Dell Inc.", "rediscoveryEnabled=false", "comment=“

container.status "serviceName=All*"


"serialNumber=70015", "serviceName=All Network Devices", "status=Critical", "parentSerialNumber="

"serialNumber=70011", "serviceName=All Switches", "status=Critical", "parentSerialNumber=70015"

"serialNumber=70018", "serviceName=All Windows Servers", "status=Critical", "parentSerialNumber="

"serialNumber=70006", "serviceName=All Routers", "status=Ok", "parentSerialNumber=70015"

container.members "serviceName=All Switches"


"serviceName=All Switches", "serialNumber=70011", "memberType=device", "memberName=switch0.zyrion.com", "memberStatus=Critical", "deviceName=switch0.zyrion.com", "deviceSerialNumber=140000", "accountName=My_Company", "accountSerialNumber=49"

BVE API Server Extensions

Command Line Query Tool – Auto-login, command recall, editing

– XML, CSV, JSON, raw output format

– Batch operation using input file

REST API – Compatible signature as BVE FlexAPI

– JSON, raw output format

– https://n.n.n.n/api/rest/command/device.list?deviceName=r*


Sample CLI Query


% utils/bveCLI.pl --host 127.0.0.1 --exec 'device.list "devicename=*switch*"' --fields=accountname,address,devicename,locationname,model --format json

{

"api-response" : {

"data" : {

"object" : [

{

"accountname" : ”My_Company",

"address" : ”192.168.10.251",

"devicename" : ”switch0.zyrion.com",

"locationname" : ”Default Location",

"model" : "PowerConnect 3024",

"serialnumber" : ”140000"

}

]

},

"status" : {

"code" : "203",

"error" : "false",

"message" : "request accepted, records returned: 1"

}

}

}

Sample CLI Query


% utils/bveCLI.pl --host 127.0.0.1 --exec 'container.status "servicename=All*"' --format xml

<?xml version='1.0' standalone='yes'?>

<api-response>

<data>

<object>

<serialnumber>70006</serialnumber>

<parentserialnumber>70015</parentserialnumber>

<servicename>All Routers</servicename>

<status>Critical</status>

</object>

<object>

<serialnumber>70011</serialnumber>

<parentserialnumber>70015</parentserialnumber>

<servicename>All Switches</servicename>

<status>Ok</status>

</object>

</data>

</api-response>

% utils/bveCLI.pl --host 127.0.0.1 --exec 'container.status "servicename=All*"' --format csv

# serialnumber, parentserialnumber, servicename, status

"70006", "70015", "All Routers", "Critical"

"70011", "70015", "All Switches", "Ok"


Questions and Answers Thanks for Attending Kaseya Connect

#KaseyaConnect Let's Share!

Technology

Advanced Administration: Kaseya Traverse