website logo
โŒ˜K
Getting Started ๐Ÿš€
What is DataLakeHouse.io?
Our Business-Value Focus
Learn the Basic Concepts
Connectors
Operations Applications
Toast
Asana
Aloha POS
BILL
Bloom Growth
Bullhorn
Ceridian Dayforce
ConnectWise
Facebook Ads
Food Delivery Service Connector
Google Analytics 4
Harvest
Hubspot
Jira
MailChimp
McLeod Transportation
NetSuite (Oracle NetSuite)
Optimum HRIS
Oracle EBS
Oracle PeopleSoft
QuickBooks Online
Salesforce
Shopify
Square
Square Marketplace
Stripe
TriNet
Verizon Wireless Business
Workday HCM
Xero
Zoom
Databases
Files & Object Storage
SSH Tunnel Setup for Hosted Database Systems
Databases FAQ
SQL Transformations
Terraform: Reverse Terraforming
DBT Cloud Transformations
Sync Bridge (Data Pipelines)
Create a Sync Bridge
Manually Run a Sync Bridge
Deleting a Sync Bridge
Historical Re-sync
Analytics
Access Analytics
Snowflake Usage Analytics
Data Catalog
Create the Catalog
Populate the Catalog
Access the Catalog
Data Warehouse Clouds
Snowflake
Open Source DW Models
Alerts & Notifications
Slack Notifications
Untitled doc
Logs & Monitoring
Security
Callback Links
Service Level Agreement (SLA)
Release Notes
May 2023
April 2023
Q3 2022
Q4 2022
Community Overview
Contributor Agreements
Code Contribution Guide
About
License
Viewpoint
Docs powered byย archbeeย 

Service Level Agreement (SLA)

6min

Each tier of feature service provides increasing levels of support and service assurances that are aligned with the capability of DLH.io to support our customers.

The table(s) below provide a breakdown of each service feature tier align with the respective SLA attributes that will allow each customer to understand expectations surrounding use of the DLH.io service.

These SLA's are backed by the DLH.io Support Team, so that when an support ticket is submitted by a customer regarding an issue, bug, or other unexpected behavior of the platform, our team is ready to receive and handle the requests to resolution. Customers can report incidents and submit support requests via our DLH.io Support Portal, https://support.datalakehouse.io. We maintain a team of engineers and support technicians that provide a sufficient balance for ticket triage and ticket resolution handling for our growing customer base.

If DLH.io is unable to maintain the service levels for each Service offerred as described further in this SLA, then the Customer may be eligible for a credit which may go towards its monthly service fees. This SLA may be updated from time to time where the most recent version of this is found in the legal section of our website, httpss://datalakehouse.com/legal/

Our Core Services SLA

Core Service Name

Description

Monthly Uptime %

Other Detail

Core Web Application

This is the main UI access point

99%

N/A

Developer API

The developer API used to interact programatically with DLH.io

99%

N/A

Analytics Dashboards

Dashboards representing DLH.io analytics applications marketplace items

99%

N/A

Analytics Models

Models related to the transformation of data for application specific ontologies

99%

N/A

๏ปฟ

๏ปฟ

๏ปฟ

๏ปฟ

๏ปฟ

Initial Response Time

This is the time it takes for a support agent to respond via email to any issue once submitted by a customer. Requests for support must be submitted via the DLH.io support portal in order to qualify for the response times and SLAs outlined.

Initiate Response Times

One of our DLH.io agents will respond to your support ticket request in accorance with the ticket severity as outline in this table:

Level

Basic Plan

Enterprise Plan

Business Critical Plan

Level 1

4-8 hours

4 hours

1-2 hours

Level 2

8-16 hours

8-12 hours

4-8 hours

Level 3

24-48 hours

8-16 hours

8-16 hours

Level 4

24-48 hours

24 hours

8-24 hours

๏ปฟ

Severity Levels

Severity

Details

Level 1

(Urgent & Production Delays)

Where any part of the reported feature has an impact to your production systems have a significant risk of loss due to issues with the platform.

Level 2 (High Priority)

An effective result of the platform's current status is affecting the ability to use the DLH.io solution for it's desired and already incorporated process results. A work-around may be temporarily in place but a solution needs to be delivered quickly.

Level 3 (Issue/Bug)

Functionality in the desired use of the platform is mainly accessible and operational, however some functionality of the DLH.io platform appears to have a moderate or low impact on performance expectations.

Level 4 (Low Priority)

Some functionality in the platform seems to be having an impact on desired behavior or utility. However, the impact is minimal as it relates to critical systems or use of a specific feature.

๏ปฟ

Updated 27 Apr 2023
Did this page help you?
Yes
No
PREVIOUS
Callback Links
NEXT
Release Notes
Docs powered byย archbeeย 
TABLE OF CONTENTS
Our Core Services SLA
Initial Response Time
Severity Levels