Size of the data that gets stored in Germain Datastore depends on the 1) technology you are going to monitor 2) database technology you are going to use to store that data. Some guidelines and we can help with that sizing exercise.

Germain DB Sizing Example

Example of the Database Storage requirements for an environment that has 1500 concurrent users using a CRM and an ERP application, 8 hours per day. For this example, Germain retains 60 days of raw data, and 1 year of aggregated data.

Database Storage Estimate

Excluding Session Replay

Assumed Unit Size

2048

Bytes

Units/Day 

1,000,000


Data retention - Raw/RCA Data

60

Day(s)

Data retention - Aggregated Data

1

Year(s)

Estimated Storage

0.11

TB

Session replay

1-hour Session Replay Size

31.00

MB/hour

Concurrent users using your app

1,500

Concurrent users

Hours/day a user uses your app

8

Hour(s)/day

Data retention

7

Day(s)

Estimated Storage

2.48

TB


Total Estimated Storage

2.60

TB


Note: If we use AWS, The 2000 IOPS is an option that AWS provides where they will guarantee the performance of the storage. We can always remove the "provisioned IO" and go to "GP2 (SSDs)". That would save some cost and the performance should still be good (on AWS large drives have faster IO in general).

Example: 2 Applications

MB/h

30s seek
interval

2 min seek interval

5 min seek interval

ERP application

Extreme User Activity

31.00

27.50

26.80

Expected User Activity

6.40

2.90

2.20

Idle User Activity

4.00

1.20

0.47

CRM Application

Extreme User Activity

10.40

7.50

6.90

Expected User Activity

8.20

5.30

4.70

Idle User Activity

3.90

1.00

0.39

Note: The network traffic difference between two versions of a monitored application may significantly vary, so it is critical to perform a proper sizing analysis for each monitored app and each significant release.