4.3

4.5 4.4 4.3 4.2 4.1

4.3

4.5 4.4 4.3 4.2 4.1

HarperDB Docs
Getting Started
Developers
Administration
Deployments
Technical Details
- Reference
- Release Notes
  - HarperDB Tucker (Version 4)
    4.3.36
    4.3.35
    4.3.34
    4.3.33
    4.3.32
    4.3.31
    4.3.30
    4.3.29
    4.3.28
    4.3.27
    4.3.26
    4.3.25
    4.3.24
    4.3.23
    4.3.22
    4.3.21
    4.3.20
    4.3.19
    4.3.18
    4.3.17
    4.3.16
    4.3.15
    4.3.14
    4.3.13
    4.3.12
    4.3.11
    4.3.10
    4.3.9
    4.3.8
    4.3.7
    4.3.6
    4.3.5
    4.3.4
    4.3.3
    4.3.2
    4.3.1
    4.3.0
    4.2.8
    4.2.7
    4.2.6
    4.2.5
    4.2.4
    4.2.3
    4.2.2
    4.2.1
    4.2.0
    4.1.2
    4.1.1
    4.1.0
    4.0.7
    4.0.6
    4.0.5
    4.0.4
    4.0.3
    4.0.2
    4.0.1
    4.0.0
    HarperDB Monkey (Version 3)
    3.3.0
    3.2.1
    3.2.0
    3.1.5
    3.1.4
    3.1.3
    3.1.2
    3.1.1
    3.1.0
    3.0.0
    HarperDB Penny (Version 2)
    2.3.1
    2.3.0
    2.2.3
    2.2.2
    2.2.0
    2.1.1
    HarperDB Alby (Version 1)
    1.3.1
    1.3.0
    1.2.0
    1.1.0
More Help

Powered by GitBook

On this page

Deployments

HarperDB Cloud

Alarms

PreviousInstance Size Hardware Specs NextVerizon 5G Wavelength

Last updated 1 year ago

HarperDB Cloud instance alarms are triggered when certain conditions are met. Once alarms are triggered organization owners will immediately receive an email alert and the alert will be available on the page. The below table describes each alert and their evaluation metrics.

Heading Definitions

Alarm: Title of the alarm.
Threshold: Definition of the alarm threshold.
Intervals: The number of occurrences before an alarm is triggered and the period that the metric is evaluated over.
Proposed Remedy: Recommended solution to avoid the alert in the future.

Alarm

Threshold

Intervals

Proposed Remedy

Storage

> 90% Disk

1 x 5min

CPU

> 90% Avg

2 x 5min

Memory

> 90% RAM

2 x 5min

Instance Configuration

Increased storage volume

Increase instance size for additional CPUs

Increase instance size