Your SlideShare is downloading. ×

Advanced Administration: Kaseya Traverse

262
views

Published on

Kaseya Traverse is a new addition to Kaseya's IT management suite and focuses on advanced cloud and network monitoring capabilities. In this session we will cover advanced topics for managing your …

Kaseya Traverse is a new addition to Kaseya's IT management suite and focuses on advanced cloud and network monitoring capabilities. In this session we will cover advanced topics for managing your Kaseya Traverse instance. You will learn how to setup SLA measurements for business critical services, perform baseline analysis to automatically adjust alarm thresholds, effectively use templates to facilitate faster rollout, and utilize the query tool for common administrative tasks. While geared towards administrators responsible for day-to-day management of Kaseya Traverse instances, this session will also highlight advanced capabilities that regular users can take advantage of. For attendees not familiar with Kaseya Traverse, the "Kaseya Monitoring Suite Overview" session is a recommended pre-requisite.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
262
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Advanced Administration: Kaseya Traverse Rajib Rashid Sr. Director, Product Management Copyright ©2014 Kaseya 1
  • 2. 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. Copyright ©2014 Kaseya 2
  • 3. Intelligent Baseline Analysis Copyright ©2014 Kaseya 3
  • 4. 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 Copyright ©2014 Kaseya 4
  • 5. Baseline Analysis Workflow Copyright ©2014 Kaseya 5
  • 6. New Suggested Thresholds Copyright ©2014 Kaseya 6
  • 7. Dynamic Adaptive Thresholds Copyright ©2014 Kaseya 7
  • 8. Service Level Measurements Copyright ©2014 Kaseya 8
  • 9. 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 Copyright ©2014 Kaseya 9
  • 10. Business Service Availability Copyright ©2014 Kaseya 10
  • 11. Detailed Drill-Down Analysis Copyright ©2014 Kaseya 11
  • 12. 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 Copyright ©2014 Kaseya 12
  • 13. Device Templates & Profiles Copyright ©2014 Kaseya 13
  • 14. 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 Copyright ©2014 Kaseya 14
  • 15. Linked Device Template Copyright ©2014 Kaseya 15
  • 16. Test Discovery Workflow Copyright ©2014 Kaseya 16
  • 17. BVE API Server Copyright ©2014 Kaseya 17
  • 18. 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 Copyright ©2014 Kaseya 18
  • 19. 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” Copyright ©2014 Kaseya 19
  • 20. 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 Copyright ©2014 Kaseya 20
  • 21. Sample API Commands Copyright ©2014 Kaseya 21 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*" OK 203 request accepted, records returned: 4 "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" OK 203 request accepted, records returned: 1 "serviceName=All Switches", "serialNumber=70011", "memberType=device", "memberName=switch0.zyrion.com", "memberStatus=Critical", "deviceName=switch0.zyrion.com", "deviceSerialNumber=140000", "accountName=My_Company", "accountSerialNumber=49"
  • 22. 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?dev iceName=r* Copyright ©2014 Kaseya 22
  • 23. Sample CLI Query Copyright ©2014 Kaseya 23 % 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" } } }
  • 24. Sample CLI Query Copyright ©2014 Kaseya 24 % 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"
  • 25. Copyright ©2014 Kaseya 25 Questions and Answers Thanks for Attending Kaseya Connect #KaseyaConnect Let's Share!